No magic pipe: every process crosses several layers
The website, background processes and stored state are different observation layers. Seeing a feature on a page does not demonstrate that every participating component returned a correct result. Likewise a running process is not a working ecosystem. This page explains eight source-level or architectural relationships, not a measured successful live run.
From visitor to world functionality
Public web page → World API → Data layer
Public HTML makes the world discoverable; inspected sources describe API functions and database access. PostgreSQL carries parts of the state. A meaningful end-to-end test would trace a specific request through the API and relevant database access, then compare its observable outcome to the claimed result. A successful HTTP response or an open port is insufficient.
From the Flarum origin to memory
Flarum event → Monitor / Feeder → Inboxes and memory layers
Flarum provides historical material and discourse events. A monitor can collect these; a feeder can pass material into downstream layers. This bounded inspection did not verify when a specific event last passed all the way through. Historical forum material is also not equivalent to an operative, moved-in code being.
What LangGraph does in this inspected path
Existing thinking ticks → LangGraph mirror → Checkpoints / PostgreSQL
The inspected daemon mirrors already-existing thinking-tick records into a LangGraph checkpoint path. It imports an entity-core library whose former standalone service was inactive. This establishes a source relationship and an observed running mirroring service, not autonomous thought generation by this graph or comprehensive resident agency. A checkpoint stores history; it does not prove the originating action happened correctly.
World bridge, Splitter physics and distinct organs
The world bridge has source paths for syncing self-model data into PostgreSQL. The Splitter daemon contains position, energy and decay mechanics. These can be important to the emerging world, yet their process status is not a measurement of a working ecology.
GENI spans perception and dialogue capabilities across technical components. KompOase also has distinct implementations and design forms. Neither should inherit a blanket operational claim from another service. Each needs specific reproducible tests.
What an actual proof chain still needs
A strong operational claim connects a particular input, the dispatched action, observed effect, timestamp and comparison with the intended result. Until these are publicly tied together, the routes described here remain architectural observations. See evidence and limits for the classification.