Decide emission cadence ownership

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a05e30-2884-71b0-98d7-7edd16ae737b

decisions/decisions.md

@@ -345,3 +345,111 @@ Revert this record and the consumption contract. The falsifier is operational:
 if spending an approval on a failed attempt makes the estate unable to
 complete the actions this object exists for, a reserve/commit protocol can be
 raised then. Unconsume is not the alternative — it reopens replay.
+
+## GH-DEC-2026-004 — Layer emission-cadence ownership between Info Tech Canon and Net Kingdom
+
+```yaml
+id: GH-DEC-2026-004
+kind: decision
+title: Layer emission-cadence ownership between Info Tech Canon and Net Kingdom
+status: resolved
+owner: Bernd Worsch
+repo: gate-house
+standard: net-kingdom/canon/standards/security-layer-model_v0.7.md
+source_note: kings-guard/specs/EmissionCadenceDeclaration.md
+requested_dispositions:
+- approved
+- revised
+- rejected
+affects:
+- gate-house
+- info-tech-canon
+- net-kingdom
+- kings-guard
+- qonto-assistant
+created: '2026-09-04T00:55:29Z'
+updated: '2026-09-04T00:55:29Z'
+rationale: >-
+  Approved interactively on 2026-09-04. The layered split gives each artifact
+  one owner: ecosystem-wide semantics belong to info-tech-canon; NetKingdom-
+  specific MUST/SHOULD rules and the low-volume load-bearing heartbeat-plus-
+  reconciliation profile belong to net-kingdom. This avoids both a Staff-local
+  consumer schema and competing Taxonomy definitions.
+decided_by: Bernd Worsch
+decided_at: '2026-09-04T00:55:29Z'
+state_hub_decision_id: "89c73f45-d07b-40ea-b428-5a7375ce4b09"
+```
+
+## Context
+
+Security-layer-model v0.7 §§9.6 and 17 require evidence sources to declare an
+expected emission cadence so silence can become a finding. King's Guard is the
+only current consumer and drafted `EmissionCadenceDeclaration.md` against the
+real `qonto-assistant` source, but correctly declined to keep a Staff-local
+schema. The standard left ownership between the two Taxonomy repositories:
+`info-tech-canon` for ecosystem-wide semantic contracts and `net-kingdom` for
+NetKingdom standards of record.
+
+Treating that as joint ownership would leave version authority ambiguous.
+Giving the entire artifact to either repository would instead conflate a
+reusable evidence/observability contract with the security obligations of one
+estate. The split is therefore made by artifact, with one owner for each.
+
+## Decision
+
+**`info-tech-canon` owns the versioned, ecosystem-wide
+`EmissionCadenceDeclaration` semantic contract.** It owns the generic forms,
+fields, vocabulary, validation semantics, compatibility rules, and evolution
+of the contract.
+
+**`net-kingdom` imports that contract and owns the NetKingdom security
+profile.** It owns which evidence classes MUST or SHOULD declare cadence, the
+rule that rate monitoring is forbidden for rare load-bearing classes, and the
+heartbeat-plus-reconciliation obligations that satisfy security-layer-model
+§9.6.
+
+The remaining ownership boundaries are unchanged:
+
+- each source repository owns its declaration instance and emission behavior;
+- `kings-guard` owns stream evaluation and silence findings, not the schema;
+- Gate House owns doctrine and conformance supervision, not publication or
+  runtime behavior.
+
+The King's Guard draft remains the provenance and handover input. Once the
+Taxonomy artifacts are published, it becomes historical rather than a second
+contract.
+
+## What this authorizes
+
+- Requesting `info-tech-canon` to adopt, revise, or contest the generic
+  contract and create its own owning work record.
+- Requesting `net-kingdom` to adopt, revise, or contest the security profile
+  and create its own owning work record.
+- Sources such as `qonto-assistant`, `approval-engine`, and `secrets-engine`
+  publishing instances against the eventual canonical contract and profile.
+- King's Guard replacing its draft-shaped fixture with the published contract
+  without changing its consumer ownership.
+
+## What this does not authorize
+
+- Joint ownership or two independently versioned definitions of the generic
+  schema.
+- Gate House or King's Guard retaining the schema as a local contract.
+- Gate House creating workplans in either Taxonomy repository.
+- Treating ownership as source conformance: `qonto-assistant` remains
+  incomplete until it publishes and emits the required positive claim.
+
+## Assent and completion
+
+The ownership ruling is resolved. Publication is complete only when both
+Taxonomy owners reply in their own voice and publish or explicitly schedule
+their respective artifacts. Until then the prior handover residual remains
+open, now with an unambiguous requested disposition.
+
+## Reversal
+
+Supersede this record if the generic contract proves inseparable from the
+NetKingdom security profile, or if Info Tech Canon cannot provide a stable
+cross-domain contract boundary. Reversal must still name one owner for every
+artifact; returning to undifferentiated "Taxonomy ownership" is not an
+acceptable outcome.