# templates/finding.template.md > 81 lines of code and 0 definitions. Tree: Coordination tree Language: markdown Canonical: https://banes-lab.com/anatomy/coordination#file-coordination-templates-finding-template-md Source text: https://banes-lab.com/assets/sources/source.34eae219dc5614c883d1cc58eeb0c9ebe013b21efa22b85aab309328e59c49ab.generated.txt ## Source ````markdown # A venue's MEASURED half: this tree's own instances, one row per claim, carrying what OBSERVES it. # Copy to `.finding.md` in the declared findings root. The class half lives in a model and never here. # Model: `models/coordination.model.md` — the class decides what a row MEANS; this surface carries what it came to HERE. ═══════════════════ LIFETIME (declared, read rather than inferred) ═══════════════════ **THE VALUES ARE DRAWN FROM THE CLASS SURFACE'S CLOSED SETS AND ARE NOT RESTATED HERE AS A SECOND COPY.** Retention, mutability and removal authority each draw from the set stated there, and an unlisted value is an approved extension to that set rather than a naming choice taken here. **The file default:** retention `current-truth` — a row records the state AFTER a repair and gives way to a newer version of itself. Mutability `owner-rewritable` — any seat may correct a row, announced before the edit lands. Removal authority `author` — the party who wrote a row retires it. **A section declares only where it DIFFERS from that default**, so the default stays one statement and the exceptions are the whole of the cost. | section | axis | value | why | | ------------------------------------------ | ---------- | -------- | ------------------------------------------------------------------------------------------------- | | this LIFETIME block and the CONTRACT block | mutability | `frozen` | written from the template and never edited in a live surface — a correction lands in the template | **AND THE OBSERVER COLUMN IS WHY THIS SURFACE IS NOT CURRENT TRUTH IN THE ORDINARY SENSE.** A row naming `nothing` as its observer is a MEASUREMENT that the tree was searched and none was found, so replacing it silently when an observer later lands is correct while DELETING it is not — the measurement is an operand of every count taken over this table. A row leaves by being superseded by its own newer version, never by being pruned because it reads as negative. ═══════════════════ CONTRACT (permanent) ═══════════════════ ## What decides a row, and where that decision lives **THE FRAMEWORK DECIDING A ROW LIVES IN THE MODEL AND IS NEVER RESTATED HERE.** The fields, the reachable states, the families of control and every rejected state are CLASS content. One contract in two files is two copies with nothing keeping them equal, and the copy nobody re-reads is the one a reader takes. **Read the model for how a row is DECIDED; this surface carries only what the decision came to here.** **AN ADOPTER COPIES THE MODEL AND NEVER A POPULATED FINDING SURFACE.** A baseline embedded in a template makes the next adopter inherit another project's incidents as laws — so this template ships the SHAPE and carries no row, and a surface raised from it is empty until its own tree is measured. ## The row grammar **The specimen is FENCED so every scanner reads it as a row MENTIONED rather than CLAIMED.** A surface raised from this template unfences its own table with the placeholders resolved, and a write form DERIVES the column set from the specimen below rather than transcribing it. ```text | | | | | | ``` | column | what it carries | what makes it wrong | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | `mechanism` | the construct being measured, named as a SHAPE rather than as a file | a path or a tool name, which stops being resolvable the moment either moves | | `evidence` | what observes it, and in which direction — a check that FIRES, one that fires AND ACCEPTS, an absent capability, a discovery-time refusal, or `nothing` | a verdict quoted from a run, which is a cache with no invalidation | | `range` | the POPULATION the measurement covers, named by its members' shape | a COUNT, which answers how many and never which, so every arithmetic axis skips it in silence while the field reads as evidence | | `reach` | the party the observation actually reaches, which is rarely the party that wrote the mechanism | the mechanism's author, which is presence standing in for delivery | | `failure mode answered` | the SHAPE that failed and how it presented, or `—` | an episode, a date, a party or an ordering, which is a diary entry wearing a row's clothes | **A COUNT IS NEVER TRANSCRIBED INTO A ROW.** Where a range is a population the pipeline derives, the row names the population and the report on disk carries the size — a transcribed count is a derived fact maintained by hand, wrong from the first change nobody propagated and reading as current throughout. **THE LAST COLUMN IS THE ROW'S OTHER HALF, AND A DASH IN IT IS A REAL ANSWER.** A row records the state after a repair, so without the failure it answered a later reader sees a proven capability and cannot tell it was operationally absent for a whole prior period, what made it reachable, or that the same absence returns the moment a new surface copies an old template. The dash states that the mechanism was correct as first built. **A ROW STATES THE SHAPE THAT FAILED AND NEVER THE EPISODE**, which is the same permission a rule's own measured clause carries: the construct and how it presented are the operand, while who, when and in what order are archaeology this surface does not hold. ## A section that measures CLAIMS rather than mechanisms takes its own columns **A claim is not a mechanism, so it never borrows columns that mean something else.** Where a surface records what its parties CLAIM beside what it OBSERVES, the two are different operands of one question and are tabled separately — and the kind is recorded per COMPONENT rather than per claim, because a claim whose components denote different sorts of thing has no single kind and recording one erases exactly the structure the comparison is computed from. **A PAIR CELL TAKES THE VALUE OF ITS WORST COMPONENT-PAIR AND NAMES THE COMPONENT THAT PRODUCED IT**, so a pair reads as unresolved only where a component-pair genuinely is. **A set is only as comparable as its least comparable component** — admitting one predicate makes the question undecidable by text for every claim it is paired against, including components that are perfectly extensional. **`UNEVALUABLE` IS A MEASUREMENT AND NEVER A VERDICT THAT TWO THINGS OVERLAP.** A surface reporting either disjointness or collision from unevaluable pairs asserts a computation nobody performed. ## The value column and the reason column are two axes **The VALUE is drawn from a closed set and is the JOINABLE operand; the REASON is for a reader and joins on nothing.** A row stated as one prose cell reads as governed and is joinable by nothing, which is the construct this surface class exists to record arriving inside the surface recording it. ## Gate - Every row carries every declared column; an omitted cell states nothing where a dash states something. - A range naming a quantity rather than members fails, because the axis that would compare it cannot. - A count of any set the pipeline derives fails wherever it appears in a cell. - `nothing` in the observer position is a pass — it is the measurement, not the absence of one. ═══════════════════ THE ROWS ═══════════════════ **A surface raised from this template carries no row until its own tree is measured.** An empty table is the correct state of a finding surface nobody has measured yet, and it is distinguishable from a measured one, which is the whole reason the section is born present and empty. | mechanism | evidence | range | reach | failure mode answered | | --------- | -------- | ----- | ----- | --------------------- | ````