docs: M3-backend Plan A implementation plan + spec refinements

Browse Source

Adds the bite-sized TDD implementation plan for Plan A (registry mirror +
runtime-config APIs + initial_state/unreviewed semantics; additive only).
Refines the spec with two planning discoveries: the re-stamp must be a
Python startup step (pure SQL can't read DEFAULT_PROJECT_ID), and the
PK-rebuild blast radius justifies splitting M3-backend into Plan A (this)
and Plan B (rebuild + project_id threading + re-stamp, before M4).

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

...

This commit is contained in:

Ben Stull

2026-06-03 22:23:55 -07:00

parent 2cf7db4bff

commit dd72f913a3

2 changed files with 1683 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

docs/superpowers/plans/2026-06-03-m3-backend-plan-a.md

+1634

File diff suppressed because it is too large Load Diff