Skip to content

docs: design SpecSafe evidence chain #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LaloLalo1999 merged 2 commits into from
Sep 8, 2026
Merged

docs: design SpecSafe evidence chain #71

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c55e2ab
docs: design SpecSafe evidence chain
LaloLalo1999 Aug 24, 2026
d31b8fd
docs: position evidence chain within governed delivery architecture
LaloLalo1999 Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,13 @@
SpecSafe is a two-phase software engineering framework for AI-assisted development. It provides structured planning workflows to reduce ambiguity, then enforces test-driven implementation through small spec slices — regardless of which AI coding tool you use.

For the full canonical workflow, see [docs/SPECSAFE-CANONICAL-WORKFLOW.md](./docs/SPECSAFE-CANONICAL-WORKFLOW.md).
For the proposed cross-product assurance seam and future operating plan, see
[SpecSafe Evidence Chain and Readiness Extension](./docs/SPECSAFE-EVIDENCE-CHAIN-DESIGN.md).

Within the governed delivery architecture, SpecSafe remains repo-local
assurance: Telar owns business intent, policy, stable identity, human authority,
and the normalized ledger; Ultimate Harness is the sole Run Control; OMP
Pantheon is the OMP Execution Adapter.

## Two-Phase Workflow

Expand Down
Loading
Loading