---
id: ITC-WP-0018
type: workplan
title: "EmissionCadenceDeclaration semantic contract"
domain: infotech
repo: info-tech-canon
status: finished
owner: codex
topic_slug: emission-cadence
priority: high
created: "2026-09-04"
updated: "2026-09-04"
spec_refs:
  - infospace/assimilation/emission-cadence/ASSIMILATION.md
  - infospace/standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
  - infospace/schemas/emission-cadence.schema.yaml
state_hub_workstream_id: "78f879cf-f097-5ee5-8f6a-15e34209822d"
---

# ITC-WP-0018 — EmissionCadenceDeclaration Semantic Contract

## Goal

Adopt the King’s Guard handover as the ecosystem-wide, versioned semantic
contract for declaring expected stream emission, while leaving NetKingdom
security obligations in the importing NetKingdom profile.

## T01 — Review ownership and assimilate the handover

```task
id: ITC-WP-0018-T01
status: done
priority: high
state_hub_task_id: "b6cba288-1edf-557c-b692-cd24058fb9d6"
```

Preserve the handed-over draft, compare its concepts with the existing
Observability and Governance models, and record the authorized `adapt`
disposition from `GH-DEC-2026-004`.

## T02 — Publish the generic contract and validation schema

```task
id: ITC-WP-0018-T02
status: done
priority: high
state_hub_task_id: "cca8a6e6-03fe-50a1-9f0d-84cbc8b92cac"
```

Publish the generic forms, fields, validation semantics, compatibility rules,
and a non-authoritative worked example. Do not encode the NetKingdom rule that
rare load-bearing classes require heartbeat plus reconciliation.

## T03 — Register, retrieve, validate, and announce

```task
id: ITC-WP-0018-T03
status: done
priority: high
state_hub_task_id: "9df9fd50-26e0-531e-a0a2-9f92eed5f2b3"
```

Register the artifact and schema, regenerate retrieval assets, run the full
validation and test suite, and notify the handing-over and deciding repositories.

## Acceptance

- InfoTechCanon is the sole owner of `EmissionCadenceDeclaration` semantics.
- The schema validates both generic forms and rejects incomplete form payloads.
- NetKingdom-specific evidence classes and MUST/SHOULD policy are not defined here.
- The artifact is discoverable through the CLI/JSON/API retrieval surfaces.
- Generated assets, validation, tests, work records, and State Hub agree.

## Result

Completed 2026-09-04 in canon 0.7.0. The handed-over draft was adapted into the
generic standard and schema, the security-profile boundary was preserved, the
worked example and structural validation were published, and all retrieval
assets were regenerated. `make validate` reports 0 errors and 0 warnings;
`make test` passes 29 tests.