Files

Jarvis 72d516831f 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)

2026-07-13 08:56:15 -05:00

3.6 KiB

Raw Blame History

Mission Manifest — Tess Interaction Agent

Mission

ID: tess-20260712
Issue: #706
Branch: feat/tess-interaction-agent
Phase: Execution
Current Milestone: TESS-M1 — Runtime contracts and security foundation
Progress: 0 / 5 delivery milestones complete
Status: active
Owner: Mosaic orchestrator; Mos is coordinating fleet authority
Source PRD: docs/PRD.md — TESS-* requirements
Scratchpad: docs/scratchpads/tess-20260712.md

Mission Statement

Ship Tess as Jason's durable Pi-native GPT-5.6 Sol high-reasoning interaction agent for Discord and CLI, with safe visibility/control of Mosaic fleet and transitional Hermes capabilities, while Mos remains the coding/general orchestration authority.

Invariants

Mosaic is the enterprise AI hub; Hermes is a reference migration adapter.
Gateway is the single API surface.
Mos owns coding/general fleet orchestration; Tess owns human interaction, visibility, mediation, and migration access.
Runtime, transport, channel, memory, and external-agent integrations are replaceable adapters.
No source task completes before merged PR, terminal-green CI, independent review, and linked task/issue closure.

Milestones

ID	Issue	Name	Status	Exit gate
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	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

All AC-TESS-* criteria in docs/PRD.md are mapped to reproducible evidence. The final operational test must prove Discord + CLI session continuity, fleet/Mos coordination, authorized Hermes transition capabilities, denial/audit paths, restart recovery, and rollback.

Session History

Session	Date	Runtime	Outcome
S1	2026-07-12	Hermes / GPT-5.6 Sol	User commission captured; Mosaic/OpenViking/session/code archaeology completed; issue #706 created; PRD and task control plane initialized.

3.6 KiB Raw Blame History