project_22spike_S2_mq_meta_q_status_review_2026_05_03

22-spike Q&A-formulation suite — Spike 2 ADD-4 MQ-* meta-Q status review CLOSED outcome-VALIDATED 2026-05-03

Summary

5th 22-spike to close (after Spikes 1 + 12 + 18 + 22). FIRST Group-1-strict-order Spike-2-after-Spike-1 inline-paired closure via Batch A Option B smart-batching. Methodological-foundation spike per plan v1.13 → v1.14 §2 Task 2.

Outcome: outcome-VALIDATED on spirit reading per v3.7 Candidate 3 (STRICT-VS-SPIRIT READING PRE-FLIGHT). Strict reading on as-authored 6-denominator was unreachable (only 3 MQ files exist); strict reading on adapted 3-denominator was MET (2 of 3 stale = 66%); spirit reading correctly produces VALIDATED because the staleness IS what the spike was designed to fix.

Plan defect surfaced

Plan §0 row 62 + Task 2 expected MQ-000..MQ-005 (6 files); actual filesystem inventory was 3 files:

1. MQ-000 — prior-work-revisit-scope.md (ACTIVE; Rich-locked ζ.2 semi-bounded methodology 2026-04-30T16:30)
2. MQ-001 — _pre-refined-prompt/MQ-001-zeta-Q4-reconsideration-PRE-REFINED-PROMPT.md (ARCHIVED; Rich-locked R2 ω.α revert 2026-04-30T21:57; subsequently SUPERSEDED in Full Phase-2-3 Reversion 2026-05-01T20:45)
3. MQ-002 — _pre-refined-prompt/MQ-002-phase-2-closure-build-readiness-dry-run-PRE-REFINED-PROMPT.md (ARCHIVED; Rich-locked Σ.α dry-run 2026-05-01T04:49; subsequently SUPERSEDED in same Full-Reversion)

MQ-003 / MQ-004 / MQ-005 NEVER existed. The plan assumed an MQ-numbering schema that was never instantiated. v3.7 Candidate 6 (Plan-file URL/IRI/filename pre-resolution checklist) detects this defect-class — FIRST defect detected on FIRST applicable plan post-Spike-1 lock validates Candidate 6’s prospective utility.

Plan v1.14 → v1.15 patch candidate flagged for REFERENCE session: change re-status MQ-000..MQ-005 to re-status the actual MQ inventory (currently MQ-000 active + MQ-001 + MQ-002 archived); adjust kill-condition denominator ≥3 of 6 → ≥2 of 3 (66% spirit threshold preserved).

3-MQ inventory scoring against v3.7

MQ	Pre-Spike-2 status	v3.7 score	Action	Post-Spike-2 status
MQ-000 prior-work-revisit-scope	status: approved, maturity: ready, question_status: ANSWERED-CASCADING	SURVIVES v3.7 by category exemption — methodology meta-Qs are categorically exempt from v3.7 spike-discipline (no kill-condition with strict-vs-spirit applicable; v3.7 candidates 1-5+7 don’t apply by category; candidates 6+8 retro-apply but find no defects)	NONE	unchanged
MQ-001 zeta-Q4-reconsideration (archived)	status: answered, maturity: locked, question_status: ANSWERED-R2-CASCADED	STALE — superseded by Full Phase-2-3 Reversion 2026-05-01T20:45 BST but status: field not synced	RE-FRAME (frontmatter only)	status: superseded, question_status: SUPERSEDED-BY-FULL-REVERSION-2026-05-01T20-45, NEW superseded_by: field, v1.1 → v1.2
MQ-002 phase-2-closure-build-readiness-dry-run (archived)	status: answered, maturity: locked, question_status: ANSWERED-CASCADED	STALE — superseded by same Full-Reversion event but status: field not synced	RE-FRAME (frontmatter only)	status: superseded, question_status: SUPERSEDED-BY-FULL-REVERSION-2026-05-01T20-45, NEW superseded_by: field, v1.1 → v1.2

maturity: locked retained on MQ-001 + MQ-002 (describes answer-state at lock-time; distinct from current usability).

Outcome rating disciplines applied

• v3.7 Candidate 3 STRICT-VS-SPIRIT READING PRE-FLIGHT — applied to resolve kill-condition. Strict reading produced denominator-dependent ambiguity (UNREACHABLE on 6-denominator; MET on 3-denominator); spirit reading correctly says outcome-VALIDATED because staleness is what spike fixes.
• v3.7 Candidate 4 SAMPLE-SET + STRUCTURAL-CEILING — retro-applied to identify the kill-condition’s ≥3 of 6 denominator was a structural-ceiling defect (sample set never had 6 elements; structural ceiling is 3).
• v3.7 Candidate 6 PLAN-FILE URL/IRI/FILENAME PRE-RESOLUTION — empirically validated by detecting first defect on first applicable plan post-Spike-1 lock. Candidate 6’s prospective utility now confirmed.
• v3.7 Candidate 7 PARALLEL-SESSION SAFETY — applied via Read-immediate-Edit on plan + arch-state (Batch K SPIKE-RUNNER 4 was concurrently editing both files; v3.34 lands cleanly post-v3.33 Spike 22 closure).
• v3.7 Candidate 8 LOGGING-CONTRACT WITHIN-SESSION CLOSURE — applied (T-file authoring + arch-state row + memory file + MEMORY.md + active-work-log + plan checkbox + plan CHANGELOG + lastmod bump all WITHIN SAME session as T-file authoring).

NOT applicable to MQ-000 (methodology-Q): Candidates 1, 2, 3 (post-hoc only — no kill-condition), 4 (no sample-set), 5 (no TRANSIENT sub-mode possible).

Cascade artefacts

• T-file: ~/off-github/library/projects/inherit/T-spike-mq-meta-q-status-review-2026-05-03.md v1.0 (304 lines / 32.8 KB; 7 body sections + frontmatter + CHANGELOG; 11 honesty caveats); off-github commit pending (Batch A closure batch 1)
• arch-state: v3.33 → v3.34 with NEW §13 row Q-and-A-S2 + Changelog row; docs-strategy commit (Batch A batch 2; pending)
• MQ-001 frontmatter sync: _pre-refined-prompt/MQ-001-zeta-Q4-reconsideration-PRE-REFINED-PROMPT.md v1.1 → v1.2; same docs-strategy commit
• MQ-002 frontmatter sync: _pre-refined-prompt/MQ-002-phase-2-closure-build-readiness-dry-run-PRE-REFINED-PROMPT.md v1.1 → v1.2; same docs-strategy commit
• Plan: v1.13 → v1.14; §0 Spike 2 checkbox ticked; lastmod 12:05 → 11:38; CHANGELOG row added; same docs-strategy commit
• Memory file: this file
• MEMORY.md: index entry to be added (above most-recent entry)
• Active-work-log: CLOSED entry to be added
• NO docs-personal commit (no richard-task disposition — methodological-foundation spike pattern)

Companion pin floor-bumps

• arch_state: v3.33 → v3.34
• refined_prompt: UNCHANGED at v3.7 floor (Spike 2 follows v3.7 disciplines without altering them)
• predecessor_plan: UNCHANGED at v1.9 snapshot
• design_spec: UNCHANGED at v1.0 floor
• outcome_index: UNCHANGED at v1.0 floor

Methodological observations

1. 5th 22-spike to close, after Spikes 1 + 12 + 18 + 22.
2. FIRST Group-1-strict-order Spike-2-after-Spike-1 inline-paired closure via Batch A Option B smart-batching. Pattern: Spike 2 closes fully (steps 1-7 of plan §1.6 + closure verifier + report-back) BEFORE Spike 3 starts.
3. Honesty caveats for body of spike (11 documented at T-file §3 + frontmatter): plan denominator wrong from outset; outcome-VALIDATED is meta-recursive (validates v3.7’s prospective protection by detecting first defect); MQ-000 exemption is by category not content quality; supersession of MQ-001+MQ-002 was determined at Full-Reversion event 2026-05-01T20:45, NOT at Spike 2 time; maturity: locked retained because it describes answer-state at lock-time; no retroactive v3.7 re-rating of historical MQ-001+MQ-002 v1.1 lock-time answers (Spike 1 reconsideration trigger NOT activated).
4. Tier 2 retrieval honestly thin (top sim ≤0.749 with 0 eps-iota T-file matches in top-5 — exactly as plan §1.7 expected for internal meta-Q work; confirms internal-only scope).
5. NO architectural change beyond §13 row + Changelog row + 2 MQ frontmatter syncs; NO master plan / per-repo BUILD-PLAN edit; NO risk register change; NO new SKOS scheme; NO new A-21 CI gate (still 22 per A-130); cross-module primitive count UNCHANGED at 27; module count UNCHANGED at 9.
6. NO richard-task disposition (consistent with Spike 1 — methodological-foundation spikes don’t produce operational obligations).

Reconsideration trigger preserved

If Rich subsequently disagrees with:

• Spirit-vs-strict resolution producing outcome-VALIDATED (would prefer MITIGATED or KILL-CONDITION-MET) → re-frame Spike 2 outcome at next session
• Decision NOT to re-rate historical answers in MQ-001 v1.1 + MQ-002 v1.1 (would prefer retroactive v3.7 re-rating) → Spike 1 reconsideration trigger fires + plan v1.14 → v1.15 + new MQ open
• maturity: locked retention on archived MQs (would prefer maturity: superseded) → trivial frontmatter edit
• Plan defect flag (would prefer plan stays at MQ-000..MQ-005 wording) → plan defect retracted

→ Spike 2 T-file is the starting reference for any of these reconsiderations.