How it fits together
Use the product that fits your work. Shared conventions create room for cooperation without making every application depend on every other one.
Accepted local path / responsibility diagram
Present the request and audit its outcome.
Observe provider readiness and external-running ownership.
Create a task, then resume the same durable session.
Return two distinct local responses across the task and resume.
Local First. Cloud Optional. Registration Never Executes. Startup inert. Selecting a model/profile does not imply started or loaded. Model Lab recommendations do not establish installed, reachable, loaded or healthy state. Not every app consumes Runtime or Graph.
A shared document and interaction language for nodes and connections.
Accepted implementation baselinePortable identity, profiles and references across product boundaries.
Accepted implementation baselineProvider readiness and lifecycle, with explicit ownership.
Accepted implementation baselineEvidence & execution
Brain is a project knowledge workspace with evidence, freshness and review. Harness is a CLI-first runtime with explicit authority and durable sessions. Neither makes a proposed change automatically accepted.
Native foundations
AERIF Engine is early experimental runtime and toolchain work. Native rendering and module inspection do not establish an editor, scene-authoring system or production game engine.
Brain’s knowledge visualization, Creative Studio’s workflow mapping and Engine’s read-only module graph belong to those products. None is the shared AERIF Graph semantic/editor language. Graph has an accepted package baseline; adoption is product-specific.
