PARKED — Do Not Build (with the gate that unlocks it)

Before building anything not in the current gate spec, check here. If it's listed, it's parked.

Capability	Needs	Unlocked at	Why parked
Community-care routing	Community Care Eligibility API	Gate 2 pass	Strengthens routing; not needed to prove the loop
Benefits status / submission	Benefits Claims / Intake API	Gate 3 pass	New domain; Intake also needs org VA-accreditation
Housing hook	Loan Guaranty API	Gate 3 pass	Second/third domain
Appeals	Appeals Status / Decision Reviews	Post-Gate 3	Low-frequency, high-complexity
A second EHR integration	—	Gate 2+ (never in 1.5)	Gate 1.5 is ONE named EHR only
Submitting any form to the VA	Benefits Intake API	Gate 3 pass	Phase 1 delivers consent to providers, not the VA
Any veteran-side reward / token / cash-out / data-dividend	—	Never	Fails Bible test; Anti-Kickback / HIPAA sale-of-PHI
Layers 2–6 (Care Network, insurance, pharmacy, CCN, data revenue)	—	Their own phase	Entire future business; not Phase 1
Cross-ecosystem verification (LastVet × last1.app scoped grant)	Gate 2 exit + related-party papering	Post-Gate 2 (HORIZON)	Eligibility-only orgs; card + deep link only — see gates/HORIZON_CROSS_ECOSYSTEM_VERIFICATION.md
Veteran-facing Meridian (care-navigation explainer, M1)	M0 exit criteria + clinical advisor review	M1 (parallel with Gate 1)	Parallel AI track — see last1-meridian/MERIDIAN_SPEC.md
Provider Meridian (coordination note drafting, gap flags, M2)	M0 exit + Gate 2 entry	M2 (parallel with Gate 2)	Items for human review only — see last1-meridian/MERIDIAN_SPEC.md
Meridian owned weights / outcome intelligence (M3)	Gate 2 exit + counsel-gated de-id pipeline	M3	Specialized models + proprietary adapters — see last1-meridian/MERIDIAN_SPEC.md

Rule: parked items do not get built "while we're in here." If one seems necessary, that is a signal to stop and raise it with Ryan — not to build it.