One card for who and what stood behind an agent decision
An agent decision receipt carries a reserved pp.lineage block inside policy_parameters, so the lineage is covered by the artifact's execution_hash with no extra mechanism. Paste a receipt below and this page renders the lineage as a card: which model produced the output and whether that fact is attested or only asserted, how much autonomy the agent had across the five questions supervisors ask, the intent to policy to action to outcome chain, the caller's trace binding, and every hash the receipt carries. When the artifact embeds its preimage the execution_hash is recomputed in your browser and compared, so a lineage that changed after sealing shows MISMATCH.
๐ All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data โ use synthetic or anonymised inputs only.
The lineage card
Every section renders exactly the states present in the input. A member the receipt does not carry renders as not present; the card never fills a gap, scores the receipt, or judges the evidence.
Model identity
Autonomy tier
Intent → policy → action → outcome
Trace binding
Hash bindings
Principal authority members spec-pending
What this page is and is not: No AINumbers node emits pp.lineage yet; these fixtures follow the published draft shape. The card is render-only: it displays exactly the states present in the input, recomputes the execution_hash from the embedded preimage when both hashed members are present, and never generates, scores, completes or judges the evidence. The delegation_chain, human_checkpoints and revocable_by member names are spec-pending: they are not in the published draft schema, so a fixture carrying them is labelled spec-pending above and an absent member renders as not present rather than missing or invalid.
In the AINumbers estate: the estate does this today for policy scope: a Policy Mandate export names the principal, the allowed actions and the mandate caveats, and the receipt family that binds intent to outcome is the OpenChainGraph execution_hash artifact, verifiable in the Execution Hash Explorer and the receipt verifier. How the lineage members above plug in is a design: a future receipt kernel would carry pp.lineage in the same preimage position the hash already covers. The estate does not use pp.lineage today.