Where the course ends
If you have worked through the level, you now own a small system that nobody sold you: your data, your database, your API, your tools, running at the edge for about nothing a month. This closing lesson is about what that is actually worth — and where the honest limits are.
What you built
- A zero-build static dashboard on Cloudflare Pages.
- A D1 schema with a table per domain, UTC throughout, and an idempotency key on anything an import touches.
- An API of Pages Functions with one middleware, default-deny, and an allowlist of public reads that redact on the server.
- An MCP server of narrow, purpose-built tools, validated at the boundary and logged on every call.
- Two authentication paths — scoped OAuth for third parties, a bearer token for you — arriving at one check.
- A composite score that reports its own coverage, decays when stale, and refuses to invent a number.
Now the transfer — which was always the point
The health tracker was the exercise. Look at what you do at work and notice how little changes:
| Health OS | At work | Same lesson |
|---|---|---|
| Watch, scale, cuff → one database | Bank, invoicing, e-shop → one database | Raw first; aggregate, never replace |
| Public trends, private clinical detail | Public price list, private margins | Redact on the server, never in the UI |
log_weight as a tool | create_invoice as a tool | Narrow tools cannot be misused |
| Assistant connected by scoped OAuth | A contractor's tool, connected the same way | Revocable beats convenient |
| One wellbeing score | One “how is the month going” number | Say what the number does not know |
| Re-running an import is boring | Re-running a bank import is boring | Idempotency is not optional |
The second column is where the money is. The first column is where you were allowed to be wrong while you learned it — which is exactly the argument from lesson 8.1, arriving back where it started.
What this level deliberately does not cover
Stated plainly, so nobody discovers a gap the hard way:
- Anything clinical. No interpretation of readings, no reference ranges, no advice. The index is an instrument panel, not an opinion about your health.
- Sharing with other people. One user, several devices. Multi-user changes the access model fundamentally — and doing it badly with health data is the kind of mistake that does not stay personal.
- Regulated handling. The moment data about someone else's health lands in your database, you are in a different legal world. This level assumes it is yours.
- Scale. Edge functions have short execution limits and D1 is SQLite. For one person over years it is close to ideal; for a product it is not the shape you would pick.
- Native apps. Getting data out of a phone is platform work, and it changes with every OS release. The pipeline downstream of the export is what this level teaches.
Be careful with your own creation
When to stop and ask instead
There is no shame in this, and it is often the cheaper answer. A paid consultation makes more sense than another weekend when:
- You need it working by a date, and the date matters.
- It has to plug into systems you did not build and cannot change.
- You are past the point where the learning is the reward and the thing is now simply in the way.
- You want a second opinion on an access model before real data goes into it — the one decision where being wrong is expensive and quiet.
If that is where you are, take it to support and describe the situation plainly. Consultations are taken selectively, on cases that are interesting — that is an honest constraint, not a sales technique.
If you would rather keep going alone
Good. That was the intention. Three directions that follow naturally from here:
- Automate one import end to end — no manual export step — using Level 6. This is where the system stops needing you.
- Let agents keep it healthy with Level 4: a watchdog that notices an import produced nothing, a nightly check that the numbers still reconcile.
- Point the whole pattern at something at work. Pick the least dangerous process you have. Build it the way you built this. Notice how much less frightening it is the second time.