ContextLattice v3.24.0 - Portable Continuation

ContextLattice v3.24.0

Portable Continuation

ContextLattice can now carry the state of serious work across machines without
turning memory into a sync service or trust into a checkbox. The CLI remains
the primary interface. HTTP remains the integration fallback.

What changed

• contextlattice_agent_tools portable-continuation adds one canonical CLI
  family for collaborative grants, provenance-preserving import plans and
  receipts, encrypted continuation manifests, reconciliation, and status.
• Context Passport diffs now include a bounded human-readable view of changed
  objectives, scope, claims, evidence, lineage, and redaction provenance.
• Collaborative grants are signed, least-privilege, recipient-bound,
  purpose-bound, time-bounded, usage-limited, delegation-limited, and
  revocable. Fresh authorization is performed again at reconciliation.
• Continuation manifests contain digest references rather than raw prompts or
  memory. Context Mesh seals the signed manifest and grant with native age
  X25519 encryption; the sender chooses the delivery channel.
• Receivers reject wrong recipients, expired or tampered artifacts, issuer
  repackaging, stale subject snapshots, key-epoch drift, exhausted grants,
  divergent lineage, and replay.
• Provenance-preserving importers create deterministic, atomic, resumable plans.
  An external worker performs the import and returns an opaque execution digest;
  the gateway records the receipt but never executes the import or mutates
  ordinary memory.

Product boundary

The public core includes human-readable Passport diffs, signed collaborative
grants and revocations, provenance contracts, deterministic import planning,
encrypted cross-machine continuation, dry-run reconciliation, bounded durable
state, telemetry, and the primary CLI.

Operator and Enterprise add workspace policy, approval and review queues,
bounded retention and history, bulk revocation governance, and schedules for
operator-chosen external delivery or import adapters. Paid governance still
does not deliver an envelope, contact a connector, run a model or subprocess,
execute an import, write ordinary memory, merge, or push.

CLI

Each POST operation reads an owner-only JSON payload. Rich artifacts can stay
out of the agent transcript by writing the result to an owner-only file.

contextlattice_agent_tools portable-continuation grant-create \
  --payload-file grant-request.json --output grant.json --pretty

contextlattice_agent_tools portable-continuation manifest-create \
  --payload-file continuation-request.json \
  --output continuation-envelope.json --pretty

contextlattice_agent_tools portable-continuation manifest-reconcile \
  --payload-file reconciliation-request.json \
  --envelope-file continuation-envelope.json --pretty

contextlattice_agent_tools portable-continuation status --pretty

Rollback

Stop the external transport or import adapter, revoke the exact collaborative
grant, and reject pending review or schedule records. Preserve signed grants,
revocation tombstones, import receipts, Passport lineage, and conflict evidence;
never replace rollback with silent deletion or last-write-wins.