The persistence phase began as a story-save effort. The project paused after defining story state because saving the story alone would have created a durable product state with no coherent account of what the learner had demonstrated or which support they had used.
The revised design gave story and learner state separate domain models, then joined them under one checkpoint identity. The runtime captures both together. The store writes both through one atomic envelope. Restoration accepts the complete pair or preserves it for recovery.
Privacy shaped the contract as much as consistency did. Durable learner state contains minimized structured evidence and scheduling information, not a history of raw answers, transcripts, audio, AI prompts, corrected language, or drafts.
The result is not yet a broad product, but it can preserve one coherent moment of story and learning without overstating what happened inside it.
← Back to HelloStranger