OpenShell pilot · ChatGPT connected
Co-Tru.
Your agents work across organisations.
Their evidence should work across them, too.
Turn OpenShell events into private, verifiable evidence — with an independent rail and NEO Chamber governance for acceptance, audit and disputes.
Signed · AES-256-GCM encrypted
Retained by the owner
Existing NEO FX → NEO rail
Independent witness signatures
Acceptance · accountability
Evidence for dispute resolution
Confidential content stays with its owner.
THE ENTERPRISE PROBLEM
When something goes wrong, each organisation has its own logs and its own account of what happened. Sharing every confidential record with the other party — or the model provider — is a poor starting point for trust.
Co-Tru gives them a common basis for checking evidence. The original stays private. Its commitment is witnessed independently. NEO Chamber provides the governance layer when the evidence needs to be accepted or disputed.
FROM THE WORKING OPENSHELL PILOT
Two published records from the Telemach pilot.
Witnessed on 30 September 2026.
AGENT A · RECORD 31
An OpenShell event reported as allowed by its owner, committed to the existing rail and backed by two witness signatures.
049ec81ddbd1f58f194c2bdeeaa41bb0213e26a74279d225cc7411d6f9e56be4AGENT B · RECORD 36
An OpenShell event reported as blocked by its owner, following the same commitment, witnessing and evidence retrieval path.
9a0210690f95bfba452a9132f06eee938005abc6955389f80390c5570555e67eThe verifier recomputes commitment inclusion and checks the pinned neo-5 and neo-6 Ed25519 signatures. These records have BASE/WAW WITNESSED proofs. Their ALLOWED/BLOCKED labels are owner-reported; source completeness is not established. The dated Chamber receipts are evidence lookups, not dispute rulings. This pilot is separate from the newer N8 FINAL / ML-DSA rail. The archived proof closes to HOUR; the live refresh checked on 1 October reached ANNUAL. The MCP tools can fetch and verify the current proof again.
Public witness keysTHE NEXT DEPLOYMENT PATH · VALIDATED AT THE SOURCE
OpenShell v0.1.2 · Kyma driver v0.9.1
1 October 2026 · 11:00–11:24 UTC
Co-Tru's new source connector collects OpenShell events on Kubernetes. The Novska test verified collection, recovery after a crash and visibility of an interrupted handoff — using the open-source driver for SAP BTP Kyma.
COLLECTION
The connector was added automatically beside the OpenShell supervisor. It read the event file and handed off every complete record up to the measured checkpoint, with zero backlog.
CRASH RECOVERY
After a forced collector crash, Kubernetes restarted it. Collection resumed from the saved position without repeating the earlier request, then delivered five more records.
LIFECYCLE
Stop and delete closed the observed streams. Starting again created a new generation and pod identity, with the collector automatically attached to the new supervisor.
FAILURE VISIBILITY
When the receiver was deliberately made unavailable before shutdown, the pod disappeared but its stream remained open. The test identified this as possible_loss.
This run validated the source connector on a kind Kubernetes cluster. Connecting it to Co-Tru's evidence intake and running the joint rail test are the next steps.
| Scenario | Observed result |
|---|---|
| Automatic injection | The webhook added the native sidecar to the supervisor pod. |
| Driver compatibility | The sandbox remained Ready through collection and collector restart. |
| File access | The collector read the OCSF file using the supervisor's UID/GID, with a read-only log mount. |
| Record handoff | Three records reached the test receiver; its offset matched the 2,480-byte file. |
| Collector crash | A SIGKILL followed by a container restart preserved the cursor; five subsequent records advanced it to 7,082 bytes. |
| Stop, start and delete | Observed streams closed with FILE_END and STREAM_END; a new run received a new source identity. |
| Forced pod deletion | The tested stream closed cleanly. OpenShell then left that sandbox in Provisioning without a supervisor; this was recorded separately. |
| Receiver unavailable at shutdown | The final stream had no STREAM_END and no live pod: possible_loss was identified. |
The receiver was an in-memory test double. This run used process events generated by sandbox commands; it did not produce the ALLOWED/BLOCKED rail proofs displayed above. Those belong to the separate Telemach pilot. Live daily rotation, a lost acknowledgement, the real intake and the joint rail path remain follow-up checks. The run does not establish complete capture under every failure.
The source connector was built and tested in Claude Code; the existing Co-Tru evidence adapter and MCP connection were built in Codex. Codex also checked the running Novska infrastructure and the receiver's aggregate status before publication.
Download the public validation recordA MODULAR ADDITION TO THE EXISTING STACK
Co-Tru's NOSGOA adapter reads OpenShell's OCSF events at the owner. It preserves the existing edge, NEO FX and rail interfaces.
Full events and signed envelopes remain encrypted at the owner. The rail receives the 32-byte binary commitment.
Five read-only tools for finding evidence, verifying proofs, retrieving Chamber receipts and refreshing rail proofs.
The Linux/OpenShell pilot runs on Telemach. The Kubernetes source connector has passed its Novska test with the Kyma driver, ready for the joint intake test.
CONNECT CO-TRU
Connect the public demonstration to ChatGPT or another compatible MCP client. It exposes the published pilot evidence, with no login to Co-Tru required.
This is the server address for your AI client. The page you are viewing is the presentation link.