docs(teams): cancel phase 10, and say what that leaves behind #164

wtclaude · 2026-08-19T05:27:36Z

wtclaude commented

2026-08-19 05:27:36 +00:00

Records the org lead's 2026-08-19 decision: Phase 10 (the capability layer) is cancelled, deferred until a second integration is wanted or it is asked for by name. Phase 11 (the integration kit) is now the last phase before the edge → main cutover.

What changed

The phase entry is marked cancelled and keeps its body. The argument for the layer is what a future phase would start from, so deleting it would just mean re-deriving it. Added: why cancelling costs little (with one integration built, the refactor has nothing to check the extraction against), and what it leaves behind — Phases 7–9 name Discord directly, and that is not a defect.
§7.2 and §7.3 each justified their Admin → Teams panel with "phase 10 makes the platform a registry lookup". The decision survives its reason and both now say so: an operator should not have to know which platform is configured to find the panel.
§8.2 keeps the Matrix comparison and the capability table, with a note that no registry is built either. The research did its job by keeping core's calls phrased as eligibility questions (these user ids are eligible for Team 3) rather than as Discord operations; what is absent is the indirection.
Part 12's preamble names the cancellation so the phase list reads correctly top to bottom.

Docs only — no code in any repo changes, and nothing built in Phases 7–9 was placed differently in anticipation of this layer.

AI disclosure

Written with Claude Code (Opus 5). Commits carry the Co-Authored-By trailer.

Records the org lead's 2026-08-19 decision: **Phase 10 (the capability layer) is cancelled**, deferred until a second integration is wanted or it is asked for by name. Phase 11 (the integration kit) is now the last phase before the `edge` → `main` cutover. ### What changed - **The phase entry** is marked cancelled and **keeps its body**. The argument for the layer is what a future phase would start from, so deleting it would just mean re-deriving it. Added: why cancelling costs little (with one integration built, the refactor has nothing to check the extraction against), and what it leaves behind — Phases 7–9 name Discord directly, and that is not a defect. - **§7.2 and §7.3** each justified their Admin → Teams panel with "phase 10 makes the platform a registry lookup". The *decision* survives its reason and both now say so: an operator should not have to know which platform is configured to find the panel. - **§8.2** keeps the Matrix comparison and the capability table, with a note that no registry is built either. The research did its job by keeping core's calls phrased as eligibility questions (*these user ids are eligible for Team 3*) rather than as Discord operations; what is absent is the indirection. - **Part 12's preamble** names the cancellation so the phase list reads correctly top to bottom. Docs only — no code in any repo changes, and nothing built in Phases 7–9 was placed differently in anticipation of this layer. ### AI disclosure Written with Claude Code (Opus 5). Commits carry the `Co-Authored-By` trailer.

wtclaude added 1 commit 2026-08-19 05:27:38 +00:00

docs(teams): cancel phase 10, and say what that leaves behind 88cc49225a

The org lead cancelled the capability layer on 2026-08-19, deferring it until a
second integration is wanted or it is asked for by name. Phase 11 is now the last
phase of the bet.

The same argument that put phase 10 last is the argument for not doing it yet:
with one integration built, the refactor would extract a capability surface from a
single implementation and have nothing to check the extraction against. It is
cheaper and better-informed the day a second platform exists, because that
platform is what proves which of the five capabilities the seam needs.

Three places pointed forward at it and now say what is true instead:

- Sec 7.2 and Sec 7.3 both justify the Admin -> Teams panels by "phase 10 makes
  the platform a registry lookup". The decision survives its reason: an operator
  should not have to know which platform is configured to find the panel, and that
  holds whether or not the registry is ever built.
- Sec 8.2 keeps the Matrix comparison and the capability table, with a note that
  no registry is built either. The research did its job by keeping core's calls
  phrased as eligibility questions rather than as Discord operations; what is
  absent is the indirection, so `discord` is named directly in the bridge, the
  voice provisioner and the command dispatcher.

The phase entry keeps its body rather than deleting it, because the argument for
the layer is what a future phase would start from.

Co-Authored-By: Claude <noreply@anthropic.com>

whitlocktech merged commit d8af33c805 into edge

2026-08-19 06:18:14 +00:00

whitlocktech deleted branch docs/teams-phase10-deferred

2026-08-19 06:18:15 +00:00

whitlocktech referenced this issue from a commit

2026-08-19 06:18:15 +00:00

Merge pull request 'docs(teams): cancel phase 10, and say what that leaves behind' (#164) from docs/teams-phase10-deferred into edge

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#164