Human membership
The production tenant retained two active humans—one owner and one auditor—with no pending invitations.
PUBLIC EVIDENCE
Start with a portable MCP2 example that reconstructs one selected decision without MCPaios access. The preserved September 3 production proof below documents a separate historical deployment; it is not a live inventory of today’s tenant.
EVIDENCE / PORTABLE EXAMPLE / HISTORICAL PROOFEXTERNAL REVIEW
The bundle supplies the original verification request, its complete one-grant chain, policy material and digest binding, decision receipt, and historical verifier time. After obtaining the repository, run this command from its root:
node examples/portable-reconstruction-v1/verify.mjsThe example needs no database, network service, MCPaios account, or operational secret. It does not imply that arbitrary live receipts are automatically exportable in this shape or independently signed. A decision receipt alone is not the complete evidence package.
Open the pinned portable example →WHAT WAS DEMONSTRATED
The public evidence is deliberately bounded to the path that was actually exercised.
The production tenant retained two active humans—one owner and one auditor—with no pending invitations.
Separate production operator and fence credentials were provisioned with one-time plaintext handling and hash-only persistence.
The fence committed an ALLOW before the harmless local demo.echo action executed and later bound SUCCESS completion evidence.
The owner revoked the exact bounded grant with a recorded human reason.
The same fence request class returned GRANT_NOT_ACTIVE; local execution and completion were skipped.
Both temporary production service credentials were revoked; active production service credentials returned to zero.
Both the successful pre-revocation path and later denial remained reproducible with identities, scope, protocol, and authority state.
HISTORICAL STATE · SEPTEMBER 3, 2026
That historical deployment’s final state retained the historical record while leaving no active grant or service credential from the demonstration.
WHY RECONSTRUCTION MATTERS
Requested: the machine proposed exact demo.echo authority against one target.
Approved: the authenticated owner ratified that proposal with a recorded reason.
Granted: the operator issued only the exact ratified scope.
Decided: the fence committed a durable ALLOW against authority revision 14.
Completed: the external fence reported SUCCESS after local execution.
Stopped: human revocation advanced authority state; the later request received durable DENY without execution.
EVIDENCE BOUNDARY
It does not prove arbitrary remote target execution safety.
It does not claim protection against every compromised infrastructure dependency.
It does not claim hardware-backed trusted time or universal Byzantine independence.
It does not claim readiness for every possible target connector.
OPERATE THE BOUNDARY
The Control Plane exposes receipts, completion evidence, reports, and full reconstruction only to authenticated members.