The Synthesis; AI Assurance (the what); AI Confidence Engineering (how we know); the Crosswalk and its eleven notes; the testing lifecycle, two pillars, three levels, scoping, design, and the 0–2 rubric; the Intent Layer; anchors A2 and Anchors × Evidence Layers; Closing the Complexity Gap; the beliefs on the Two Unknowns, multi-model compounding, foundational capabilities, confidence as a scarce resource, and justifying generation; Pillar 1 and values V01, V03, V04, V08, V09, V11.
Sections 9 and 10
Sources
A position paper and blueprint extension. The companion folder holds sixteen wiki-ready notes: a map of content, a phase map, nine weave notes, a fifth anchor, four templates, and integration notes.
21 October 2026
Cited
Where the argument comes from.
Spec-Driven Development: A Spec-First Approach to AI-Native Engineering
Apoorv Gupta, Microsoft for Developers, 10 June 2026.
GitHub Spec Kit
README and spec-driven.md — constitution, specify, plan, tasks, implement, converge.
OpenAssurance.ai blueprints
Specification-spine diagrams
The specification spine: components by status. The source of the definition.
Into the vault
What the paper asks to merge.
- Copy spec-driven-assurance/ beside crosswalk/, ai-assurance/, and confidence-engineering/.
- Add The third weave — Spec-Driven Assurance to the master map of content, and #spec-driven-assurance to the tag map.
- Add a row to the Crosswalk map of content, and extend the operating rule to SDD artifacts.
- Add the A5 row to Anchors × Evidence Layers, the four-anchor table in Closing the Complexity Gap, and Anchors × Manifesto Values. Close the open thread on specification-by-example as the primary artifact.
- List the four templates in Reusable Assets Strategy, and append the index rows from the integration note.
Four templates belong in the reusable-assets library: an assurance constitution, a spec for an AI-infused feature, assurance gates for plan and tasks, and a validate-and-converge record.