SecureToolKit advances through explicitly approved security phases. A completed implementation phase is not automatically production-ready, and no phase may silently broaden the trust boundary.
| Area | Status |
|---|---|
| Phases 1–6 protocol | Frozen at PROTOCOL_PHASE_1_6_FINAL |
| Phase 7 architecture | Accepted at PHASE_7_ARCHITECTURE_FINAL |
| Phase 7 Swift implementation | RC1 candidate present on main |
| Phase 7 conformance publication | Candidate process; separate approval required |
| Public GitHub release | In preparation |
| Production readiness | Not approved |
- Tool registry and immutable definition snapshots
- Closed schema validation and canonical request representation
- Authenticated intent, provenance, influence, and Host-boundary binding
- Deterministic policy publication and evaluation
- Structural Authorization issuance and pure validation
- Bound human-confirmation lifecycle and confirmed Authorization validation
Before a public RC can be represented as a long-term baseline, release records, conformance status, supported platforms, security reporting, documentation, and the exact Git identity must agree. Candidate evidence must not represent itself as approved.
| Phase | Intended scope | Status |
|---|---|---|
| 8 — Audit | Privacy-minimized audit contracts and integrity semantics | Not started |
| 9 — Demo | Separate Host-owned non-production integration | Not started |
| 10 — Release | Final API, security, supply-chain, platform, and disclosure gates | Not started |
Phase 8 is not started by repository-publication work. Execution remains outside SecureToolKit in every phase.
The historical Phase 1–6 milestone plan remains available in docs/ROADMAP.md. The Phase 7 engineering program and gates are indexed in docs/README.md.