Eden OS / HealthOS Workstream Wrap-Up

Objective: Wrap up the Eden OS/Health OS workstream with a clear articulation of current status, scope boundaries, and next steps.

Sources: ELT call transcript (Feb 11, 2026), HealthOS Wrap Up slide, project Gantt, phase deliverables.

1. Slide text: “HealthOS Wrap Up”

Pulled from slide (verbatim):

With Surf, Eden has agreed to honor the end of this contract, and we will be winding down Surf and his two engineers. After that, Eden will be bringing on their India offshore team to take on any further developments.
There are still outstanding items for once the telemetry is hooked up to the intakes: How do we actually bring that into BigQuery so that we can push it through the rest of our data platform? But for the purposes of Eden OS development, our project is complete.

Next steps (from slide):

Close out final payment
Offboard Surf + team

Internal note (Surfield Thomas): Post–close out, is the work to integrate HealthOS into Mixpanel and BigQuery out of scope? Also: they might not want to offboard the team and/or Surf—still being figured out.

2. Current status (from transcript + Gantt)

Where things stand (Feb 11 ELT call)

Topic	Eden’s position	Brainforge position
Contract type	Delivery-bound: $100k for deliverables (MVP). Not time-bound.	Milestone-based; last milestone = delivery. Surf is contracted by hour to Brainforge; BF turned that into fixed project for Eden.
Surf + 2 engineers	Will honor $100 k . H a v e a dd e d o w n r eso u r ces (3 e n g in eer s, Q A, P M D i e g o) —$ 30–40k/mo—Surf directing; want same final delivery.	Won’t extend Surf beyond current runway (already extended to Feb 19). If intake stays in scope for Surf, need ~4 more weeks budget; otherwise will wind Surf down when in-scope work is done.
Intake	MVP = process an order, log in, cancel/manage order, talk to customer care. Diego + Roja (QA) to define exact MVP.	Intake scope changed: started as 10 screens (Remo), now 15+ more; Figmas not finalized; not done by Feb 19. Consider post–10-screen intake work out of scope for Surf; Eden’s team can own intake completion.
Pharmacy + Beluga	—	Pharmacy integrations not done by Feb 19; Beluga API changed; Fermetica—likely use legacy API. Surf’s team sprinting on pharmacy + Beluga to hit deadline.

Outcome of call: Eden to align with Diego (and Roja) on MVP definition; Robert needed answer by ~end of week (Feb 14) to give Surf team heads up. If intake is treated as out of scope for Surf, then delivery = pharmacy integrations + remaining in-scope items → then Surf done; Eden’s India team takes over from there.

Gantt snapshot (as of Feb 24, 2026)

Phase 1 — Foundation & Onboarding: 100% complete.
Phase 2 — Core Integrations: 86%. Pharmacy Integrations (8 providers) 0%, red, due Jan 19. Beluga dev marked 100% Jan 12 but API changed since.
Phase 3 — Zendesk & Data Migration: 100% complete.
Phase 4 — Patient Portal: 63%. Patient Intake Flow 0% (red, due Jan 25). Billing (NMI) 39% (red, due Feb 3). Edit/Update Address 24%. FINALIZE (Check-in Link, Testing & Validation) 0%, red, due Feb 9.

So: in-scope delivery (excluding expanded intake) is partly done; pharmacy, billing, intake (original or expanded), and finalize are the main gaps vs. original dates.

3. Four phases (reference)

Phase	Deliverables	Notes
1 — Foundation & Onboarding	Infra live; CI/CD; integration + portal scoping docs	Done.
2 — Core Integrations (Dec 8–22)	Beluga, billing, pharmacy API implementations; BQ migration plan; intake + portal spec docs. Assumptions: Stripe, NMI, BigQuery access; vendor API docs.	BQ migration done; Beluga changed; pharmacy not complete.
3 — Zendesk & Data Migration	Zendesk in support flows; migrated/validated patient dataset. Assumptions: BQ schema doc by Dec 15.	Done.
4 — Patient Portal Delivery	Patient portal MVP ready for launch; final testing, validation, go-live package. Out of scope: Shipping status, medication arrival notifications.	MVP definition with Eden (Diego/Roja); several items behind (intake, billing, check-in, testing).

4. Synthesis: where we’re drawing the lines

Slide narrative: Contract honored; wind down Surf + 2; Eden India team for further work; Eden OS project complete for our scope; outstanding data question = telemetry → BigQuery (and by implication Mixpanel) for the rest of the data platform.
Staffing / scope tension: Eden sees delivery-bound contract and their own spend; Brainforge sees time/cost guardrails on Surf and considers expanded intake out of scope. Alignment: treat intake (beyond original 10 screens) as Eden’s team; Surf completes pharmacy + remaining in-scope deliverables → close out payment and offboard Surf + team.
Open questions:
- Post-close: Is HealthOS → Mixpanel/BigQuery explicitly out of scope or a separate follow-on? (Surfield’s question.)
- Offboarding: Surf/team may not want to be offboarded; “still being figured out.”

5. Next steps (consolidated)

Eden: Confirm with Diego (and Roja) MVP definition (process order, login, cancel/manage order, support) and confirm intake beyond original 10 screens is Eden’s team.
Brainforge: Once MVP/scope is confirmed, give Surf team clear end date; complete final in-scope delivery (pharmacy, etc.); close out final payment; offboard Surf + 2.
Clarify: In writing or next ELT touchpoint—(a) telemetry → BigQuery (and Mixpanel) = out of scope for this engagement or follow-on; (b) any change to offboarding plan (Surf/team).

You can use this doc as the single reference for “where the situation is at” and feed in any further direction from your side when ready.

6. One slide: Eden discussion

Title: HealthOS wrap-up — where we are & what we need to align on

Where we are

Eden has agreed to honor the end of the contract. We will wind down Surf + 2 engineers; Eden’s India team will take on further development.
For Eden OS development, our project is complete once in-scope delivery is done. One open item: once telemetry is hooked to intakes, how it flows into BigQuery (and the rest of the data platform)—to confirm if that’s this engagement or a follow-on.

Proposed line

In scope for close-out: Pharmacy integrations, Beluga updates, and remaining deliverables from the original fixed scope. Surf’s team completes these → we close out final payment and offboard Surf + 2.
Handoff to Eden: Patient intake beyond the original 10 screens (redesigned flow, 15+ additional screens). Eden’s team (Diego, Roja, engineers) owns completion to MVP. MVP = process an order, log in, cancel/manage order, talk to customer care.

What we need from you

MVP confirmation — Diego (and Roja) to confirm the minimum required for “MVP ready” so we’re aligned on what “done” means for this contract.
Two clarifications — (a) Post-close: is HealthOS → Mixpanel/BigQuery in scope here or a separate follow-on? (b) Any change to timing or approach for offboarding Surf + team?

Next steps

Close out final payment once in-scope delivery is complete.
Offboard Surf + team; Eden India team takes over intake and any further work.

7. Objection-handling table (slide-ready)

Context for all responses: We are not doing any further development at this point. We are waiting on Eden’s engineers (and, where relevant, vendors) to provide what we need to close out or validate. Use this table to address every outstanding item and objection in discussion with Eden.

Objection / outstanding item	Source	Our response
Telemetry → BigQuery / Mixpanel: “Is that in scope after close-out? Will you do it once intake is done?”	Wrap-up; Surfield; Diego (Feb 18)	That work is dependent on their build. We are not doing further development. Once their engineers have intake live and events flowing, we can map and ingest into BigQuery/Mixpanel—we are waiting on them for the source. If they want it as a follow-on, we can scope it separately.
Offboarding Surf + team: “They might not want to be offboarded.”	Wrap-up; Surfield	Contract and runway are at their end. We are not doing further development; handoff to Eden’s India team is the agreed next step. Offboarding stands.
Contract is delivery-bound: “We’re paying for delivery, not time. We need the same final delivery.”	Adam / ELT (Feb 11)	We are drawing the line at the original fixed scope (pharmacy, Beluga, in-scope portal). Expanded intake is out of scope; we are not doing further development. What’s left for “same final delivery” (e.g. intake completion, full E2E) is for Eden’s team; we are blocked until their engineers deliver intake and push orders through the system.
We’ve put our own resources; Surf directs our engineers. “Surf directs Sergio, Ivan; we have daily standups.”	Adam / ELT (Feb 11)	Acknowledged. Our position is unchanged: we are not extending Surf’s team. Eden’s team continues; we are not doing further development on our side beyond close-out.
Intake out of scope: “We can’t test end-to-end without intake. Most of intake is already done.”	Diego (Feb 18)	Intake was redesigned (Beluga changes, 15+ new screens); that’s beyond original scope. We are not doing further development on intake. Eden’s engineers complete intake and push real orders; we are waiting on them to have something we can validate against.
Staging data / can’t validate models: “We need staging data; tables are empty. We need real orders.”	Awaish, Surf (Feb 11, Feb 4); Diego	We are not doing further development. We’ve built models on the schema; validation requires their engineers pushing real orders through staging. We are waiting on them to populate and run flows.
Pharmacy / Beluga API changes: Delays due to vendor or Eden decisions.	Surf (Feb 11, Feb 4)	In-scope work was blocked on their vendors (API changes, pricing) and on their team (IDs, spreadsheets, decisions). We are not doing further development; any remaining pharmacy/Beluga work is for Eden/vendor to complete.
Ryan / Beluga intake updates: “We need Ryan to give us guidelines; we don’t know how many screens.”	Surf (Feb 11)	Intake scope and guidelines sit with Eden (Ryan, Diego). We are not doing further development; we are waiting on their team for final specs and for intake to be completed on their side.
MVP definition: “We need MVP = process order, login, cancel, support.”	Adam / ELT; Diego	MVP completion (full flow, E2E) depends on Eden’s engineers finishing intake and pushing orders. We are not doing further development; we are waiting on them to deliver that.
Data work incomplete until real orders: “We haven’t run a real order through; modeling may need to change.”	Robert (Feb 18)	We are not doing further build development. Data/modeling validation happens once their engineers push real orders through staging; we are waiting on them.
“Did you mention this to Adam? Is he 100% on board?”	Diego (Feb 18)	We’ve communicated the cutoff and options to ELT. We are not doing further development past close-out. Next steps (what’s left after Friday, who does it) need to be aligned between Adam and Eden’s team; we’re clear on our line.

Brainforge Knowledge

Explorer

EDEN_HEALTHOS_WRAPUP