# GRAPH RULES — how any node earns its place

Every future node, before it exists, answers in writing:

1. **What is it?** — one of the closed node types in MASTER_ONTOLOGY.md.
2. **Where does it belong?** — its pillar, its position on the existence
   axis AND the evidence axis.
3. **What evidence supports it?** — the named source per field, or
   UNSOURCED written plainly.
4. **How does it connect back?** — the relationship edges (each carrying
   its own evidence) that reach the Qurʾān in finitely many steps.

## Filing discipline (inherited from v1, mechanical)
- Append-only journals; fsync per write; whole-file rewrites banned for
  accumulating records.
- Gated writers refuse: missing fields, unfixed vocabularies violated,
  duplicates, unverbatim quotes (re-read at filing time), numbers a tool
  did not actually print, and evidence files that do not exist.
- People-claims: every biographical field (birth, death, tribe, teacher,
  student, battle, narration count) cites work+locator or is UNSOURCED.
  A beautiful biography with invisible sources is a defect, not a page.
- Contested matters (theological positions, sectarian differences) are
  DOCUMENTED with their carriers, never adjudicated — the
  similarities-only ethos extends to the whole waqf: agreement is shown
  as agreement, difference as difference, and judgement is left to the
  qualified.

## Versioning
The ledger `_FRAMEWORK-13800.json` is the single source of structure
(v1.4.0, by the owner's word: P28 The Sīrah Universe joined, total
13,800; the earlier `_FRAMEWORK-13500.json` remains on disk as the
v1.2.0 record — append-only, nothing deleted); `_TRACKER-13800.json`
the single source of state; both append-only with version entries. No
window builds anything absent from the ledger.