coulomb/net-kingdom
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Require explicit cadence profile assessment and correct contract pins

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e77d-47a4-7771-8e34-7339c7fac0e4
This commit is contained in:
tegwick 2026-09-28 12:40:07 +02:00
parent 9383b94019
commit 36303d25a3
7 changed files with 281 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

46
workplans/NK-WP-0035-emission-cadence-security-profile.md
View file

@ -10,7 +10,7 @@ owner: codex
topic_slug: netkingdom
planning_priority: P1
created: "2026-09-04"
updated: "2026-09-07"
updated: "2026-09-28"
related:
- GH-DEC-2026-004
- canon/standards/security-layer-model_v0.7.md
@ -122,6 +122,22 @@ checkout. Full reconciliation remains pending because API queries/writes timed
out or returned connection-refused errors. Generated index/intake metadata was
reviewed; the source files remain authoritative.
### Import metadata reconciled — 2026-09-28
Updated the importing profile to candidate document 0.2.0 / wire schema 0.1,
reviewed contract revision `4d0851c3fca306538b53838421f4499baf352778`, and
owner-published candidate bundle digest `b08b4d95fc4b0bd3`. Verified the schema
SHA-256 remains `6d52692eb1e4d1325e0d6062d95acded98beddaae5bcfe24c6f0e91f1b6be6ae`.
Corrected local-identity's current declaration pin and preserved the old pin
with its correction in the historical findings. No emission behavior changed.
All 15 focused cadence tests pass. Revalidation with the two source-owned
rare-class assertions is generic-valid and still returns exactly two
`rare-heartbeat-missing` findings. T04 remains `wait` for external source
migration, observer integration and the explicit local-identity incompatibility
resolution; the profile remains proposed. Metadata repair is complete and does
not count as source/observer adoption.
## Review the layer model's use of the profile
```task
@ -153,3 +169,31 @@ profile, carries the volume/rare split explicitly, and states that
classification is the source's to publish and never the checker's to infer.
Change log item 6 and §14 record the review; the standard remains `proposed` and
publication waits on the close of the circulation round.
## Infrastructure review — 2026-09-28
T04 remains `wait`, but upstream publication is no longer the blocker.
The current generic document is candidate 0.2.0 with wire schema 0.1;
InfoTechCanon corrected the candidate bundle digest to `b08b4d95fc4b0bd3`
(the wire schema was unchanged). Review and update the profile's old
draft/document/revision description and local-identity's stale bundle pin
against the exact owner artifact before handoff; do not confuse a bundle digest
with the schema SHA-256.
Approval Engine and Qonto still carry draft-shaped owner envelopes. In addition,
NetKingdom now has its own source declaration at
`local-identity/emission-cadence.yaml`: generic validation passed, but both
rare load-bearing entries lack the required heartbeat. The source has no
audit-core sender/feed; its findings also record dropped audit I/O errors and
no completeness claim. Generic validity is not security-profile conformance
or an operating observer result.
Extend T04 acceptance to cover the local source explicitly: either implement
and evidence activity-scoped heartbeat/reconciliation with its owners, or
retain the documented incompatibility without claiming profile-wide adoption.
Resolve the declared heartbeat event class versus audit-core's registered
`heartbeat_classes` mapping, migrate the two external owner instances, and
obtain a real source/observer result before the King's Guard handoff. Keep
the profile proposed; no weakened rare-class conjunction is approved.
Evidence and cross-plan priorities: [estate review](../history/2026-09-28-open-workplan-infrastructure-review.md).