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

docs(workplan): align managed workload declaration wording
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02929-244b-7391-b933-c04010e8eedb
This commit is contained in:
tegwick 2026-08-22 14:55:10 +02:00
parent db2ef631c6
commit a286b91652
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
workplans/NK-WP-0027-reef-placement-reconciliation.md
View file

@ -172,9 +172,11 @@ state_hub_task_id: "d60e209d-3090-59e7-afc4-0a3780507403"
applications.** In the `security-zones_v0.1` publication review, require a
stable workload identity and responsible party for operational/control-plane
units, and a machine-readable join from credential/control resources to the
workload they serve. Do not require `rapp` packaging merely to gain identity,
and do not infer the join from path strings or repository ownership. Coordinate
the declaration boundary with `zone-engine`, `repo-manager`, and the affected
workload they serve. Require the authoritative rapp declaration for managed
deployables, but do not invent a workload or rapp for native non-workload
subjects or independently governed units that are not managed deployables. Do
not infer the join from path strings or repository ownership. Coordinate the
declaration boundary with `zone-engine`, `repo-manager`, and the affected
control owners.
**Done 2026-08-22.** Tenancy Posture draft-12 Decision 5.6.2 and its schema now