docs: Archive Sprint 3500 (PoE), Sprint 7100 (Proof Moats), and additional sprints
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>
This commit is contained in:
30
docs2/task-packs.md
Normal file
30
docs2/task-packs.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# Task packs
|
||||
|
||||
Task packs are deterministic, auditable workflows executed by Task Runner.
|
||||
They are distributed as signed bundles and can run online or offline.
|
||||
|
||||
Pack structure
|
||||
- pack.yaml manifest
|
||||
- assets, schemas, docs
|
||||
- provenance and signatures
|
||||
|
||||
Key features
|
||||
- Deterministic plan and execution graph
|
||||
- Approval gates and policy gates
|
||||
- Evidence bundles with plan hashes and artifacts
|
||||
- RBAC scopes for discover, run, and approve
|
||||
|
||||
Determinism and validation
|
||||
- Canonical plan hash and inputs lock file
|
||||
- Stable ordering and fixed timestamps
|
||||
- Fail closed if approvals or hashes are missing
|
||||
|
||||
Publishing
|
||||
- Validate, build, sign, and push to registry or OCI
|
||||
- Offline bundles must satisfy packs offline schema
|
||||
|
||||
Related references
|
||||
- docs/task-packs/spec.md
|
||||
- docs/task-packs/authoring-guide.md
|
||||
- docs/task-packs/runbook.md
|
||||
- docs/task-packs/registry.md
|
||||
Reference in New Issue
Block a user