Attested Subject to Quarterly Test Evidence Pack

AI governance and assurance, not lifecycle-bound. Identifier handoff (subject_hash), not a computed value passed on. Two-step quarterly evidence flow: bind a sealed artifact into a subject identifier, then compose the quarter's testing-evidence pack tied to that subject. Stop condition before step 2: proceed only when step 1 reports binding_complete true and producer_pinned true; a pack built over an incomplete or unpinned subject is labelled not attested.

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT node

Attested Artifact Subject Binder art-502-bind-attested-subject

Then the step 2 run takes the step 1 output's subject_hash unchanged by name and wraps the pack's per-test receipt digests into an evidence bundle tied to that subject

MCP Call · bind_attested_subject

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "bind_attested_subject",
    "arguments": {}
  },
  "id": 1
}

↓

2 STAGE 2 node

Quarterly Agent Test Evidence Composer art-378-quarterly-test-evidence-composer

Then, only when the stop condition holds (binding_complete true and producer_pinned true), the quarterly testing-evidence pack is composed and its per-test receipt digests are wrapped into an evidence bundle tied to subject_hash; otherwise the pack is labelled not attested

MCP Call · build_agent_test_evidence

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_agent_test_evidence",
    "arguments": {}
  },
  "id": 1
}

↓

3 TERMINAL node

Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator

Then the session receipts are aggregated into the session receipt

MCP Call · aggregate_execution_receipts

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}

Question: Is this quarter's test evidence tied to one identified, pinned subject, or is the pack not attested? Run the AINumbers MCP tool `run_chain` with {"chain":"attested-subject-to-quarterly-test-evidence-pack"} and read `art-378-quarterly-test-evidence-composer.ha_evidence_bundle`. Re-run with `inputs` for `art-378-quarterly-test-evidence-composer`, reusing the values that result echoed, with `subject_hash` changed so remove subject_hash and watch ha_evidence_bundle go null. Compare the same field. Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`. Ledger, for a human re-check: https://ledger.ainumbers.co/ PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads. Chain page: https://ainumbers.co/chaingraph/chains/attested-subject-to-quarterly-test-evidence-pack.html

Attested Subject to Quarterly Test Evidence Pack

Ask your agent