Skip to content

Latest commit

 

History

History
66 lines (53 loc) · 4.21 KB

README.md

File metadata and controls

66 lines (53 loc) · 4.21 KB

Design Document Index

Role

Design documents describe product pressure, domain models, and subsystem possibilities in more detail than the normative architecture. They are inputs, not a second architecture.

For authority, lifecycle, time, persistence, extension, and package boundaries, the Target Architecture Package wins. A design construct becomes an implementation requirement only after it has a normative owner, validation scenario, and roadmap gate.

Current direction

Document Status Normative routing
Reference Game Vision Current product and validation direction Target roadmap and coverage
Engine Core And Game System Boundary Partially superseded design principle System architecture; extensibility
Capability, Affordance, And Actor Interface Reconciled domain input Context and agency; extensibility
Perception And Observation Partially superseded domain input Cognition and agency
Epistemic State Partially superseded domain input Cognition and agency; formal state
Social Institutional Model Active domain exploration Cognition and agency; social gate
Semantic Appraisal And Motivation Active evaluator-internal exploration Cognition and agency
Intent Templates And Planning Partially superseded domain input Cognition and agency
Multi-Resolution Simulation Partially superseded domain input Runtime, persistence, and scale
Physical Simulation Grammar Active gameplay-domain exploration System architecture; gameplay composition gate
Standard World Library Partially superseded design principle Code architecture; extensibility
Typed Effect Primitives Partially superseded vocabulary input Extensibility; owner-specific preparation
World Model Partially superseded domain input Formal and system state owners

“Active” here means useful for continued domain design. It does not mean normative.

Frozen pre-target models

The following files retain historical reasoning and useful examples, but their cross-system contracts have been replaced. Do not extend or implement them as the current architecture.

Document Replaced by
Simulation Core Target package as a whole
Simulation Transition Compiler Formal model, system architecture, and family-specific compiler contracts
Causal Runtime Runtime/persistence model and runtime code architecture
Time Model Normative superdense-time scheduler
Pack Authoring And Semantic Declarations Tiered, family-specific extensibility architecture
Truth, Authority, And Layer Boundaries Formal state partitions and typed gates
Action And Event Model Authority records, domain events, actions, and processes in the target package

These files remain in place because research and idea notes cite them as historical inputs. Their status headers and this index prevent those links from creating a second active architecture.

Partially superseded documents may likewise contain older names such as ActionRequest, CausalTransaction, or EventRecord. Their domain examples remain useful, but those names do not override the current grounded-candidate, prepared-transition, domain-event, and authority-record contracts.

Design rule

A subsystem may be arbitrarily rich internally while preserving a narrow outer contract. Prefer concrete domain types and local algorithms. Introduce a shared abstraction only after at least one vertical scenario supplies its producer, consumer, invariant, failure model, and evidence that the abstraction belongs across a boundary.