docs(tess): sync M4 milestone to in-progress + map TESS-MEM-001 to AC-TESS-05
- MISSION-MANIFEST: TESS-M4 not-started -> in-progress (5 M4 PRs merged: #734/#735/#736/#737/#738; #739 mergeable pending Mos merge; provider-registration linchpin still blocked; M4-V not yet re-fired -> not 'done') - VERIFICATION-MATRIX: fold orphaned TESS-MEM-001 into AC-TESS-05 with operator-memory reachability evidence (M4-W-001 spine: #736 plugin + #739 consumer)
This commit is contained in:
@@ -32,7 +32,7 @@ Ship Tess as Jason's durable Pi-native GPT-5.6 Sol high-reasoning interaction ag
|
||||
| TESS-M1 | #707 | Runtime contracts and security foundation | ready | AgentRuntimeProvider, normalized events/capabilities/errors, RBAC/audit contracts and contract tests merged |
|
||||
| TESS-M2 | #708 | Durable Pi Tess service and state | not-started | GPT-5.6 Sol high service starts, resumes, checkpoints, and passes restart/compaction tests |
|
||||
| TESS-M3 | #709 | Discord and CLI interaction surfaces | not-started | One durable session works through dedicated Discord binding and `mosaic tess`, including attach and approvals |
|
||||
| TESS-M4 | #710 | Fleet, Mos, Hermes, memory, state, and tool plugins | not-started | Fleet/Mos boundary and transitional capability matrix demonstrated end-to-end |
|
||||
| TESS-M4 | #710 | Fleet, Mos, Hermes, memory, state, and tool plugins | in-progress | Fleet/Mos boundary and transitional capability matrix demonstrated end-to-end |
|
||||
| TESS-M5 | #711 | Matrix/native migration, recovery, documentation, and qualification | not-started | Transport parity, migration/rollback matrix, security review, docs, greenfield and deployment validation complete |
|
||||
|
||||
## Success Criteria
|
||||
|
||||
Reference in New Issue
Block a user