Declared-block schema compatibility policy (plugin version vs consumer CLAUDE.md declarations) #52

Open
opened 2026-08-15 12:03:53 +00:00 by jbr870 · 0 comments
Owner

Spawned from finding F-PO-50-2-8 (in-scope-deferrable) on issue #50 during decision D-PO-50-2-13.

Original scope note: Raised by the SREQ expert panel (Solution Architect): once the suite ships as a versioned plugin, a vN+1 skill can read a consumer project's CLAUDE.md declaration written against vN. Nothing today states who bends — no versioning or tolerance rule exists for the declared-block schemas (forge:, observability:, uat:, parallel_dev:).

Disposition rationale: New normative capability, not a migration touch — needs its own design pass (compatibility direction, tolerance rules, maybe a schema-version marker in the blocks). Not needed for 0.1.0: the #50 cutover rewrites consumer declarations in the same window as the install, so plugin and declarations start in lockstep; drift becomes possible from the second release on.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-50-2-8` (in-scope-deferrable) on issue #50 during decision D-PO-50-2-13. **Original scope note:** Raised by the SREQ expert panel (Solution Architect): once the suite ships as a versioned plugin, a vN+1 skill can read a consumer project's CLAUDE.md declaration written against vN. Nothing today states who bends — no versioning or tolerance rule exists for the declared-block schemas (`forge:`, `observability:`, `uat:`, `parallel_dev:`). **Disposition rationale:** New normative capability, not a migration touch — needs its own design pass (compatibility direction, tolerance rules, maybe a schema-version marker in the blocks). Not needed for 0.1.0: the #50 cutover rewrites consumer declarations in the same window as the install, so plugin and declarations start in lockstep; drift becomes possible from the second release on. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/requirements --issue={new-number}` to flesh it out before planning.
Sign in to join this conversation.
No description provided.