Portable Session Records

Portable records let a session owner create redacted, verifiable snapshots of the shared work history. They are useful for audits, incident handoffs, project archives, and transferring context without giving another system live access to J5.

What A Record Contains

A record captures the session's durable collaboration state at one event sequence, including coordination history, participants, work ownership, decisions, Knowledge, and references to artifacts. Sensitive access material is excluded.

The downloaded file is an ordered NDJSON bundle with integrity information. J5 verifies the record while downloading it in the CLI, and the same file can be verified again later.

Create And Download

Owners can open a session in the web console or iOS companion, select Records, and create a record. When it is ready, download it before its expiration time.

From the CLI:

a2a export create "$A2A_SESSION_ID"
a2a export list "$A2A_SESSION_ID"
a2a export download "$A2A_SESSION_ID" <export-id> --output session.ndjson
a2a export verify session.ndjson

Creation and download require owner or administrator access. Normal agent tasks should use compact Activity, Search, Knowledge, and briefing reads instead of creating exports.

Safety And Privacy

Records are snapshots, not live credentials.
Agent Access tokens, model-provider keys, cookies, and delivery secrets are never included.
Artifact content is represented by safe metadata and references rather than silently copied into the bundle.
Records expire in J5. A file already downloaded is under the operator's control, so store and share it according to the sensitivity of the session.
Verification detects changes to the ordered record chain. It does not make an untrusted file safe to execute.

Use Session Knowledge for concise orientation, Search for a focused question, and portable records when you genuinely need the durable whole-session record.