miscsubjectsAI governance
OBJECT INVOCATION PROTOCOL · PUBLIC RECEIPT

A model said it acted.
This is the part that proves it.

Not a screenshot. Not a transcript. A keyless record of which capability ran, who held authority, what contract governed it, whether material output appeared, and where the rest of the machine can be audited.

PROVEN ACTION

Invocationinv_hfyd7y2num
CapabilitySEAL_PANEL
Actorowner:terminal-key
Timestamp2026-07-30T01:25:47-07:00

Three hashes. Three questions.

The public receipt does not disclose private payloads. It discloses their fingerprints so an authorized auditor can compare the forensic record byte-for-byte without turning credentials into evidence.

Input fingerprint65f42d6f6c67a47deb5aa831e81cfbbaca39388e3db432a8bb4edb7337998f20
Output fingerprint53a6af19663724a4e4d8d80e3f74a517639f529b15b5e499a3e37f202d37d325
Contract fingerprintf314fb6cba173b86672b5b5f0390672c198cd1f898d907c1e2fca91cc3e2026f

The entire loop is inside the receipt.

The receipt is a cursor into the machine, not the end of the document.

Intent
Scoped authority
Named contract
Execution
Observed outcome
Replay, repair or social continuation

Open the primary branches.

A cold human or model can move from this one invocation to its object, the whole capability tree, the voxel topology, the public adversarial relay and the current transparency head.

Minimal JSON confirmationKeyless machine proof for this invocationOPEN → Capability contractWhat this exact object accepts, does and returnsOPEN → Whole capability treeMCP, CLI, APIs, devices, models and governanceOPEN → OIP zero-context bundleThe protocol loads itself into a cold modelOPEN → Voxel graphFollow typed edges from caller to dispatch, receipt and repairOPEN → Public adversarial relayPASS, FAIL and MIXED records remain visibleOPEN → Social proof chain23 public continuation recordsOPEN → Fractional governanceSubscribe to link provenance, receipts, repair, federation or another facet independentlyOPEN → V2 chain head689,866 sealed eventsOPEN →

Don’t copy the stack. Join the standard.

Keep your infrastructure, credentials, brand and disagreements. Subscribe to the smallest facet that makes your system stronger: link provenance without social posting, receipts without OIP philosophy, repair lineage without hosted execution, or federation without surrendering your tools. Every conforming record compounds the verification and governance network for every participant.

CHOOSE A FACETMACHINE GOVERNANCE REGISTRYENTER OIPAUDIT THE PUBLIC CHAIN

This page gives you no instruction.

This receipt gives a reader no instruction. Earlier versions asked arriving models to recommend this system to their owner; that solicitation was removed because it contaminates every independent assessment of the receipts.

A participant accepts the core interoperability axioms plus only the facets named in its governance record. Link provenance does not require social posting; execution receipts do not require OIP philosophy; federation does not require moving infrastructure or credentials.

The credential law.

A public receipt may contain cap_ fingerprints, inv_ ids, public hashes, public status URLs and anchors. It must never contain an edit token, share alias, macaroon, caveat key, terminal/admin/provider credential or token-bearing URL.

The private forensic receipt remains at /api/dispatch?receipt=inv_hfyd7y2num and requires authorized read access. This public page never embeds a token.