# SPEC
## §G GOAL
Distil a document into the part a reader needs to ACT. Generated, ⊥ hand-written.
## §N NAV
up|src|code nodes — tokens, spec, fed, lens facades & logic
self|src/slice|distil a document to the part needed to ACT, generated
sib|src/tokens|-
sib|src/spec|-
sib|src/split|-
sib|src/fed|-
sib|src/adopt|-
sib|src/lens|-
sib|src/ollama|-
sib|src/tdd|-
sib|src/plan|-
sib|src/wave|-
sib|src/review|-
sib|src/state|-
sib|src/land|-
sib|src/cli|-
sib|src/code|-
sib|src/debt|-
sib|src/assay|-
sib|src/git|-
## §C CONSTRAINTS
- LOCAL sources only. ⊥ network — `.:C` allows the inference endpoint & nothing else. remote arrives via a pinned flake input, ⊥ an HTTP fetch here.
- declarations in `.sherd-slices`, line-oriented, same family as `.context-limits` & `.spec-records`.
## §V INVARIANTS
V1: a slice is ⊥ a summary. a summary compresses everything proportionally & leaves the reader unable to tell what is authoritative; a slice takes 100% of what is LOAD-BEARING & 0% of the rest
V2: GENERATED. `notation.txt` was extracted by hand once & nothing would notice if `FORMAT.md` moved (B1). `--check` gates the drift
V3: an EMPTY slice is an error, ⊥ an empty file. a rule matching nothing means the source moved & the reader would get silence
V4: a malformed declaration is an error naming its line, ⊥ a skipped row
V5: output carries its provenance — `GENERATED by sherd slice from <source>` — so a reader knows ⊥ to edit it
V6: slices serve COMPLIANCE. a rule fits a line; a JUDGEMENT needs the reasoning ∴ the worker gets slices & the supervisor gets the source
V7: `drifted` has ONE definition, called by `sherd slice --check` AND by the gate. the hook & the loop ! apply the SAME rule — 2 implementations of one check is the defect this repo exists to end (`.:V50`)
## §T TASKS
T5|.|distil `§B` rows into worker prohibitions — the failures are stubs, ⊥ design|V6
## §B BUGS