PlannedProduct direction; not a playable release

How it works

A useful Chronicle, built one voluntary step at a time.

The planned experience is an illustrated narrative and decision game, not a generic dashboard with fantasy decoration. A typical session is designed to last roughly three to eight minutes and always provides a clear stopping point.

This page explains accepted product direction. Accounts, private Chronicles, production capture, Aster, quests, and gameplay are not live.

A planned daily route

Arrive, choose, confirm, and leave freely.

The route adapts to goals, context, accessibility needs, and available data. It may be replaced, deferred, or rejected without punishment.

  1. Arrival

    Return to the Hearth for a clear briefing and an honest stopping point.

  2. Wayfinder route

    Aster may propose two or three relevant quests. The player may replace, defer, or reject the route without punishment.

  3. Capture or action

    Tap, type, speak, photograph, import, learn, move, reflect, or review according to the person’s context and accessibility needs.

  4. Confirmation

    Extracted information remains a reviewable draft until the player confirms, corrects, or rejects it.

  5. Feedback

    The Chronicle becomes more useful and the planned island experience responds without treating health status as moral worth.

  6. Departure

    See what changed, what was learned, which permission was used, and what may come next before choosing to leave.

Authority boundary

AI may assist. Deterministic services decide.

Generative presentation cannot decide eligibility, permission, completion, rewards, safety, unlocks, canon, or story order.

Deterministic responsibilities

  • Eligibility
  • Permissions
  • Completion
  • Rewards
  • Unlocks
  • Safety gates
  • Story revelation order
  • Canon facts

AI-assisted presentation

  • Input-extraction drafts
  • Clarifying questions
  • Plain-language explanations
  • Personalized route presentation
  • Source-linked recall summaries
  • Dialogue phrasing inside approved scene boundaries

Failure and return

No broken-streak punishment.

A missed day may create a gentle Broken Lantern return path: resume, reduce the route, change reminders, or reconsider the goal. Health status, body size, symptom absence, or perfection never becomes moral worth.

Core paths must remain available without AI

  • Manual capture
  • Structured recall
  • Permission review
  • Correction
  • Export
  • Deletion
  • Ordinary play