[Hafeok]

Act address landing session, GATE 2. This PR proposes the change; Emil rules on it. Merging it cuts v5.15.0, because the descriptor is included.

The session record is in the projection repository's meta/sessions/2026-09-27-act-address-landing/ (gate1-survey.md, gate1-rulings.md).

Weakest point

The repaired falsifier limb 1 says the governing set is computed from "address, ground readings and predicates, without the verdict itself". It assumes that everything a governing predicate needs sits either in the address or in what the act read, and never in the verdict. That line between reading and verdict input is untested, and it is flagged UNVERIFIED — Emil review in the claim's notes.

What files

Object	Kind / status	Note
core/claims/DDD-ground-06.yaml	conceptual, projected	Position on declared ground axes plus layer path, read at the act-site; occupant excluded
core/decisions/DDD-dec-37.yaml	decision	The ruling, including the GATE 1 landing rulings
term:act-address in core/graph/terms.yaml	draft	Established by core/14 §5; aliases [act address] only
core/14-indexed-determination.md	prose	Contract establishes, the intro's term count, and a new §5 with the embed
i18n/ordliste-dansk.md	glossary	handlingsadresse, lagsti (ruling 9)
README.md	index row	core/14 row gains "act address"
releases/v5.15.0.yaml	descriptor	Minor: one claim and one term added; no id or settled node moves

Rulings applied (GATE 1, Emil, 2026-09-28)

• Ruling 1: falsifier limb 1 repaired, as described above.
• Ruling 2: the independent case is named neutrally, as "the first independent application case, pre-registered in the projection's session records". I applied the same neutral wording to breaks and region; the drafts named the downstream claims and the method there.
• Ruling 3: the declared-space limit is cited to DDD-ground-05 and DDD-ground-02.
• Ruling 4: Rule 1, kept joined.
• Ruling 8: the term is homed in core/14, and the bare address alias is dropped.
• Ruling 9: the glossary rows are added.

Validation

Gate	Result	Baseline
validate-core-order.py core/	exit 0; 0 errors, 66 warnings, 0 W4	66
validate-claims.py core/claims/	exit 0; 64 claims, 32 warnings, none on DDD-ground-06	32
validate-claims.py core/decisions/ --decisions	exit 0; 14 decisions	—
validate-releases.py releases/	exit 0; 12 descriptors, basis resolves	—

What fires downstream

This release moves no pinned object, so it contributes no W5 and no W6. The two new IDs are pinned at the downstream advance.

That advance runs from v5.13.0, so it also carries v5.14.0's published DDD-frame-08 W6. The full prediction is committed downstream at GATE 3, before the bump.

Do not merge until Emil accepts.

🤖 Generated with Claude Code

https://claude.ai/code/session_011UYoSMH3Hn75vS3EKdZFT3

---

Generated by Claude Code