Core flows · Signature flow
Evidence becomes playable only after its trust boundary is explicit
Media, predictions, review, semantic events and game outcomes remain separate durable facts. That separation lets Contrive explain a turn, replay it deterministically and improve its assistance without rewriting history.
Core flows · Signature flow
Evidence becomes playable only after its trust boundary is explicit
Media, predictions, review, semantic events and game outcomes remain separate durable facts. That separation lets Contrive explain a turn, replay it deterministically and improve its assistance without rewriting history.
What this view establishes
The architectural commitments
- Predictions can assist a player or reviewer but cannot silently become accepted truth.
- A semantic performance is distinct from every camera clip that depicts it.
- Game state is replayed from append-only accepted events, so assistance can evolve without changing the result.
Evidence transformation flow
- 01
02 Source
- 02
03 Proposals
- 03
01 Explicit review
review-actionimplementedHuman review
Accept, edit, reject or defer
- 04
02 Accepted evidence
- 05
03 Play and history
Source transitions through the human truth boundary
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
Captured media→ProcessingGraph run
exact source
- 02implemented
Captured media→Verified local store
verified bytes
- 03implemented
ProcessingGraph run→Proposal + provenance
suggests
- 04implemented
Proposal + provenance→Human review
never auto-promotes
- 05implemented
Artifact lineage→Semantic performance
cited provenance
- 06implemented
Human review→Semantic performance
accepts or edits
- 07implemented
Semantic performance→Evidence submission
pins
- 08implemented
Evidence submission→Deterministic judgment
admitted facts
- 09implemented
Deterministic judgment→Append-only game event
atomic resolve
- 10implemented
Append-only game event→Reconciled replicas
accepted history
Connections and evidence
10 directed, source-backed relationships
Numbers set an explanatory reading order. They do not measure runtime timing.
- 01implemented
Captured media→ProcessingGraph run
exact source
- 02implemented
Captured media→Verified local store
verified bytes
- 03implemented
ProcessingGraph run→Proposal + provenance
suggests
- 04implemented
Proposal + provenance→Human review
never auto-promotes
- 05implemented
Artifact lineage→Semantic performance
cited provenance
- 06implemented
Human review→Semantic performance
accepts or edits
- 07implemented
Semantic performance→Evidence submission
pins
- 08implemented
Evidence submission→Deterministic judgment
admitted facts
- 09implemented
Deterministic judgment→Append-only game event
atomic resolve
- 10implemented
Append-only game event→Reconciled replicas
accepted history
What this view establishes
The architectural commitments
- Predictions can assist a player or reviewer but cannot silently become accepted truth.
- A semantic performance is distinct from every camera clip that depicts it.
- Game state is replayed from append-only accepted events, so assistance can evolve without changing the result.
Follow the live system
Move from explanation to inspection
The Atlas is static and source-backed. The Observatory shows authenticated environment state.
14 repository sources behind this view
README.mdSources/MediaCapture/CaptureTimebase.swiftSources/NeoStoryGameKernel/GameInterpreter.swiftSources/NeoStorySQLite/LocalBlobStore.swiftdocs/apple-ingestion-slice.mddocs/cross-platform-sync.mddocs/game-application-roadmap.mddocs/game-authority-wave2.mddocs/game-kernel-g0.mddocs/processing-graph-foundation.mddocs/skate-video-annotation-product-slice.mddocs/v3-measurement-workbench.mddomains/skate/schema/skate-domain.schema-package.jsonfixtures/game-kernel-g1/README.md