The world model is the directory's knowledge graph laid out as tables. It is visible to admins only, and it changes nothing: every table is a read of the graph the write chain and ingestion already maintain.
Open it from the sidebar, directly under Memory, or at /:directory/world-model. Members and guests never see the row, and the URL answers with a 404 for anyone who is not an admin.
Five kinds, and tabs the graph defines
A switch in the title row picks the kind: Entities, Edges, Claims, State or Aliases. Under it, the tab strip is derived from the graph, not fixed:
The tab and the search box both live in the URL (?tab=, ?facet=, ?q=), so a filtered view can be shared like an Issues view. Long tables load fifty rows at a time; Load more appends the next page.
Reading the State tabs
The chain defines two states while it runs, and both are here in full. Organisation is the OrganisationState every run reads at its start: entities and their variables (X), relationships (R), actions (A), objectives (O), constraints (C), temporal dynamics (T), beliefs (B), plus the system model derived from them (S: stocks with their observed levels, flows, and reinforcing or balancing feedback loops). It is projected from the graph and appears after the directory's first ingest.
Every other State tab is one doc: the typed ProblemState the chain produced for that run, archived beside the graph so it can be replayed without a model. Same sections, same reading.
What the numbers above the table mean
The summary line counts active entities, active edges out of all edges, committed and pending claims, distinct entity and relation types, alias rows, and the graph head (the sequence number of the last committed transaction). When a number looks wrong, the head tells you whether the graph has moved since you last looked.
Reading the Types table
A registered type is one the schema declares, with the endpoint types an edge of that type may join. A dynamic type was minted by extraction and accepted as-is. Dynamic types that should have folded into a registered one are the usual reason to add a line to the alias file, which the Aliases tab shows in full.
What it is not
There is no editing here. Aliases are changed through the graph admin page, claims through the claims review, and entities through the write chain.