The Technical Roadmap
Meets the Patent
How the four-phase build delivers every technical element of the closed-loop biological control patent.
Closed-Loop Biological Control Architecture with Weighted Arbitration & Logistics API Orchestration · Leadership review · Aug 2026 · v1
One engine, many verticals — and the patent is the engine
Ingest wearable signals → normalise → arbitrate by weighted priority → act — through the app and through provider APIs. The patent claims exactly that loop, so every roadmap phase builds out the claimed invention, not merely toward it.
1 · Blankets the MVP core
The ingestion → variance → dual-gate → weighted-arbitration → block-the-workout loop is claimed verbatim in the three independent claims. Strongest protection — and it ships first.
2 · Already reaches Phase 4
The clinical-routing spine — provider registry, quota ledger, allocation token, fast-track booking — sits inside the independent claims. Protected today, years before Care ships.
3 · One clean gap
The Phase 3 human layer and multi-user model are not yet claimed. One continuation closes it.
Bottom line: all 35 distinct technical elements are delivered by the roadmap — 18 in the MVP alone.
A seven-layer architecture — the patent’s Fig. 4 is the Weyos engine
Every claim element lives on one of these layers — which is why patent coverage maps cleanly onto the phases.
20 claims, triple-secured
METHOD · Claim 1
The process itself.
SYSTEM · Claim 9
Memory + processor configured to run it.
MEDIUM · Claim 17
Instructions on a non-transitory medium.
Three independent claims each recite the full loop, differing only in legal form. + 17 dependents add archetype weighting, lab context, prediction, fulfilment payloads, and closed-loop learning.
20 claims → 35 distinct technical elements. The core ~21-element loop is protected three times over — as method, system, and medium.
100% of patent elements are on the roadmap
| Where it’s delivered | Elements | Share |
|---|---|---|
| Phase 1 — Guardian Core (MVP) | 18 | 51% |
| Phase 2 — Deepen signal & action | 8 | 23% |
| Cross-cutting — Prediction & Feedback | 4 | 11% |
| Phase 4 — Weyos Care (claimed today) | 5 | 15% |
| Total | 35 | 100% |
technical elements delivered. More than half ship in the first release. Nothing in the claims is unbuildable.
Four phases — each one builds claimed capability
Native app + 16-rule / 5-layer arbitration engine. Builds the claimed core.
Lab Test Data + Food Health & Budget. Builds contextual diagnostics + API fulfilment.
Loneliness & Connection + Circle. Beyond current claims — continuation target.
Elderly care. Builds out the already-claimed clinical-routing spine.
Phase 1 delivers the inventive core — 18 elements
402 · Ingestion — 5
Async streaming ingest · HRV (first sensor) · skin-temperature (second) · in-memory time-series store · standardized variance metric = (current − trailing mean) ÷ historical SD.
404 · Archetype — 2
Map user to a classification archetype · derive the normalized weight vector.
408 · Weighted arbitration — 11
Dual-gate evaluation · dissonance score · clinical-anomaly registry match · priority-state record · block a scheduled instruction via the delivery-state field · dispatcher lock · block the workout notification · clinical lock-out · mandatory interface · cryptographically-signed override.
The strongest, broadest protection in the filing — and it ships first.
Phase 2 delivers context + real-world action — 8 elements
406 · Contextual Diagnostics — 3
Contextual-modifier set built from functional diagnostic inputs, a lifestyle questionnaire, and stated lifestyle goals. → Lab Test Data module + onboarding.
412 · Execution / API orchestration — 5
Generate an API fulfilment payload from the telemetry · transmit it to an external provider · payload carries a user identifier, one or more products, and a delivery mode. → Food Health commerce + food-budget backbone.
This is where the recommendation becomes a real order.
Cross-cutting tracks deliver the moat — 4 elements
410 · Predictive Inference — 1
The override is driven by a prediction of a stress event before physiological onset — the “predict the crash” science.
414 · Recursive Feedback — 3
Receive additional biometrics · compute a recovery delta · adjust the weight vector from it — closed-loop personalisation.
Not tied to one phase — platform tracks that deepen across Phases 2–4, fed by every vertical’s data.
The clinical-routing spine — protected now, built at Phase 4
- 1Activate a clinical-routing handshake
- 2Match the user’s region against a provider-network registry
- 3Query a live quota ledger for a reserved-allocation slot
- 4Issue an allocation token when a slot is free and eligibility is met
- 5Otherwise transmit a fast-track booking payload to the provider
Strategic point: the hardest, most valuable escalation logic is protected now — roughly three years before it ships.
Every layer, every element, mapped to a phase
| Layer | Function | Elements | Delivered in |
|---|---|---|---|
| 402 | Ingestion & Normalization | 5 | Phase 1 |
| 404 | Archetype Baseline | 2 | Phase 1 |
| 408 | Weighted Conflict Resolution | 11 | Phase 1 |
| 406 | Contextual Diagnostics | 3 | Phase 2 |
| 412 | Execution (fulfilment) | 5 | Phase 2 |
| 410 | Predictive Inference | 1 | Cross-cutting |
| 414 | Recursive Feedback | 3 | Cross-cutting |
| 412b | Clinical-Routing Handshake | 5 | Phase 4 (claimed now) |
35 / 35 elements covered.
Where the roadmap runs ahead of the patent
Every patent element is built. The reverse direction has a single gap:
Phase 3 — the human layer
Psychosocial signals, mood check-ins, the trusted-contact “Circle,” and social interventions are not yet claimed.
Multi-user & permissions
Load-bearing for both Phase 3 and Phase 4 — the role-scoped account and consent model is not yet claimed.
Action
File one continuation covering the social/emotional layer, consent-scoped contact routing, and the multi-user model. They share a substrate and are best drafted together.
Why the filing holds up
✓ Technical-effect framing
Claims are grounded in concrete architecture — in-memory store, priority store, delivery-state field, dispatcher lock — the language that carries software-health inventions past eligibility challenges.
✓ Triple statutory lock
The core loop is claimed as method, system, and medium — three independent routes to the same protection.
✓ Astro deliberately unclaimed
The elemental / cosmic layer appears nowhere in the claims, keeping the filing inside a defensible “validated biometrics” envelope for clinical, regulatory, and investor audiences.
What to take away
The roadmap builds the IP. All 35 technical elements are delivered — 18 in the MVP alone.
The escalation spine is already protected. Years ahead of the Care product line.
Keep the MVP build congruent with claim 1. Preserve the in-memory store, priority store, and delivery-state field so product and claims stay aligned.
File one continuation. Close the only gap — the human layer + multi-user model.
Coverage read to guide build and filing decisions — not a legal opinion on validity or infringement.