E.2.DA:4.5a - Result-row discipline and calibration

An E.2.DA result uses this table shape:

Pillar coordinate	Value	ShortRationale	EvidenceLocus
`<E.2.DA coordinate>`	`<0..5>`	`<assigned-value basis and the applicable adjacent-value rationale below>`	`<pattern section, monolith section, host, README scenario, ToC row, E.11 entry-distribution locus, E.11 worked comparison, projection, source row, relation row, companion file, evaluation result, or missing locus named by value>`

For values 1..4, explain why the lower adjacent value would understate the evidence and the higher adjacent value would overstate it. For 0, explain why 1 would overstate the evidence and what would raise the value or reopen it. For 5, explain why 4 would understate the evidence and what would lower the value or reopen it.

A Pillar essay, local-quality average, two-column table, or result whose value depends on unchecked corpus, projection or source evidence is draft evaluation material. Check the needed evidence before assigning the affected value. An observed defect lowers a value according to its coordinate meaning; absence of a check does not by itself establish that defect. A completed E.2.DA result still evaluates all eleven coordinates.

Common calibration points:

Pillar family	`3`	`4`	`5`
Entry, usability, and projection Pillars	The object can be used with visible limits, but projection or first-use evidence is partial.	Relevant defining, constraining, or testing content and projections are coherent enough for declared use.	The use is replayable across pattern content, the public-entry form selected under E.11, and cold-reader or retrieval evidence, with an explicit stop or return and any independently grounded non-use boundary.
Layering and semantic authority Pillars	Neighbours are plausible, but some shadow-spec risk remains.	The pattern content that defines, constrains, or tests each claim is named by value and distinguishable from source-linked projections.	Pattern bodies, relations, projection rows, and anti-fragmentation cases keep each concrete contribution recoverable without shadow semantics.
Source and evolution Pillars	Source or reopen language exists, but currentness, contribution, or smallest-reopen basis is compact.	Source contribution, currentness window, and reopen condition are explicit for declared use.	Source-front movement and future reopen are replayable without freezing development after a local stop.