Skip to Content
OperationsPortability & export

Portability & export

Status on 9 November 2026: this page describes the planned export bundle. What exists today: you can request an export of your data, Nebbos operators can run a whole-tenant export, and your data is returned at the end of an engagement under the processing agreement . The self-serve bundle in a documented format, the signed receipt and the offline verify.sh described below are not built yet, and no export runs on deploy.

Continuous exercise (planned)

The plan is for the deploy pipeline to run a full export against a scoped test tenant on every production release, using the same code path and bundle format as an operator export, so that a break in the export path fails the deploy. This is not in place yet.

Bundle structure (planned)

An operator-initiated export produces a single archive with five sections. Each section is described by a manifest included in the archive.

SectionContent
Structured dataEvery operator-scoped row from every substrate table the operator has touched, emitted as JSON Lines with stable field names. One file per table. Schema references accompany each file; schema changes within the export window are documented in the manifest.
Audit chainAudit-chain entries scoped to the operator identities included in the export, accompanied by a signed hash-verification receipt. Independent verification does not require further platform calls.
Knowledge graphThe operator’s slice of the knowledge graph, including Pearl memory registers, insight rows, playbook selections, and prediction traces. Emitted as stable-shape JSON with per-node provenance.
AttachmentsUploaded documents, PDFs, images, and meeting recordings preserved in original bytes with original filenames and content types. Each file references its provenance in the structured data.
Cradle re-provisioning packetFor Host-tier and Architect-tier operators, a packet permitting re-mount of Pearl memory on a replacement Cradle. Issued only when the operator authenticates on a currently-held Cradle.

Independent verification (planned)

Every bundle includes a verify.sh script. The script walks the audit-chain segment inside the bundle, recomputes every hash, and compares the result to the signed receipt embedded in the bundle metadata. Script dependencies are limited to POSIX shell, sha256sum, and a JSON parser.

tar -xzf nebbos-export.tar.gz cd nebbos-export ./verify.sh # Sample output: # ✓ audit-chain: 12,483 entries walked, all prev_hash/next_hash bonds match # ✓ signed receipt matches platform-issued receipt # ✓ manifest checksums match file contents (1,247 files) # EXPORT VERIFIED

The bundle manifest documents every field the manifest carries, permitting a party unfamiliar with Nebbos source code to read the bundle format directly.

Bundle exclusions

The bundle contains only content the operator has a claim to. Nebbos internal operational data — model weights, shared platform artefacts, and other operators’ scopes — is not included, as the exporting operator has no claim to that content.

See The audit chain for how audit records are checked today and Row-level isolation for the enforcement of scope boundaries at the substrate.