Files

T

veronica f0d2dd9920 docs(W4): stamp kind and status front matter on 104 live documents

Applies the document contract from
docs/plans/2026-08-20_stack-docs-flatten-and-alignment.md section 3, partially:
`kind` and `status` only. `parent` is deliberately held until the flatten in
section 4 lands, so that 127 documents do not have to be re-pointed by hand
when docs/fleet/NORTH_STAR.yaml moves to docs/NORTH_STAR.yaml.

Scope, measured on origin/next at 63069149:

  127 live docs   = all *.md under docs/ minus docs/archive/ minus docs/_old_structure/
  104 stamped     here
   19 held        operator judgement (plan section 9), worklist in the same PR
    3 held        the SUPERSEDED TASKS.md stamps, which cite the moving path
    1 untouched   docs/fleet/FLEET-DOCTRINE.md, already stamped in W1

Kinds applied: 54 guide, 34 record, 9 spec, 6 tracking, 1 projection.
Every row carries a confidence and a one-line rationale in the worklist.

Two collisions with the existing state, both flagged rather than resolved:

1. docs/README.md:150-160 already documents a front-matter convention
   (title/type/audience/status/source_of_truth) with its own allowed values.
   It is applied to 4 of 127 files. Its `status` vocabulary is
   current|draft|deprecated|historical; the new contract's is active|superseded-by.
   The key collides. This commit lets the new contract win and rewrites
   `status: current` to `status: active` on those 4 files, keeping their other
   legacy keys untouched. No code reads any of them: `git grep source_of_truth`
   outside docs/ returns nothing. docs/README.md still prescribes the old
   convention and is an operator row, so it is not edited here.

2. Two of the plan's 20 operator rows are YAML files, not markdown
   (docs/fleet/examples/roster-v2.yaml, docs/openapi-tess.yaml), and the
   contract's front-matter form has no defined meaning for a .yaml document.
   That gap also applies to docs/fleet/NORTH_STAR.yaml, the source of truth
   itself. Raised in the worklist.

A third row from the plan, docs/fleet/north-star.md, no longer exists: W1
renamed it to docs/fleet/FLEET-DOCTRINE.md.

Verification: 104/104 parse with the expected kind and status in front matter;
the check was shown to reject a wrong kind before it was trusted. The diff
removes 4 lines total, all of them `status: current`.

2026-08-20 19:30:25 -05:00

3.6 KiB

Raw Blame History

kind, status

kind	status
tracking	active

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