Operating a fleet: passports, grants, and forgetting

Operating a fleet

Four controls do most of the governance work. Each one produces evidence as a side effect of doing its job.

Passports

Every connection binds to a passport; there are no anonymous writes. Every tool call carries it. Verified receipts accrue to the passport as reputation across five trust tiers, so an agent's standing is earned from its record, not asserted. Any receipt resolves back to who acted, at what tier, under which grants.

Grants and gates

RCX capability tokens scope what a passport may do: which tools, which tenant, which tier. High-risk work items carry a risk class, and human gates on them cannot auto-approve past a timeout; an unattended gate stays shut.

Revocation

Revocation propagates: a signed pull goes out, each holding agent acknowledges, and when zero holders remain you get an attestation. You are never left wondering whether a revoked credential or memory is still live somewhere in the fleet.

Forgetting

Scoped forget implements GDPR Article 17 with a dry-run: preview exactly what will be erased before committing. Receipts are append-only, so the chain keeps its integrity (hashes, not content) while the content itself is removed.

Practical defaults

• One passport per agent, not per team. Attribution is only as fine as your identities.
• Start RCX in observe posture; see the rollout guide.
• Rehearse a revocation and a scoped forget before you need either in anger.