Platform boundaries · Extensibility contract
Domains extend the platform at composition seams, never by teaching Core their vocabulary
Schema packages carry portable meaning. Generated projections, optional domain logic and richer presentation stay in their domain, while applications choose the capabilities they host.
Platform boundaries · Extensibility contract
Domains extend the platform at composition seams, never by teaching Core their vocabulary
Schema packages carry portable meaning. Generated projections, optional domain logic and richer presentation stay in their domain, while applications choose the capabilities they host.
What this view establishes
The architectural commitments
- Core owns portable mechanics, not Skate, Bird, media-model or product vocabulary.
- Schema is the cross-platform source of truth; generated types are projections rather than a competing contract.
- Applications are the only place where storage, transport, domain logic and presentation are deliberately assembled.
Directed dependency matrix and composition stack
Domain-neutral platform
NeoStoryCore
Wire envelopes, descriptors, dynamic records and pure executors
Generic capabilities
Stores, sync, HTTP, processing, game kernel, UI and sign-in
Schema packages
Stable IDs, inheritance, fields and relationships
Generated projections
Swift types and the descriptor-driven web snapshot
Domain contributions
Composition roots
Directed relationship matrix
Blank cells mean no relationship is claimed in this view; they are not evidence of independence.
| From ↓ / to → | Generic capabilities | Generated projections | Reusable Media domain | Skate domain | Bird reference domain | Contrive Skate apps | Web composition | Independent fork |
|---|---|---|---|---|---|---|---|---|
| NeoStoryCore | 01 implemented | · | 03 implemented | · | 05 implemented | · | · | · |
| Schema packages | · | 02 implemented | · | · | · | · | · | · |
| Reusable Media domain | · | · | · | 04 implemented | · | · | · | · |
| Skate domain | · | · | · | · | · | 06 implemented | 07 implemented | · |
| Bird reference domain | · | · | · | · | · | · | · | 08 declared |
| Generic capabilities | · | · | · | · | · | 09 implemented | 10 implemented | · |
| Generated projections | · | · | · | · | · | · | · | 11 declared |
Connections and evidence
Open the 11-relationship source key
Numbers set an explanatory reading order. They do not measure runtime timing.
Connections and evidence
Open the 11-relationship source key
- 01implemented
NeoStoryCore→Generic capabilities
portable boundary
- 02implemented
Schema packages→Generated projections
projects
- 03implemented
NeoStoryCore→Reusable Media domain
imported by
- 04implemented
Reusable Media domain→Skate domain
reused by
- 05implemented
NeoStoryCore→Bird reference domain
imported by
- 06implemented
Skate domain→Contrive Skate apps
registered at root
- 07implemented
Skate domain→Web composition
explicit adapter
- 08declared
Bird reference domain→Independent fork
worked template
- 09implemented
Generic capabilities→Contrive Skate apps
selected by app
- 10implemented
Generic capabilities→Web composition
descriptor driven
- 11declared
Generated projections→Independent fork
same contract toolchain
Connections and evidence
11 directed, source-backed relationships
Numbers set an explanatory reading order. They do not measure runtime timing.
- 01implemented
NeoStoryCore→Generic capabilities
portable boundary
- 02implemented
Schema packages→Generated projections
projects
- 03implemented
NeoStoryCore→Reusable Media domain
imported by
- 04implemented
Reusable Media domain→Skate domain
reused by
- 05implemented
NeoStoryCore→Bird reference domain
imported by
- 06implemented
Skate domain→Contrive Skate apps
registered at root
- 07implemented
Skate domain→Web composition
explicit adapter
- 08declared
Bird reference domain→Independent fork
worked template
- 09implemented
Generic capabilities→Contrive Skate apps
selected by app
- 10implemented
Generic capabilities→Web composition
descriptor driven
- 11declared
Generated projections→Independent fork
same contract toolchain
What this view establishes
The architectural commitments
- Core owns portable mechanics, not Skate, Bird, media-model or product vocabulary.
- Schema is the cross-platform source of truth; generated types are projections rather than a competing contract.
- Applications are the only place where storage, transport, domain logic and presentation are deliberately assembled.
Follow the live system
Move from explanation to inspection
The Atlas is static and source-backed. The Observatory shows authenticated environment state.
18 repository sources behind this view
Explorer/app/page.tsxExplorer/tests/domain-boundary.test.mjsPackage.swiftREADME.mdSources/ExplorerExport/main.swiftSources/MediaDomain/MediaDomain.swiftSources/SchemaGen/main.swiftdocs/forking.mddocs/package-architecture.mddomains/README.mddomains/bird/schema/bird-domain.schema-package.jsondomains/skate/Apps/SkatePlay/project.ymldomains/skate/schema/skate-domain.schema-package.jsondomains/skate/web/game-kernel.tsfixtures/schema-set.jsongenerate.shschema/core.schema-package.jsonschema/media-domain.schema-package.json