Separation
DATA asks what fact or state exists. CONTENT asks what information it means. LANGUAGE asks how that meaning is expressed linguistically. PRESENTATION asks how it is shown. Independently ask whether a thing is GLOBAL, belongs to one KIND, or belongs to one INSTANCE.
Authority and hierarchy
Flattened SQL does not make adjacent columns conceptual peers. A value may be subordinate to another fact even when both are columns. The governing question is Who owns this fact? Do not repeat a fact merely because copying it would make one query convenient.
Register is the registered identity/address authority. Content, Blueprint, Dataset data and Project event data hang from RegisterId instead of restating address, Locale, Routespace, Cluster or title. Locale deliberately remains in Register as a small indexed narrowing coordinate; that repetition buys a real access path.
Relationships and cross-database integrity belong to Arcygen code. SQLite stores them; it does not accumulate defensive foreign keys, triggers or speculative CHECK rules that cannot remain authoritative when data is split across database files.
Materialization
- Type 0 → already materialized
Content. - Type 1 →
Blueprint, interpreted as Markdown or later Tecode. - Type 2 → the manifestation cannot honestly be obtained from one stored content cell and therefore uses an earned processor delta.
isTeRL and Type are orthogonal: TeRL describes address resolution; Type describes materialization. Literal + Type 2 and TeRL + Type 0 are both legal.
TeRL
A TeRL represents an earned predictable, procedural or large-scale address family. /{lang}/a/ can represent every localized Article Routespace root. A concrete authored identity such as /lv/a/latvija/ remains literal. Do not pair a blanket /{token}/ TeRL with every literal item beneath it.
TeRL is bidirectional when each variable has one canonical representation: it can parse an address into variables and expand variables back into its canonical address. One TeRL may represent millions or billions of manifestations without millions or billions of Register rows.
Setup
Setup is the site-wide technical registry: regedit for the website. Human-language labels do not belong there. Routespace-wide technical defaults may live there when they are genuinely universal; current earned examples are Dataset and Project processor defaults.
Directory doctrine
The directory doctrine: plurality of deltas; forget piecemeal. A directory exists for a plurality of earned deltas, not because a checklist contains nineteen nouns. The same rule applies to tables, columns, classes and CSS mechanisms.
State Folding
When mutually exclusive state is already proven by meaningful regions of one value domain, derive state rather than storing a competing status field. DatePublish = NULL is unpublished, a future DatePublish is scheduled, and a past DatePublish is published. Author timestamps correctly; do not add an SQLite rule merely to compensate for bad seed data.