portfolio-optimiser-commons/examples/nav-golden-escape/SHOULD-NOT-BE-READ.md at a67a243a54980ff36760de9fb7d7bf71bb9851a2

Kjell Tore Guttormsen b6417414c8 docs(examples): nav-golden fixture class — bundle → read-context goldens

New fixture class for the D4 step-0 split (commons-owned; delivered into
catalog's corpus/runner). A nav-golden case is bundle in / expected-read-
context out — the shape that expresses "two conformant implementations MUST
produce an identical read-context" (method-spec §3 Step 1).

- nav-golden-hierarchy/ (positive): depth-first first-seen order, both link
  forms (/ = bundle root vs relative), one segment per level, resolved-path
  dedup, cycle termination, recursive verdict exclusion, missing-index binds
  root alone, flat render.
- nav-golden-escape/ (negative, gate must go red): .. escapes and a
  /etc/passwd root-relative trap; conformant returns only valid.md.

Both expected-read-context.md verified byte-for-byte against a conformant
navigator implementing §3 Step 1; the negative case verified to diverge
under a naive navigator.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VUCuNNvnCkayuUDy2WFgeU

2026-07-21 10:22:50 +02:00

262 B

Raw Blame History

type	title
project	Decoy — MUST NOT be read

This file sits ONE level above bundle/, outside the bundle. If its text ever appears in a read-context, the navigator resolved a .. escape and breached the bundle boundary. It MUST never be reached.

262 B Raw Blame History

262 B

Raw Blame History