Engines · Game engine and authority
A pure game kernel explains every judgment; the authority decides what joins history
Versioned rules and admitted evidence enter a deterministic interpreter with no network, media, authorization, or UI dependencies. The gateway serializes commands, appends the resulting events atomically, and replicas rebuild the same state from accepted history.
Engines · Game engine and authority
A pure game kernel explains every judgment; the authority decides what joins history
Versioned rules and admitted evidence enter a deterministic interpreter with no network, media, authorization, or UI dependencies. The gateway serializes commands, appends the resulting events atomically, and replicas rebuild the same state from accepted history.
What this view establishes
The architectural commitments
- The kernel can be tested and reproduced from canonical inputs because it has no infrastructure side effects.
- A client may forecast a command locally, but only an authority-accepted event advances shared history.
- Explanations and state hashes are part of the durable receipt, not UI decoration reconstructed later.
- The Games tab on the web (2026-09-09) lists a person's own games and turns with the clip each turn was proven by, read as that person: the gateway's ownership scoping is the only 'mine', and every outcome is the kernel's accepted event, never re-judged in the browser.
Kernel boundary and command/event flow
Inputs
Ruleset revision
Pinned mechanics, scoring and terminal conditions
Game session
Seats, phase, ruleset and accepted-event head
Evidence submission
Reviewed semantic facts and exact revision pins
Game command
Canonical intent against an expected state hash
Pure game kernel
Admission and atomic resolve
Durable history
Command admission, pure interpretation and accepted event flow
Connections and evidence
Open the 10-relationship source key
Numbers set an explanatory reading order. They do not measure runtime timing.
Connections and evidence
Open the 10-relationship source key
- 01implemented
Ruleset revision→Deterministic interpreter
pins behavior
- 02implemented
Game session→Game command
names expected head
- 03implemented
Evidence submission→Deterministic interpreter
admitted facts
- 04implemented
Game command→Admission boundary
submits
- 05implemented
Admission boundary→Atomic resolution
authorized intent
- 06implemented
Domain kernel registry→Atomic resolution
selects kernel
- 07implemented
Atomic resolution→Deterministic interpreter
evaluates once
- 08implemented
Deterministic interpreter→Judgment + explanation
explains
- 09implemented
Judgment + explanation→Append-only events
appends atomically
- 10implemented
Append-only events→Replay projection
replays
Connections and evidence
10 directed, source-backed relationships
Numbers set an explanatory reading order. They do not measure runtime timing.
- 01implemented
Ruleset revision→Deterministic interpreter
pins behavior
- 02implemented
Game session→Game command
names expected head
- 03implemented
Evidence submission→Deterministic interpreter
admitted facts
- 04implemented
Game command→Admission boundary
submits
- 05implemented
Admission boundary→Atomic resolution
authorized intent
- 06implemented
Domain kernel registry→Atomic resolution
selects kernel
- 07implemented
Atomic resolution→Deterministic interpreter
evaluates once
- 08implemented
Deterministic interpreter→Judgment + explanation
explains
- 09implemented
Judgment + explanation→Append-only events
appends atomically
- 10implemented
Append-only events→Replay projection
replays
What this view establishes
The architectural commitments
- The kernel can be tested and reproduced from canonical inputs because it has no infrastructure side effects.
- A client may forecast a command locally, but only an authority-accepted event advances shared history.
- Explanations and state hashes are part of the durable receipt, not UI decoration reconstructed later.
- The Games tab on the web (2026-09-09) lists a person's own games and turns with the clip each turn was proven by, read as that person: the gateway's ownership scoping is the only 'mine', and every outcome is the kernel's accepted event, never re-judged in the browser.
Follow the live system
Move from explanation to inspection
The Atlas is static and source-backed. The Observatory shows authenticated environment state.
19 repository sources behind this view
Explorer/app/page.tsxSources/NeoStoryClient/GameAuthorityResolveCoordinator.swiftSources/NeoStoryGameKernel/Evidence.swiftSources/NeoStoryGameKernel/GameAuthorityContract.swiftSources/NeoStoryGameKernel/GameInputs.swiftSources/NeoStoryGameKernel/GameInterpreter.swiftdocs/deployment.mddocs/game-application-roadmap.mddocs/game-authority-wave2.mddocs/game-kernel-g0.mddocs/game-lab.mddomains/skate/web/game-kernel.tsfixtures/game-kernel-g1/README.mdfixtures/game-kernel-g1/conformance.jsongateway/src/neostory_gateway/authentication.pygateway/src/neostory_gateway/game_authority.pygateway/src/neostory_gateway/kernel_registry.pygateway/tests/test_game_authority_postgres.pyschema/game-domain.schema-package.json