feat(p19): a cost code must have a FORM where the input offers forms
P18's round 2 ended with two VALIDATED proposals whose affected_item codes were ordinary words from a road standard's prose -- impulsventilator (4 of 270 N500 documents) and bituminoest baerelag (4 of 1133 N200). Both are grounded in P7's sense and neither is inert in P18/B1's sense; they are simply not identifiers of a cost line, and the gate had no stage that could say so. Known positive MEASURED, not asserted: replayed offline against the bases those runs were given, both come back Rejection naming the denominator. IDENTIFIER_FORMS moved from generate.py to validator.py: they now drive both P8's report and this gate, and two copies of "what an identifier looks like" would let the two disagree about one run's own input. B1 -- two new forms, transcribed from measurement. R761's requirement numbers are bare dotted numbers and all six refs in kontrakt-sorasen's fasit are of that shape, which neither pre-P19 form matched: r761's whole offer was 3 identifiers over 6.5 MB, and is now 2332. The FIRST form was widened in the same pass because B2 made these forms decide prose vs identifier, and this repo's own ENERGI-TOTAL-EL matched none of them -- a gate may only be wrong in the direction that admits too much. Three things keep the gate from being a rule about shapes: the generality guard (it fires only where the input offers forms), the baseline exemption (stage 0 has already ruled that code real), and full-matching. Honesty limit, measured and given its OWN arm: a decimal and an R761 process number are typographically identical, so the form counts both. P8's existing "bare numbers" arm is narrowed to bare INTEGERS accordingly. Measured over all nine round-1+2 outboxes: 26 of 36 codes are prose. Load-bearing measured (22 arms), four mutations all red against the whole suite (16 / 10 / 1 / 2), green control 1734/5 and the golden byte-unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
c84e8bf6f1
commit
d74f32dc1c
15 changed files with 446 additions and 36 deletions
|
|
@ -460,6 +460,14 @@ when the seam is detached, so the loop cannot silently degrade into theater.
|
|||
None of them has a default, because an omitted cap falls back to an *unbounded* loop rather than
|
||||
a conservative one.
|
||||
|
||||
**A cost code must have a FORM where the input offers forms.** Every `affected_item` code is
|
||||
classified as `identifier` or `prose` and reported on the proposal's provenance (`code_forms`).
|
||||
Where the delivered input demonstrably offers identifiers of its own — requirement numbers,
|
||||
process numbers, coded cost lines — a `prose` code is refused by the deterministic gate, naming
|
||||
how many identifiers the input offered. Where it offers none, the rule does not fire: a corpus
|
||||
that does not use identifiers cannot be answered in them. A code the project's cost baseline
|
||||
carries is never refused for its shape, because stage 0 has already ruled it a real line.
|
||||
|
||||
**Naming the requirement that binds a direction.** Whoever navigates a knowledge base — the
|
||||
exploration's hypothesiser and, since the debate started navigating, the proposer — is asked to
|
||||
name the ONE requirement that binds the direction it commits to, and to declare it with
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue