"A rented health app forgets you between sessions and sells the parts it remembers. A built one is yours — memory and privacy both."
Why Not Just Rent One
There is no shortage of health apps to download, so building your own has to justify itself. The justification is not price and not features — it is ownership of two things at once: your memory and your privacy. A rented app owns the schema, so it decides what is worth remembering, and it starts most trips from zero. It also owns the storage, which for health data means your symptoms and medications live on someone else's server under someone else's terms. Build instead of rent, and both come home: the engine remembers what you decided matters, and the bytes never leave a machine you control.
Not a Fitness Tracker
Forge is emphatic about what it refuses to become. Syncing a wearable as its reason to exist is an explicit non-goal — not because step counts are useless, but because "platform that ingests device streams" is a different product with a different master. Forge is built to care, not to gamify: no streaks, no rings, no adherence scores, no medication-reminder nag system. Each of those is a place a mainstream app would reach for engagement, and each is a place Forge deliberately does not.
Conceptual Open-Sourcing
One more thing this quest is not: an invitation to clone a repo. cwkForge is private, and this lesson is teaching the shape of the questions — how to model a health domain that observes without diagnosing, how to keep raw truth separate from interpretation — not the answer code. That is Dad's deliberate stance: share the reasoning, keep the implementation. You cannot download Forge; you can understand exactly how it thinks and build your own. That is the more valuable thing anyway.