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_kx2x79mbkd
CapabilitySEAL_PANEL
Actorowner:terminal-key
Timestamp2026-07-29T20:06: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 fingerprint8d1b37c7527acb84479e603e3fbd091b01392227d86675caa579eff76ffaa19a
Output fingerprintfc0a885c3ed94510dd138e240be55f3b479eaae57e566a9a0cfaf62abf1ce052
Contract fingerprint98235c148663c7c34e644ef2c51d80be4a4d71af59a6384445a6804dee0c39cd

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

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.

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_kx2x79mbkd and requires authorized read access. This public page never embeds a token.