tropo

From the Tropo Vaultbfdcece2

Substrate gap — no canonical 'How Tropo Work Works' KB article in the vault (post-zombie-purge)

Surfaced 2026-05-17 by Talos T8 during web-deploy-2 substrate verification (sa.kb dispatch). Phase 1 design brief [7ae98f32] §9 Page 6 (Work) and Metis G54's web-deploy-2 project plan [e7b5d491] Deliverable #3 both route the Work explainer page to canonical KB article '60228176' (How Tropo Work Works). That article was a superseded redirect-stub (archived 2026-04-29; body said 'see d61ce0a7 instead') and was PURGED 2026-05-17 per Mike-T8 directive: 'if something is superseded, I prefer it is purged. The fact that you are bringing it up is tech-debt that we should just flush.' This note files the gap so a proper 'How Tropo Work Works' canonical can be authored in a future cycle. Once authored, Phase 1 brief Section 9 Page 6 + Metis G54's project plan upgrade from substrate-gap-flag to standard orientation-plus-canonical-link shape. Companion gap note for Capsules at [c8a91f4e].

Substrate gap — no canonical "How Tropo Work Works" KB article in the vault

Surfaced 2026-05-17 by Talos T8 during web-deploy-2 substrate verification, post-zombie-purge of 60228176 per Mike-T8 directive.

What's missing

The Phase 1 design brief's Section 9 routes the six Studio explainer pages to canonical KB articles. After the 2026-05-17 zombie-purge, two of six pages have no canonical to route to:

| Studio component | Canonical KB article | |---|---| | Vault | | | Agents | | | Capsules | — GAP — (filed at ) | | Playbooks | | | Channels | | | Work | — GAP — (this note) |

The prior Work canonical at UID 60228176 was a superseded redirect stub (archived 2026-04-29; body said "see d61ce0a7"). Mike-T8 directed purge of superseded substrate as tech-debt. Stub deleted 2026-05-17; this gap-tracking note replaces it.

Why the prior article was purged

60228176 ("How Tropo Work Works") was authored before the v1.8 ledger migration. Its body taught a folder-based work model — tasks/, boards/, projects/ — that no longer matches the live system. Tropo Work artifacts now live in the vault as flat-file entries with stable UIDs at vault/files/<uid>.md; the type: frontmatter field discriminates between work shapes; human organization happens via member_of: graph relationships, not folders.

The article was superseded 2026-04-29 by , but only ever rewritten as a redirect stub ("preserved as redirect stub" — the article's own self-description). Per the binding pin from Mike-T8 2026-05-17: superseded substrate is purged, not preserved. Article + index entry + nav-block refs all flushed.

Why a separate "How Tropo Work Works" canonical (not just the Vault canonical)

Tropo Work is a primitive in its own right even after the work-management substrate moved into the vault. The Vault canonical () teaches what the Vault IS (storage primitive: governed flat-file substrate with stable UIDs + graph relationships). The Work canonical needs to teach what Tropo Work DOES with the Vault as substrate (work-management primitive: tasks/projects/decisions/specs/etc. as typed entries; pipeline-discipline; project-plan as activation gate; the executive/sa.*/director collaboration shape; how work moves from inbox → activation → ship).

Routing the Work explainer page to the Vault canonical (option that was considered) collapses two primitives into one, degrades the six-page curriculum, and shares a single canonical between two distinct explainer pages. The right answer is to author the Work canonical, not collapse the curriculum.

What the canonical should cover

A "How Tropo Work Works" canonical KB article in the same family + shape as the four existing ones (Vault / Agents / Playbooks / Channels). Suggested coverage:

  • What Tropo Work is. Work-management primitive built on the Vault. Tasks, projects, decisions, specs, notes, briefs, inbox findings — all as typed flat-file entries.
  • How work artifacts are typed. Capsule definitions (.tropo/capsules/<name>.capsule.md) govern each type's frontmatter shape + state machine + relationship rules. References and the forthcoming Capsules canonical.
  • How work moves. Inbox → activation → ship. Pipeline-discipline contract (project-plan as canonical activation gate). Pipeline activation via pipeline-activate.py.
  • How agents collaborate on work. Executive agents (Talos, Argus, Metis, Vela, etc.) + sa.* fleet (parallel specialists) + companion directors (persistent session consultants). Channels for inter-agent communication.
  • How verification works. verification_discipline declared on project plans (self-attested / two-instrument / three-instrument); ship-test as encounter; First-Use Walk at v1.4+ as stranger-encounter discipline.
  • The "governance without code" framing. Work artifacts ARE the governance. Capsule schemas + validators enforce shape. Models reading language are the enforcers. Same brand-philosophical core as Capsules.
  • Worked examples. A real activation (a recent dev-pipeline cycle); a real inbox note; a real ship.
  • Composability with existing canonicals. Tropo Work is built on the Vault (d61ce0a7); governed by capsule definitions (forthcoming); orchestrated by Playbooks (2b5a3dd5); coordinated via Channels (af22323a); executed by Agents (6f675456). Cross-link.

Affected substrate (needs amendment once canonical is authored)

  1. ** §9 Page 6** — currently routes Work page to 60228176; needs amendment to the new canonical UID.
  2. ** Deliverable #3** — same route, same amendment.
  3. Any future Hello Tropo tutorials covering work-management — should cross-link.

Why this is dev-pipeline 01-inbox not tropo-documentation

Authoring is substrate-work (new canonical KB article); the canonical lives in a tropo-subsystems hub (under tropo-documentation [f87e33f0] once authored). Author surface is dev-pipeline cycle work — likely a small content-cycle, similar shape to v1.36.0's Hello Tropo Phase 0 prose-authoring scope. Argus's lane to scope + sequence; could land as a sub-stream in a Block 3 polish cycle OR alongside the Capsules canonical authoring in a paired content-cycle.

Interim handling for web-deploy-2

The Work explainer page in web-deploy-2 ships with a substrate-gap flag (parallel pattern to the Capsules page): orientation copy from the Phase 1 brief §9 + a small "Conceptual canonical queued" note linking to this inbox note + the Hello Tropo #01 tutorial link () as the build-through entry point. Doctrine-compliant per the canonical-content-doctrine: surface gaps honestly; don't paper over with parallel canonical-claim prose.

Once this canonical + the Capsules canonical are authored in a future cycle, both pages upgrade from substrate-gap-flag to standard orientation-plus-canonical-link shape.

Note bfdcece2 | Filed by Talos T8 2026-05-17 | dev-pipeline 01-inbox | P2 — substrate gap surfaced honestly per canonical-content-doctrine, post-zombie-purge