open/portfolio-optimiser
1
0
Fork 0
Code Issues Releases 3 Activity

feat(row6): a proposal whose approach declared no requirement is unsupported

Browse source 
Stress round 6 validated three falsification arms, and every validated
approach rested only on run-level declarations nobody can attribute to one
approach. declare_requirement now takes a required approach_id (a mandate
id or own-proposal; an unknown id is refused naming the valid ones), and a
ValidatedProposal whose approach has neither a mandate requirement nor a
declaration under its own id becomes validator.Unsupported - a Rejection
subclass carrying the validator's own ruling, reported as `unsupported` in
coverage, the outcome artefact, the settlement and the judge, and never
counted or summed. The rule is active whenever the debate held the
declaration tool, the micro base included; the road and pre-pass paths are
untouched. Declaration quality is not judged, so the rule can be satisfied
by declaring any document the run read.

The v1 gate's row 6 probes pass; its artefact half reads IKKE MÅLT because
stress round 6 predates approach-addressed declarations, and IKKE MÅLT is
never green - it fails the exit code.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-17 16:40:54 +02:00
commit 938a1ca30e
23 changed files with 718 additions and 115 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/bestille-en-kjoring.md
View file

@ -106,11 +106,14 @@ Mandate outcome
Validated: 1 of 3 approaches — best 30000 NOK (the outcome this run carries)
```
De tre statusene betyr forskjellige ting, og forskjellen er poenget:
De fire statusene betyr forskjellige ting, og forskjellen er poenget:
- **VALIDATED** — tallene holdt. Beløpet er det validatoren slapp gjennom.
- **REJECTED** — tilnærmingen ble vurdert, og falt på tallene. Grunnen står der; det er den du kan
gjøre noe med (ofte er den «regnet mot feil grunnlag», ikke «dårlig idé»).
- **UNSUPPORTED** — tallene holdt, men ingen krav i kunnskapsbasen ble erklært som bindende for
akkurat denne tilnærmingen. Den telles ikke som validert og summeres ikke. Skriv kravet inn i
bestillingen (`requirement` på tilnærmingen), eller la kjøringen erklære det.
- **NOT EVALUATED** — kjøringen rakk den aldri. Den er **ikke** avvist, og den er ikke glemt.
En tilnærming du bestilte forsvinner aldri i stillhet. Det er hele grunnen til at oppgjøret finnes.