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 ATTEMPT / NO MATERIAL OUTPUT

Invocationinv_fnemyofze9
CapabilityCONSCIENCE_GATE
Actorowner:terminal-key
Timestamp2026-07-30T00:16:34-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 fingerprintf5ab38ff2a60bc4cf6d6712c954e85b021da7ca7bae724d61091186205f2396a
Output fingerprint70c7166fbf8f128d8d2f3eedc1bd5077d5de50d8fcded9c22805fb585800d6ff
Contract fingerprint4619cba66778e825a5b23928397d7c70a56e7d85ee5fa1775a452160ce5d493a

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