Skip to content

M-act-2 — Meridian → provider.last.vet (REDIRECTED)

Status: M-act-2b on feature/m-act-2b-synthetic-inbox-wire (iOS) + feature/m-act-2a-provider-inbox (API). last1.app-admin seed HOLD.
Prerequisite: M-act-1 (A) merged.
DoD surface: provider.last.vet deliverer inbox (never last1.app admin).

Two org types

Org type Surface Status
Program orgs (WIN) last1.app Concern path tested
Clinical providers (Harbor) provider.last.vet ROI tested; coordination receive = M-act-2a; Start coordination kickoff = M-act-2b

Gates

Gate Scope DoD
M-act-2a Provider BFF + Coordination page + Harbor→provider bridge + ops seed Provider sees/responds on provider.last.vet
M-act-2b (thin) Start coordination POSTs Harbor kickoff; device polls replies Same thread on device + provider.last.vet
Later last1.app Ω IDs on rows; auto create-from-match Engine-linked respond

Demo account / lane

Pre-users (now): production mode. iOS TestFlight 85 → api.last.vet; respond on provider.last.vet as Test Provider (ryan@last1.enterprises, LV-MEZVC). Staging stays in lockstep; invert to stage-first when real users arrive.

Parked: Provider multi-org-per-account — last.vet-provider/docs/gates/PROVIDER_MULTI_ORG_PER_ACCOUNT.md.

See last.vet-api/docs/runbooks/gate-meridian/M_ACT_2A_PROVIDER_INBOX.md.

Option A (confirmed)

Thin inbox over existing engine. Portal is the VIEW. Not a second SoR (Option B rejected).