feat: reshape Plan / pre-implementation tier (Cluster C)#249
Merged
Conversation
Implements three ratified Wave-1 decisions, designed together because #129 and #57 both alter idd-diagnose Step 3.5 routing: - #129 complexity hard gate: MUST-trigger escalation to Plan when a change touches >=5 files of one interdependent concept OR a shared abstraction. Layered above Layer P, escalate-only; Simple default preserved. - #57 meeting issue type: first-class `meeting` type. Meeting-first routing (deterministic type field, before Layer 1 / Layer V / Spectra / hard gate / Layer P), Phase A/B/C deliberation Strategy, idd-plan skip-chain, and a self-contained close gate (decision->action mapping, no /idd-verify; authoritative deliverable = latest Meeting Plan Phase C, fallback to the diagnose Strategy Phase C, block on no deliverable). - #111 superpowers hand-off: IDD<->superpowers stage-mapping table + a non-binding brainstorming pointer; no self-built staging skill. Verified across 5 rounds of 6-AI adversarial ensemble review: routing-doc drift, stale normative artifacts, meeting-gate mechanism redesign (self-contained gate replacing a leaky whitelist bolt-on), full Spectra-omission sweep, and operational meeting-gate defects. Drift-guards strengthened to lock the mechanisms (not just strings). 25/25 plugin suites pass; spectra validate + analyze clean. Refs #129 #57 #111
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cluster C of the Wave-1 IDD decision drain — three ratified user decisions, designed together because #129 and #57 both alter
idd-diagnoseStep 3.5 routing.What lands
meetingtype. Meeting-first routing (deterministic type field, evaluated before Layer 1 / Layer V / Spectra / hard gate / Layer P), a Phase A/B/C deliberation Strategy, anidd-planskip-chain, and a self-contained close gate (decision→action mapping, no/idd-verify; authoritative deliverable = latest Meeting Plan Phase C, fallback to the diagnose Strategy Phase C, block on no deliverable).deep-integration-over-hardcode).Verification
5 rounds of 6-AI adversarial ensemble review (4 IDD lenses + Devil's Advocate + cross-model Codex). Rounds swept: routing-doc drift → stale normative artifacts → meeting-gate mechanism redesign (self-contained gate replacing a leaky whitelist bolt-on) → full Spectra-omission sweep → operational meeting-gate defects. Drift-guards were strengthened to lock the mechanisms, not just canonical strings.
spectra validate reshape-plan-preimpl-tier— cleanspectra analyze— cleanNotes for review
reshape-plan-preimpl-tier(proposal / design / specs / tasks underopenspec/changes/). After merge I'll run the/idd-closeritual on the three issues (per-issue Closing Summaries) +spectra-archive.Refsonly — close happens via/idd-closeafter merge, never via an auto-close trailer.Refs #129 #57 #111