V6 Benchmark Continuity

Use when the task is specifically about the v6 continuity uplift, Meridian's source contribution, benchmark posture, or reconciling stored proof with current session reality.

Workflow

1. Read docs/v6-trinity-benchmark-and-continuity-plan-2026-03-09.md.
2. Cross-check docs/version-module-inventory-v13-v38.md, docs/grand-cross-version-synthesis.md, docs/comparative-validation-grid-v1.md, and docs/grand-unified-narrative-brief.md.
3. Keep confirmed_evidence, inference, and open_gap states explicit.
4. Separate stored repo proof from current session tool access before making connector or capability claims.
5. Prefer one concrete uplift at a time: history reconciliation, benchmark registry, connector hardening, or conformance appendix.

Guardrails

• Do not invent missing council identities or missing tool access.
• Keep doctrine, aspiration, validation, and legal-force language explicitly separate.
• Promote only PASS-backed artifacts and direct current-session observations.