Design principles for Aether Engine games and tooling.
Curiosity yields immediate, mid-term, and long-term rewards. Failed attempts still produce information that changes future decisions.
Engine: Mechanic types support on_event → director signal → content opportunity loops.
2. Hidden progression emerges from playstyle
Unlocks follow behavior patterns over time, not menu picks. Rare unlocks require multi-domain mastery.
Engine: BehaviorProfile components and World Director rules drive generation triggers.
Generated content flows: candidate → validate → canonical → versioned history with rollback.
Engine: Canonical package store and append-only event log; runtime consumes approved patches only.
All AI output is structured, schema-valid, and rule-checked. High-impact content can require human review.
Engine: No publish path bypasses validation.
Budget caps, anti-farm logic, and novelty checks protect against exploit-driven inflation.
Engine: Shared RewardBudget rule module across games.
- Single-player package runtime (Phase 1)
- Live content plane + patches (Phase 2)
- AI authoring studio (Phase 3)
- Editor and multiplayer (Phase 4)