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). The bar gates live Meridian intelligence (m1_eligible), not one feature name. - M0 harness: private repo
last1-meridianperMERIDIAN_M0_KICKOFF.md. - Crisis strings:
CRISIS_PROTOCOL.mdSection 2 (frozen); live Meridian requires clinical advisor-of-record sign-off on Section 3 blocklist (crisis.blocklist_advisor_signed).
Naming lock (September 2026 — do not overload "M1")¶
| Name | Meaning |
|---|---|
| M0 | Eval harness + crisis wiring (synthetic) |
| M1 | Care-navigation explainer only (prompt/RAG loop). Not matching. |
| Matcher-0 | Net-new care matcher (moat). Parallel build to M1, not an M1 iteration. |
| Service Matches | iOS/API presentation of matcher output (or honest preview) |
m1_eligible |
Safety go-live: one clinical signature gates any live Meridian intelligence to real veterans (explainer or matcher) |
Specs of record: last1-meridian/MERIDIAN_SPEC.md (Service Matches + Matcher-0 + Arc addendum).
What stays in gates vs Meridian repo¶
| Topic | Owner |
|---|---|
| Model architecture, M-gates, Matcher-0, harness code requirements | last1-meridian |
| "Meridian must not block Gate X" product law | This file + AGENTS.md |
| PARKED items referencing Meridian surfaces | PARKED.md |