gate-house/workplans/GH-WP-0004-section-11-layer-declarations.md

---
id: GH-WP-0004
type: workplan
title: "§11 layer declarations — amendment set and estate closure"
domain: infotech
repo: gate-house
status: active
flavor: implementation
origin: GH-IN-0003
owner: codex
topic_slug: infotech
created: "2026-09-21"
updated: "2026-09-21"
---

# §11 layer declarations — amendment set and estate closure

## Goal

Land the five §11/§4/§3 amendments that `GH-DEC-2026-017` and `GH-DEC-2026-018`
produce, into the **proposed** v0.8 cut before the acceptance flip, and close the
estate-side items the two rulings create. `GH-DEC-2026-019` holds the flip on this
workplan and states three closing conditions.

**Normative text for A9–A13 is drafted at
`docs/amendments/v0.8-section-11-declaration-amendments.md`.** That file is the
reviewable unit: each amendment carries its own wording, defect statement, and
authority, so it can be argued before anything touches the cut.

## Why now

`access-engine`'s boundaries review (`FLEX-WP-0030`) found five §11 defects from
outside, after the v0.8 round closed, in the section `audit-core` was asked to attack
and did not return a review on. One of them — A10's — is `gate-house`'s own amendment
`A2`, written twelve days ago and reviewed twice without anyone noticing it named a §4
property §4 does not carry.

v0.7 stays `accepted` and in force, unpatched. Nothing operational waits on this; the
cost of the hold is documentation currency, which is what makes it affordable
(`GH-DEC-2026-019` §3).

## Tasks

### T01 — A9: state the §3 vocabulary once, as tokens

Four tokens, closed, case-insensitive comparison, `Engine` not `Engines`, role is not
layer. Resolves the §3-versus-§4 divergence that makes two faithful runs disagree about
eight rows.

```task
id: GH-WP-0004-T01
status: todo
priority: high
```

### T02 — A10: §4 gains an evidence-source marking; §11's check reads the marking

Includes the per-event-class clause and the count repair. Then assess the remaining §4
rows repository by repository — `access-engine` is marked by `GH-DEC-2026-018` §2; the
others are asked, not assigned.

```task
id: GH-WP-0004-T02
status: todo
priority: high
```

### T03 — A11: `INTENT.md` governs, the sidecar is derived, a run states its scope

```task
id: GH-WP-0004-T03
status: todo
priority: high
```

### T04 — A12: a declaration carries no standard version

Includes asking `ops-warden` to drop `standard_version` from the reference form rather
than each of the seven adopters deciding separately.

```task
id: GH-WP-0004-T04
status: todo
priority: medium
```

### T05 — A13: the `access-engine` coordinate is pending, not broken

One line in §4. No gate-house ruling required; substance already ruled in the owning
repository under `FLEX-WP-0020`.

```task
id: GH-WP-0004-T05
status: todo
priority: low
```

### T06 — Ask `informed-decision` whether it should become a §4 catalog row

Asked, not enrolled. Its correction from `surface` to `Staff`/`pep-shaped` is its own and
is not a condition of this task.

```task
id: GH-WP-0004-T06
status: todo
priority: medium
```

### T07 — Closing condition 2: `audit-core` returns its §11 review or declines in writing

A written decline closes it. §14 records *not claimed* rather than counting silence as
assent, and the point is that the record says which.

```task
id: GH-WP-0004-T07
status: wait
priority: high
```

### T08 — Closing condition 3: `key-cape`, `ops-mason`, `net-kingdom` declare or record a dated gap

`gate-house`'s own is discharged (`GH-DEC-2026-017` §6, this commit). A declaration or a
dated gap satisfies this equally; conformance is not the condition.

```task
id: GH-WP-0004-T08
status: wait
priority: high
```

### T09 — Circulate A9–A13 for assent and disposition the returns

Round list: `net-kingdom` (publisher), `access-engine`, `audit-core`, `approval-engine`,
`ops-warden`, `kings-guard`, plus `informed-decision` and `railiance-master` as the two
repositories the vocabulary ruling touches from outside §4.

```task
id: GH-WP-0004-T09
status: progress
priority: high
```

### T10 — `net-kingdom` assembles the amendments into the v0.8 cut and flips acceptance

Publication and the flip are `net-kingdom`'s and were handed over at v0.8 round close.
This task tracks the handoff, not the execution.

```task
id: GH-WP-0004-T10
status: wait
priority: medium
```

## Done when

All five amendments are in the v0.8 cut, the three `GH-DEC-2026-019` closing conditions
are met, and `net-kingdom` has flipped v0.8 to `accepted`.