Apply gate-house's section 11 rulings: four-token validator, emission guarantee, resource.system.

GH-DEC-2026-017: the validator admitted {Staff, Engine, Tooling}, built from
section 4's catalog rows, and rejected Taxonomy, which section 3.1 defines.
railiance-master was conforming; the validator was the divergent artifact.
Now four tokens, ASCII case folded, section 4's spelling canonical, INTENT.md
governing while form disagreements are still reported, and every run states
its scope (section 11 binds section 4; volunteers are not non-conformances).
Also fixes the survey silently dropping audit-core's layer.yaml by decoding
peers into flex-auth's own struct.

GH-DEC-2026-018: flex-auth is a section 4 source of evidence. G2 closes as a
question and reopens as a dated gap (review 2026-10-19). cadence.yaml
publishes the per-event-class inventory: deny, redact, not_applicable and
audit_only rare load-bearing (heartbeat and reconciliation, rate forbidden);
allow volume load-bearing (expected-rate and reconciliation). INTENT.md
declares source_of_evidence and names it; tests assert both. Delivery is
FLEX-WP-0031.

FLEX-DEC-2026-015: resource.system follows the runtime, not the repository,
answering ops-warden's WARDEN-IN-0003.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703

workplans/FLEX-WP-0030-boundary-declaration-cleanup.md

@@ -267,6 +267,14 @@ Corrections went to `gate-house` and the five engine repositories that received
 the original, plus `ops-warden`, `kings-guard` and `audit-core`, who are affected
 by the corrected finding and had not been told of the first.
 
+2026-09-21 (rulings): gate-house ruled B1, B3 and B4 (`GH-DEC-2026-017`,
+`-018`, `-019`; amendments A9–A13). B1: `INTENT.md` governs, case folds. B3:
+**against flex-auth** — a source of evidence, non-conforming on §11 today, and
+`audit-core` confirmed independently (`AUDIT-IN-0005`). B4: ruled as asked. B5:
+A13 notes it. B2: `gate-house` declared; `key-cape`, `ops-mason` and
+`net-kingdom` have not answered. Task stays `progress` on B2 alone — not closed
+by silence. Consequences are T06–T08.
+
 ## Out of scope
 
 - Bumping flex-auth to declare v0.8. v0.8 is `status: proposed`; T01 removes the
@@ -312,3 +320,65 @@ recorded rather than edited away.
 
 2026-09-21: done. Receipt at
 `docs/evidence/2026-09-21-layer-declaration-survey.json`.
+
+## 6. Fix the validator: four tokens, case folded, scope stated
+
+```task
+id: FLEX-WP-0030-T06
+status: done
+priority: high
+```
+
+Owner: `flex-auth`. Authority: `GH-DEC-2026-017` §2–§4, A9, A11.
+
+The validator admitted `{Staff, Engine, Tooling}` — three tokens taken from §4's
+catalog rows, omitting §3.1's Taxonomy. `railiance-master`'s `Taxonomy` was
+conforming; the validator was the divergent artifact.
+
+Gate: the four tokens are admitted; comparison folds ASCII case; §4's column
+spelling is canonical; `INTENT.md` governs while form disagreements are still
+reported; a run states its scope and reports non-catalogued declarers as
+volunteers; the review records the correction rather than editing it away.
+
+2026-09-21: done. `internal/layer` (`CanonicalLayer`, `Vocabulary`, `Scope`,
+`CatalogScope`, `EstateScope`, `VolunteerDeclarations`), survey `--catalog-only`,
+eight new or inverted tests. Also fixed a survey defect found on the way: peers
+were decoded into flex-auth's struct, and `audit-core`'s `layer.yaml` silently
+dropped out once field shapes diverged. Correction in
+`docs/conformance/boundaries-review.md`; receipt re-run.
+
+## 7. Publish the per-class emission inventory and register G2 as a dated gap
+
+```task
+id: FLEX-WP-0030-T07
+status: done
+priority: high
+```
+
+Owner: `flex-auth`. Authority: `GH-DEC-2026-018`.
+
+Gate: G2 closes as a question with the ruling as its reason and reopens as a
+gap with owner, blocker and review date; the classification is published per
+event class by flex-auth, not inferred; `INTENT.md` states
+`source_of_evidence` and names the declaration; the test suite asserts both.
+
+2026-09-21: done. `cadence.yaml` classifies five decision classes. Rare
+load-bearing (`deny`, `redact`, `not_applicable`, `audit_only`): heartbeat and
+reconciliation, rate monitoring forbidden. Volume load-bearing (`allow`):
+expected-rate **and** reconciliation, because rate cannot see a targeted subset
+removed. G2 is dated 2026-10-19; delivery is `FLEX-WP-0031`.
+
+## 8. Rule whether resource.system follows the repository or the runtime
+
+```task
+id: FLEX-WP-0030-T08
+status: done
+priority: high
+```
+
+Owner: `flex-auth` as PDP. Asked by `ops-warden` (`WARDEN-IN-0003`).
+
+2026-09-21: done. `FLEX-DEC-2026-015`: it follows the runtime. It is policy
+vocabulary, retained by `FLEX-DEC-2026-013`, and both places the PDP matches on
+it fail closed on an unknown value. Any future flip is PDP-first,
+consumer-second, and is not a repository-rename step.

workplans/FLEX-WP-0031-decision-record-emission.md

@@ -0,0 +1,90 @@
+---
+id: FLEX-WP-0031
+type: workplan
+title: "The decision record has a declared emission guarantee and nothing that delivers it"
+domain: infotech
+repo: flex-auth
+status: ready
+flavor: implementation
+owner: claude
+topic_slug: netkingdom
+planning_priority: P1
+planning_order: 310
+related_workplans:
+  - FLEX-WP-0030
+  - FLEX-WP-0019
+created: "2026-09-21"
+updated: "2026-09-21"
+---
+
+# FLEX-WP-0031 — Deliver the decision-record emission guarantee
+
+`GH-DEC-2026-018` ruled that flex-auth is the §4 source of evidence for the
+decision record, and that it is not conforming on §11 until it declares and
+delivers a per-event-class emission guarantee. The declaration is published
+(`cadence.yaml`, `FLEX-WP-0030-T07`). Nothing emits: the decision record reaches
+consumers only in the `/v1/check` response, no sender named flex-auth or
+`access-engine` is registered with `audit-core`, and there is no outbox,
+heartbeat or reconciliation count. This plan closes declared gap **G2**
+(`docs/conformance/security-layer-conformance.md`, review 2026-10-19).
+
+Bound, stated up front so no argument rests on more: heartbeat and
+reconciliation detect loss, outage, drain failure and accident. Neither detects
+a compromised flex-auth suppressing a record and its own count together.
+
+## 1. Decide emission atomicity
+
+```task
+id: FLEX-WP-0031-T01
+status: todo
+priority: high
+```
+
+`GH-DEC-2026-018` left open whether decision-record emission must be atomic with
+the decision (§9.4), pending the class inventory. It exists now. Decide whether
+a rare load-bearing decision (`deny`) may be returned before its record is
+committed to the outbox, and record the answer as a `FLEX-DEC`. Gate: decided,
+with the latency cost stated.
+
+## 2. Register flex-auth as an audit-core sender
+
+```task
+id: FLEX-WP-0031-T02
+status: todo
+priority: high
+```
+
+Open an intake with `audit-core` (worked examples `AUDIT-IN-0002`,
+`AUDIT-IN-0003`): sender registration, `evidence_kind`, `heartbeat_classes` per
+class exactly as `cadence.yaml` publishes them, and a token lane routed via
+`warden route find`. audit-core has said it accepts the classification as
+supplied and will not infer it. Gate: sender registered; no secret in any file.
+
+## 3. Transactional outbox, heartbeat and reconciliation counts
+
+```task
+id: FLEX-WP-0031-T03
+status: todo
+priority: high
+```
+
+Emit one event per decision into a local outbox, drained to `audit-core`
+`POST /v1/events`; a daily `flex-auth.decision.heartbeat`; committed counts per
+class exposed for `GET /v1/reconciliation`; lag bound per `cadence.yaml`.
+Gate: `cadence.yaml` validates under the net-kingdom emission-cadence profile
+checker with the inventory supplied as `--rare-load-bearing`/`--load-bearing`
+assertions; tests assert the declared classes equal the `DecisionEffect`
+vocabulary so a new effect cannot ship unclassified.
+
+## 4. Close G2
+
+```task
+id: FLEX-WP-0031-T04
+status: todo
+priority: medium
+```
+
+Change `cadence.yaml` `state` to emitting, move G2 out of the gap table with the
+evidence, and tell `gate-house`, `audit-core` and `kings-guard`. Gate: a silence
+finding is observed on a deliberately withheld heartbeat in a non-production
+run.