Archive completed sprint documentation and deliverables: ## SPRINT_3500 - Proof of Exposure (PoE) Implementation (COMPLETE ✅) - Windows filesystem hash sanitization (colon → underscore) - Namespace conflict resolution (Subgraph → PoESubgraph) - Mock test improvements with It.IsAny<>() - Direct orchestrator unit tests - 8/8 PoE tests passing (100% success) - Archived to: docs/implplan/archived/2025-12-23-sprint-3500-poe/ ## SPRINT_7100.0001 - Proof-Driven Moats Core (COMPLETE ✅) - Four-tier backport detection system - 9 production modules (4,044 LOC) - Binary fingerprinting (TLSH + instruction hashing) - VEX integration with proof-carrying verdicts - 42+ unit tests passing (100% success) - Archived to: docs/implplan/archived/2025-12-23-sprint-7100-proof-moats/ ## SPRINT_7100.0002 - Proof Moats Storage Layer (COMPLETE ✅) - PostgreSQL repository implementations - Database migrations (4 evidence tables + audit) - Test data seed scripts (12 evidence records, 3 CVEs) - Integration tests with Testcontainers - <100ms proof generation performance - Archived to: docs/implplan/archived/2025-12-23-sprint-7100-proof-moats/ ## SPRINT_3000_0200 - Authority Admin & Branding (COMPLETE ✅) - Console admin RBAC UI components - Branding editor with tenant isolation - Authority backend endpoints - Archived to: docs/implplan/archived/ ## Additional Documentation - CLI command reference and compliance guides - Module architecture docs (26 modules documented) - Data schemas and contracts - Operations runbooks - Security risk models - Product roadmap All archived sprints achieved 100% completion of planned deliverables. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
31 lines
883 B
Markdown
31 lines
883 B
Markdown
# Contracts and interfaces
|
|
|
|
Contracts are the authoritative specs for cross module interfaces. They
|
|
define data models, API expectations, and integration rules.
|
|
|
|
Why contracts exist
|
|
- Keep module boundaries stable across teams.
|
|
- Unblock sprint work by publishing versioned specs.
|
|
- Preserve determinism and offline compatibility.
|
|
|
|
Core contract areas
|
|
- Advisory key canonicalization
|
|
- Risk scoring jobs and profiles
|
|
- Mirror bundle and sealed mode
|
|
- VEX Lens and verification policy
|
|
- Policy studio and authority effective write
|
|
- Export bundle and findings ledger RLS
|
|
- API governance baseline
|
|
- Scanner surface and analyzer bootstrap
|
|
- RichGraph v1 reachability schema
|
|
|
|
Lifecycle
|
|
- Draft, published, deprecated, retired.
|
|
- Breaking changes require a new version and migration notes.
|
|
|
|
Related references
|
|
- docs/contracts/README.md
|
|
- docs/contracts/*.md
|
|
- docs/adr/*
|
|
- docs/specs/*
|