Mesh tier
One phone is the floor. Nearby compute is the ceiling.
The solo app is the product that always matters. The mesh tier is the QVAC upside: a trusted anchor can run a larger MedPsy model while the phone keeps scan and grounding context local.
The phone
Runs camera OCR, normalizes the drug, checks DDInter, and holds the user’s private medication shelf. It can use its own model for the solo path.
The anchor
A nearby laptop or desktop loads a larger MedPsy model and answers delegated explanation requests over the peer path.
Proof boundary
Connected mesh, offline solo.
This distinction is important. The solo app is the offline/privacy story after setup. The mesh tier is a connected capability story and does not pretend to be airplane-mode P2P.
What stays local
OCR result, DDInter lookup, shelf context, and the safety boundary live with the phone.
What delegates
The explanation step can be delegated to a larger peer model when the anchor is available.
What does not happen
No claim of peer-to-peer model pulling, mid-stream failover, or cloud inference as the trust boundary.
Cross-device proof
The demo target.
The mesh evidence is framed as a capability proof: two physical machines, local fallback disabled, and response returned from the provider path.