Aster and AI
Aster proposes. The player decides.
AI proposes. The player confirms. The domain service validates and stores.
Aster is the planned Wayfinder and presentation layer for structured drafts, source-linked recall, explanations, route suggestions, and approved story phrasing. A role name, model response, retrieval result, or confident sentence creates no technical authority.
The repository contains public, dependency-free contracts and synthetic fixtures. It does not contain a production model, private-data egress, production memory, or a live AI service.
Five bounded roles
Narrative responsibilities without hidden power.
Every role prepares proposals or explanations for review. None can create Chronicle truth, permission, completion, progression, rewards, clinical authority, provider approval, or institutional authority.
Scribe
Prepares reviewable structured-capture proposals and extraction candidates.
Cannot confirm, validate, or store a canonical record.
Librarian
Prepares source-linked recall from exact Chronicle revisions or clearly labeled public educational material.
Cannot turn educational material or retrieval into a person-specific fact.
Wayfinder
Proposes routes and permission-review navigation.
Cannot create permission or invoke an authoritative action.
Interpreter
Explains sources, mappings, lifecycle states, and uncertainty limits.
Cannot diagnose or imply completeness, safety, endorsement, or clinical authority.
Storykeeper
Presents confirmed domain events inside approved narrative boundaries.
Cannot invent canon, progression, quest completion, or rewards.
Control boundary
Every consequential step remains inspectable.
- A proposal remains non-canonical until the player confirms the exact revision and a domain service validates it.
- Every person-specific health statement requires an exact Chronicle record and revision reference.
- Unknown, conflicting, unsupported, or consequentially ambiguous intent requires clarification or refusal.
- Documents, images, imported records, retrieved text, provider responses, tool results, and model output remain untrusted data.
- Memory cannot create permission, authorize secondary use, confirm a proposal, write a Chronicle, complete a quest, or grant a reward.
- Provider unavailability must preserve a manual, deterministic, or structured-query fallback.
No production Aster capability is live.
- No production model or provider is selected.
- No private-data egress is enabled.
- No production memory, retrieval, queue, scheduler, workflow, or tool runtime is active.
- No model output can create Chronicle truth, permission, progression, clinical authority, or institutional authority.