Private by default
The software can be open while a person’s production health data remains private and outside public contributor workflows.
Welcome, seeker.
LivePublic websiteLiveOpen-source repository
Your Odyssey Begins Here.
Build your Living Chronicle. Improve your health. Keep the key.
Calypso’s Promise helps people build, understand, and control a high-quality longitudinal account of their health and lived experience through brief, rewarding, narrative-driven participation. The public gateway is live. The planned game turns brief health actions, learning, reflection, and player-confirmed capture into quests on Ogygia.
The path through Ogygia
A Living Chronicle, built one self-chosen step at a time.
Building your record and receiving personal value must remain useful on their own. Research or compensated use is separate, optional, and purpose-specific.
Build your health record
Capture, connect, normalize, validate, and preserve provenance so your Living Chronicle becomes more useful over time.
Improve your health
Receive understandable feedback, learn, conduct safe personal experiments, and choose actions that matter to you.
Control and share in created value
Choose whether and how information contributes to research or compensated opportunities. Secondary use remains separate and purpose-specific.
The Promise
The software is open. The person’s health data is private.
Build your Living Chronicle. Improve your health. Keep the key.
Personal value, meaningful control, explicit uncertainty, and the ability to refuse or return without punishment are product requirements—not optional policy language.
Meaningful refusal
Declining research, sharing, a quest, or a suggested action cannot become punishment, shame, or loss of the core experience.
Player confirmation
AI may propose a draft, but the player confirms, corrects, or rejects it before a domain service can treat it as authoritative.
Correction and exit
Inspection, correction, export, revocation, and deletion are first-class rights rather than rewards for payment or progression.
Evidence before claims
Current capability status
These labels describe what the public evidence supports today. They do not promise production readiness or independent certification.
Public repository
Governance, architecture, roadmap, public contracts, and synthetic evidence are inspectable now.
Inspect the repository (opens in a new tab)Public website
The accepted Next.js public gateway is deployed on the canonical domains with Git-triggered deployment returned to disabled.
Read current status (opens in a new tab)Trust Center and Open Forge
The source-backed Trust Center and Open Forge explanations are public. Forge itself remains bounded local public/synthetic contributor tooling, not a private or production service.
Read the Sprint 8 evidence (opens in a new tab)Roadmap, support, and funding transparency
Public roadmap, support, and canonical funding-transparency views are deployed without activating transactions, private support intake, or sponsor authority.
Inspect the integrated status (opens in a new tab)Phase 0 newsletter signup
The preserve-and-activate path uses the existing private server webhook and Google Sheet for email updates only. Gate #63 remains open until merged deployment and manual verification are accepted.
Review Phase 0 gate #63 (opens in a new tab)Public synthetic prologue
Sprint 9 remains unimplemented. Issue #64 is defining its public-only, no-account, no-real-health-data, temporary-state, refusal, and accessibility boundaries.
Review the pre-Sprint 9 gate (opens in a new tab)Private Living Chronicle product
Accounts, private Chronicles, production Aster, providers, connectors, and consequential workflows remain behind later gates.
Read current boundaries (opens in a new tab)Build in the open
Inspect the work. Challenge it. Help.
The code, architecture, decisions, roadmap, and public synthetic evidence are available now. Private health data, credentials, and protected operational records are not part of public contribution.