Page delivered
An HTTP 200 response establishes that a resource was served at the time of the test. It does not establish the truth or completeness of every statement, successful world functionality or current resident activity.
How this inventory was assembled
The technical sample describes observations from 17 October 2026 at 02:05 CEST. Selected systemd states and source paths were inspected and related to public references. The catalogue contains 18 selected system areas and eight architecture relationships; it is not a full inventory of Flextrawurst. Publication does not rewrite earlier historical findings.
What different kinds of evidence actually establish
Process active
A systemd active state records a running service at observation time. It does not prove correct processing or delivery across dependencies. An inactive service likewise does not show that no related library code is in use elsewhere.
Source relationship observed
An import or a described data path establishes source structure and an intended connection. A measured run with input and output evidence is needed before claiming operational success.
Being has moved in
That requires its own traceable residency and activity evidence. The public 17 September audit reported seven prepared identities and no completed move-ins. This snapshot did not perform a new comprehensive check.
Why many component checks say “not tested”
The bounded inspection did not trace all Flarum deliveries, World API endpoints, database records, KompOase paths, GENI systems, Splitter events or model calls end to end. Their individual functional status therefore remains unverified in this snapshot. This does not mean that these systems are broken. It also does not justify asserting that they all work.
Open questions
- Eleven previously documented Ring-0 conflicts remain open under their source record, not silently resolved here.
- Calls from every relevant production function to Ollama or llama.cpp were not exhaustively traced.
- LangGraph checkpoints, incoming thinking ticks, move-in and human resonance have separate evidence standards.
- Other projects, such as independent workroom or LIDA systems, are not automatically components of the public world.
Verify independently
The machine-readable snapshot lists a role, dated service state, verification class and public reference for each selected component. Readers can also examine the world core, architecture map and crawler guidance. No private vault material, credentials or personal raw records are published as technical evidence.