To operatørbeslutninger 24.08, ingen normativ tekst endret.
method-spec.md §3: en informativ merknad mellom §3-ingressen og Step 1 om at
mandatet kan UTLEDES før løkka starter. ALDRI et niende nummerert steg — et
nummer i samme rekke arver rekkens autoritet, og aktiviteten er ikke normativ.
Merknaden bruker derfor ingen RFC 2119-nøkkelord, får ingen `###`-overskrift,
navngir ingen konkret agent-toolkit (framework-nøytralitets-vakta), legger
ingen kontraktsfelt til og berører ingen søm i §11. Den sier eksplisitt at
ingenting nedstrøms slakkes: Step 1s navigasjonsregler, Step 4s validator-gate
og verdikt-lag-eksklusjonen står uendret uansett hvordan mandatet ble til.
Ordrett «step 0» finnes nå to steder, på to akser som hver navngir sin egen:
examples/nav-golden-escape/README.md:3 («catalog's requirement that step 0's
gate…») og method-spec.md:66 («this specification defines no step zero»).
README.md: bygg-energi-mikro-bulleten lovte fortsatt «a realistic full-scale
example comes later». veglys-fv-soer og tunnel-hauglia er begge publisert og
fyller rollen; setningen peker nå på dem i stedet for å love noe som mangler.
Ordre 20260824T155506Z-3454831118-from-.claude, punkt 1 og 2.
Ratified Q3 resolution: the navigator must traverse hierarchical bundles;
door A stays flat (ingest-spec unchanged). Replaces the path-separator ban
with resolve-and-boundary-check as one change (decision record §3 item 6):
link syntax normative (/ = bundle root, never fs-absolute; else relative;
nested allowed, escape not), depth-first first-seen traversal, dedup on
resolved path, one segment per level, missing index.md binds the root
alone, verdict-exclusion = type check per reached file (recursive, never a
graph property), flat read-context render. Robustness now covers malformed
targets (skipped never raised) — closes the null-byte class at spec level.
Two §11 seams. Framework-neutral; backward-compatible (golden unaffected).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VUCuNNvnCkayuUDy2WFgeU
Author shared/method-spec.md: the 8-step loop (normative, RFC-2119), the
verdict JSON contract incl. the id-minting algorithm and the chosen conflict
semantics, the inbox/outbox folder contract, the fail-closed promotion-gate
semantics, the IR projection + golden suite as the only ground truth (incl.
the reproducible Monte Carlo procedure), and the budget/stop, provenance and
startup-contract requirements — every normative claim cross-checked against
the load-bearing tests/code. The sibling implementation builds from this spec
alone.
Load-bearing trio (tests/test_method_spec_loadbearing.py, persona-trio
style): required structure, a name-shaped framework-neutrality guard over the
spec + the persona skill tree, and a cross-check-completeness test driven
from the REAL artifacts and the REAL verdict serializer (red on code drift).
All three detach points proven RED (missing file / framework name / dropped
field). shared/README.md: the "(planned)" line replaced with the real entry.
Suite 152 -> 155 passed / 4 skipped; ruff check+format clean; mypy src clean.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AaQCFnfsh3tfq1VfzdJpoi
