Skip to content

docs: add upgrade-path + external-infra roadmap; promote Tier 1 to Phase 9#19

Merged
RNT56 merged 1 commit into
mainfrom
docs/promote-phase9
Jun 16, 2026
Merged

docs: add upgrade-path + external-infra roadmap; promote Tier 1 to Phase 9#19
RNT56 merged 1 commit into
mainfrom
docs/promote-phase9

Conversation

@RNT56

@RNT56 RNT56 commented Jun 16, 2026

Copy link
Copy Markdown
Owner

What

Turns the mid-2026 competitive gap analysis into an actionable, codebase-sourced plan, and promotes its Tier-1 workstream into the canonical work queue.

New docs

  • docs/UPGRADE-PATH.md — Tier 1–3 gap-closing task specs in the exact docs/TASKS.md format, every claim file:line-sourced; recaps the protocol, the 7 invariants, the additive-seam pattern, and the three I7 trust classes.
  • docs/ROADMAP-EXTERNAL-INFRA.md — 8 gated EXT-01..08 items (managed cloud fleet, hosting/deploy, in-editor + custom models, remote vector index, enterprise SSO/SCIM/RBAC, central secrets, remote registry, Firecracker microVM), each behind an explicit thesis gate (§0). These cross the "one self-hosted binary / no ambient authority" lines on purpose and stay quarantined.

Promotion into docs/TASKS.md — Phase 9 (P9-T01..T07)

  • P9-T01 multimodal model.Block + provider image translation — the one serialized, contract-level change (· solo; updates docs/ARCHITECTURE.md when implemented).
  • P9-T02 sandboxed headless-browser tool · P9-T03 behavioral verifier (the browser check feeds the verdict — verify stays the sole authority on "done", I2) · P9-T04 SCM/CI webhook → trigger.Signal · P9-T05 gated PR/push GateAction + forge (no autonomous land, I3) · P9-T06 cron triggers · P9-T07 Tier-1 CLI wiring.
  • Added the master-DAG rows + a "later phases" note (Phase 7 shipped; Phase 8 = the concurrency workstream; Phase 9 = this).

Housekeeping

  • Removed a stray merge-conflict ======= artifact in the CHANGELOG [Unreleased] section.

Why it's safe

  • Documentation only — no behavior change. The default binary is byte-identical; every Phase-9 task is itself additive and nil/flag-gated when later implemented.
  • docs/TASKS.md is a contract file (CLAUDE.md §5); this is its dedicated, serialized change — no other open branch's primary Owns is docs/TASKS.md. Rebase before merge to absorb any trivial append from the concurrency (Phase 8) workstream.
  • make verify is green.

Note

Tasks use a real phase number (Phase 9; Phase 8 is reserved for the in-progress multi-agent concurrency workstream). Tiers 2–3 in docs/UPGRADE-PATH.md remain proposals until similarly promoted — each promotion is its own serialized docs/TASKS.md task.

🤖 Generated with Claude Code

…ase 9

Capture the mid-2026 competitive gap analysis as an actionable, codebase-sourced
upgrade path, and promote its Tier-1 workstream into the canonical work queue.

- Add docs/UPGRADE-PATH.md (Tier 1-3 gap-closing task specs in the docs/TASKS.md
  format, with file:line sourcing) and docs/ROADMAP-EXTERNAL-INFRA.md (8 gated
  EXT-01..08 items, each behind an explicit thesis gate).
- Promote Tier 1 into docs/TASKS.md as Phase 9 (P9-T01..T07): multimodal
  model.Block (the one serialized contract-level change), sandboxed browser tool,
  behavioral verifier (verify stays the sole authority on done, I2), SCM/CI
  webhook intake, gated PR/push GateAction + forge (no autonomous land, I3),
  cron triggers, and the Tier-1 CLI wiring.
- Add the master-DAG rows + a "later phases" note; cross-reference the proposal
  doc from Phase 9. Remove a stray merge-conflict ======= artifact in CHANGELOG.

Documentation only: no behavior change, the default binary is byte-identical.
docs/TASKS.md is a contract file; this is its dedicated serialized change.
make verify green.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant