Expand description
STATE & DATA AUTHORITY (Ontology phase): deterministic attribution of state ownership per component from the fact layer.
Six subsections:
persistent: stores/data entities via WRITES edges (the existing componentownsclaims).runtime: FIELD facts withmutable=true, STATE entities, REGISTRY entities.reactive: REACTIVE entities (svelte/vue/react/mobx/signals state) via OWNS edges.configuration: CONFIGURED_BY relationships (Configuration facts).caches: WRITES/READS to cache-technology stores.derived: PUBLISHES/SUBSCRIBES/CONSUMES topics + middleware/registry registrations.
Every line is COMPONENT <verb> TARGET (PROV)-style, deterministically
sorted. Provenance is preserved verbatim from the underlying
relationship — nothing is promoted.
Structs§
- State
Claim - One structured state-ownership claim:
componentowns/reads/registerstarget(evidenceprovenance).verbisownsfor write-derived ownership andreadsfor readers — atlasownsclaims ignore reads so a reader is never promoted to owner. The structured bridge from the STATE & DATA AUTHORITY compiler into the atlas componentownsclaims.
Constants§
- STATE_
SECTIONS - Deterministic render order of the STATE & DATA AUTHORITY subsections.
- S_
CACHES - S_
CONFIGURATION - S_
DERIVED - S_
PERSISTENT - S_
REACTIVE - S_
RUNTIME
Functions§
- compile_
state_ authority - Attribute state ownership per component from the fact layer.
- compile_
state_ claims - Emit per-component state claims over the same fact sets as
compile_state_authority: WRITES to stores/caches, mutable FIELD / STATE / REGISTRY owners, CONFIGURED_BY configuration targets, topics (PUBLISHES/SUBSCRIBES/CONSUMES), and middleware/registry REGISTERS. Deterministic: sorted by (component, verb, target, provenance). - concept_
occurrences - Live OCCURRENCE entities attached to a concept (OCCURS edges), sorted
by id for determinism. Derived counts and provenance always come from
these — concept
countattributes are never stored or mutated at write time (Wave 13). - is_
cache_ store - Cache-technology store detection (store_refs with cache tech): an explicit technology hint or a cache-ish store name.
- occurrence_
count - Derived occurrence count of a concept — the count the schema/reactive compilers use (never a stored counter). Purge naturally lowers it.
- occurrence_
producer - Most frequent occurrence owner name of a concept (deterministic
tie-break: lexicographic smallest), or
Nonewhen the concept has no occurrences. The atlas schema producer — an owner symbol, never the concept/expr itself. - section_
label - Human-readable subsection header for a section key.
- state_
authority_ groups - Groups of symbol ids that SHARE state authority: distinct symbols
writing the same store (data entities resolve to their owning store, so
db.usersanddb.orderscount as one target), read by the same CONFIGURED_BY configuration target, or owning the same REACTIVE state entity (Wave 11 — symbols mutating the same reactive state cohere). This is the shared-state-authority signal for the semantic clustering graph (+4 per pair inside a group).