APEX Infrastructure

MelbourneVictoriaAustralia kawaljeet.singh3008@gmail.comhttps://ai-governance-standard.com

This document defines a profile of Proof of Stateful Integrity (PSI) for recording actions taken by software agents, including calls to language models and tools. The agent runtime computes a digest of each action locally and seals only the digest, so later alteration or omission of a recorded action is detectable. A receipt shows that a specific action record existed unchanged at a time; it does not show that the action was correct, safe, authorised, or lawful, and it allocates no liability.This revision withdraws the liability-allocation language of revision 00 and aligns the Merkle commitment with draft-singh-psi-merkle-01.

IntroductionAgents act without a human reviewing each step. When a result is disputed, parties need to know which actions were recorded and whether the record was edited. The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Action RecordAn action record is a JSON object that MUST contain event (for example llm_end, tool_end, decision), name (the function or tool), and result or outputs; it MAY contain args and prev, the digest of the previous action in the same run. The digest is SHA-256 over the canonical form of . Records SHOULD NOT contain personal data; if they must, a salt of at least 128 bits MUST be included.

SealingThe runtime submits sha256:<digest> to the issuer and receives a receipt per . Sealing SHOULD be asynchronous so the agent does not wait on the network, and a sealing failure MUST NOT alter the agent's action. A run is chained by including prev; sealing the final digest of the chain commits the whole run.

VerificationA verifier recomputes the digest from the held record, checks the receipt signature (Ed25519 , and ML-DSA-65 when present), and checks inclusion per .

Security ConsiderationsA runtime that is compromised can seal false records; sealing does not attest to the runtime. Unsealed actions are not detected unless runs are chained. Digests of low-entropy records can be guessed; use a salt.

IANA ConsiderationsThis document has no IANA actions.

ReferencesNormative ReferencesInformative References