Architecture

Daily Rule separates authored meaning from procedural transformation and from delivery. Content is authored in themes, selected by dated seasons, loaded into an immutable runtime, and consumed by the engine and API.

The important boundaries

• Content owns what words are available and the editorial metadata attached to them.
• Engine owns how a seed becomes a puzzle and how candidates are evaluated.
• Runtime owns which content and seasons are active for a date.
• API owns transport, caching, observability, and player-facing service behavior.
• Web owns interaction, presentation, accessibility, and product events.
• Documentation records the concepts and operating agreements that connect the parts.

Read Platform components for the package map and Runtime flow for the path from configuration to a served puzzle.