Runtime Governance Records

What gets recorded

The runtime governance profile covers seven observable event categories under theorg.peacprotocol/runtime-governance namespace. Each event maps to one of the 6 type URIs in the extension registry.

Install

pnpm add @peac/adapter-runtime-governance @peac/protocol

Basic Usage

The adapter accepts your runtime's governance event output and maps it to a structured PEAC record. Pass the record to issue()with your signing key to produce a compact JWS.

import { mapRuntimeGovernanceEvent } from '@peac/adapter-runtime-governance';
import { issue } from '@peac/protocol';
import { loadKey } from '@peac/crypto';

const signingKey = await loadKey(process.env.PEAC_SIGNING_KEY_JSON!);

// Your governance runtime emits a structured event
const governanceEvent = {
  kind: 'policy-evaluation',
  policy_ref: 'urn:policy:agent-safety-v2',
  subject_ref: 'did:key:z6Mk...',
  outcome: 'allowed',
  reason_code: 'scope_permitted',
  evaluated_at: new Date().toISOString(),
};

// Map to PEAC record shape
const record = mapRuntimeGovernanceEvent({
  event: governanceEvent,
  issuer: 'https://governance.example.com',
  subject: 'did:key:z6Mk...',
});

// Issue a signed record
const { jws } = await issue({
  claims: record,
  issuer: 'https://governance.example.com',
  signingKey,
});

// jws is a compact JWS — carry it in PEAC-Receipt header or A2A metadata
console.log(jws);

Record shape

Each record carries governance-specific fields inside the extension block. All identifiers are opaque references — no raw policy text, agent identity strings, or runtime-internal data is stored inline.

{
  "iss": "https://governance.example.com",
  "sub": "did:key:z6MktyMgNkikLRwqEYq7FRX5...",
  "iat": 1747008000,
  "typ": "interaction-record+jwt",
  "peac": {
    "kind": "interaction",
    "pillars": ["safety", "compliance"],
    "type": "org.peacprotocol/rtgov-policy-evaluation",
    "extension": {
      "policy_ref": "urn:policy:agent-safety-v2",
      "subject_ref": "did:key:z6Mk...",
      "outcome": "allowed",
      "reason_code": "scope_permitted",
      "evaluated_at": "2026-05-11T10:00:00.000Z",
      "upstream_artifact": {
        "source": "agt-policy-engine",
        "version_ref": "urn:version:2026-05-11"
      }
    }
  }
}

The upstream_artifact block preserves the raw source attribution from the governance runtime without synthesizing additional semantics.

Microsoft AGT / AAIF Compatibility

The runtime governance adapter was designed with the Azure AI Foundry (AAIF) and Agent Governance Toolkit (AGT) event model as the primary mapper use case. AGT governance events map directly into RTGOV type URIs without schema changes.

import { mapAgtGovernanceEvent } from '@peac/adapter-runtime-governance';

// AGT emits its native event shape
const agtEvent = await agtRuntime.getLastGovernanceEvent();

// Map to PEAC record — no extra wiring needed
const record = mapAgtGovernanceEvent(agtEvent, {
  issuer: 'https://governance.example.com',
});

Upstream artifact preservation

PEAC never synthesizes governance outcomes from incomplete data. Theupstream_artifact block is required on all RTGOV records and preserves the source runtime's attribution without interpretation.

Conformance — Section 27 (RTGOV)

Seven requirements cover the observable emitted-record semantics for runtime governance records.

Resources