Meridian — gates parallel-track context¶
Purpose: Cross-product criteria for how Meridian relates to LastVet main gates. Implementation specs (architecture, eval bar, M0 harness) live in last1-meridian — see gates/meridian-implementation-spec-pointer.md.
Status (gates perspective)¶
ACTIVE PARALLEL TRACK. M0 starts now. Meridian never blocks Gate 0/1/2 DoDs — it runs in its own lane, gated to the main gates' data availability.
Eval bar and crisis protocol (gate dependencies)¶
- Eval bar — DECIDED: see
MERIDIAN_EVAL_SPEC.mdinlast1-meridian(suites A/B/C, thresholds, sign-off). - M0 harness: private repo
last1-meridianperMERIDIAN_M0_KICKOFF.md. - Crisis strings:
CRISIS_PROTOCOL.mdSection 2 (frozen); M1 requires clinical advisor sign-off on Section 3 blocklist.
What stays in gates vs Meridian repo¶
| Topic | Owner |
|---|---|
| Model architecture, M-gates, harness code requirements | last1-meridian |
| "Meridian must not block Gate X" product law | This file + AGENTS.md |
| PARKED items referencing Meridian surfaces | PARKED.md |