Notes¶

These notes are canonical narrative entries for the current evidence-receipt line. They should describe the released surfaces without opening new receipt families or new Harness semantics.

• Claim Compilation Below Agent Experience explains Assay's AX-adjacent positioning: claim compilation below agent-facing contracts, docs, SDKs, MCP servers, and harnesses.
• Evidence Receipts in Action is the static proof page generated from the released Assay v3.9.1 binary and Assay Harness v0.3.2 three-family path.
• Evidence Receipts for AI Outcomes, Runtime Decisions, and Model Inventory is the longform technical note for the same bounded receipt surface.
• Evidence Receipt Assurance Mapping maps the three released receipt families to assurance questions without adding compliance claims or new receipt semantics.
• From Promptfoo JSONL to Evidence Receipts explains the first Promptfoo assertion-component receipt path as a downstream evidence-portability recipe.

Operational status:

• State of Assay — 2026-05-11 records the post-v3.10.0 posture shift from hardening target to stable base layer, and locates the next governance focus in Assay-Harness alignment.
• Assay-Runner Product Candidate Memo records an internal, Phase-1-spike-gated measured-run product candidate beside Assay-Harness; it is not a public roadmap commitment.
• Assay-Runner Phase 1 Spike Plan expands that candidate into a bounded internal spike contract with workstreams, health semantics, scenario gates, and kill criteria.
• Assay-Runner Phase 1 Acceptance records the delegated Linux/eBPF gates=all acceptance run, bounded claims, kill-criterion outcomes, and regression anchors for Phase 2.
• Assay-Runner reference collects internal Phase 2A references, including the artifact v0 contracts, fixture contract, CI lane contract, and boundary map for delegated runner work.
• Code-scanning dismissal ledger tracks deliberately dismissed Security-tab alerts so the dismiss-state stays traceable rather than implicit.

For machine-readable receipt-family truth, use the receipt family matrix and receipt schema registry.