Assemble AIUC-1 Evidence Pack

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Three-step AIUC-1 evidence pipeline: lint a control-evidence bundle against the 23 automatable AIUC-1 v2026-Q1 controls, assemble a signed control-keyed evidence pack with an OSCAL export, then lint the pack for evidence freshness against the AIUC-1 quarterly re-test cadence and cert expiry.

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

Chain Stages · 3 Steps

1 ROOT node

AIUC-1 Control Evidence Linter art-303-aiuc1-control-evidence-linter

per_control status feeds Stage 2 pack assembly as the control_mapping evidence basis

MCP Call · lint_aiuc1_control_evidence

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "lint_aiuc1_control_evidence",
    "arguments": {
        "aiuc1_version": "2026-Q1",
        "control_evidence": [
            {
                "control_id": "AIUC-A-01",
                "evidence": [
                    {
                        "type": "receipt",
                        "receipt_hash": "sha256:",
                        "issued_at": "2026-06-01"
                    }
                ]
            }
        ]
    }
  },
  "id": 1
}

↓

2 STEP node

AIUC-1 Evidence Pack Assembler art-304-aiuc1-evidence-pack-assembler

controls[] and pack_claim_strength feed Stage 3 freshness lint against the assembled pack

MCP Call · assemble_aiuc1_evidence_pack

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "assemble_aiuc1_evidence_pack",
    "arguments": {
        "aiuc1_version": "2026-Q1",
        "artifacts": {
            "receipts": [
                {
                    "id": "r1",
                    "digest": "sha256:"
                }
            ]
        },
        "control_mapping": [
            {
                "control_id": "AIUC-A-01",
                "artifact_refs": [
                    "r1"
                ]
            }
        ]
    }
  },
  "id": 2
}

↓

3 TERMINAL node

AIUC-1 Evidence Freshness Lint art-305-aiuc1-evidence-freshness-lint

Computes stale_controls and cert_expiry over the assembled pack, final stage

MCP Call · lint_insurance_evidence_freshness

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "lint_insurance_evidence_freshness",
    "arguments": {
        "as_of": "2026-07-14",
        "cert_anniversary": "2026-01-10",
        "controls": [
            {
                "control_id": "AIUC-A-01",
                "newest_receipt_at": "2026-07-01"
            }
        ]
    }
  },
  "id": 3
}

Question: As of the review date, is our AIUC-1 certification still current, or has it expired before this evidence pack goes to the auditor? Run the AINumbers MCP tool `run_chain` with {"chain":"assemble-aiuc1-evidence-pack"} and read `art-305-aiuc1-evidence-freshness-lint.cert_expired`. Re-run with `inputs` for `art-305-aiuc1-evidence-freshness-lint`, reusing the values that result echoed, with `as_of` changed so as_of is 2027-03-01, after the certificate anniversary year ends. 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/assemble-aiuc1-evidence-pack.html

Assemble AIUC-1 Evidence Pack

Ask your agent