2026-09-23 20:08:46 +02:00
|
|
|
---
|
|
|
|
|
id: NK-WP-0040
|
|
|
|
|
type: workplan
|
|
|
|
|
title: "Define an execution-attribution receipt for Railiance runs"
|
|
|
|
|
domain: infotech
|
|
|
|
|
repo: net-kingdom
|
2026-09-24 01:23:00 +02:00
|
|
|
status: ready
|
2026-09-23 20:08:46 +02:00
|
|
|
flavor: planning
|
|
|
|
|
owner: claude-code
|
|
|
|
|
topic_slug: netkingdom
|
|
|
|
|
created: "2026-09-23"
|
2026-09-24 01:23:00 +02:00
|
|
|
updated: "2026-09-24"
|
2026-09-23 20:08:46 +02:00
|
|
|
related: [RCLK-WP-0002]
|
2026-09-23 20:10:51 +02:00
|
|
|
state_hub_workstream_id: "e2533f3a-aa43-59b3-bff3-8e64b6149487"
|
2026-09-23 20:08:46 +02:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
Raised by the railiance-clock identity review
|
|
|
|
|
(`history/2026-09-23-railiance-clock-identity-and-layer-review.md`, Ruling 1).
|
|
|
|
|
IAM Profile v0.3 defines who acts: human, service and agent principals, and
|
|
|
|
|
delegation. Playbook Capability Contract v0.1 defines what is selected and who
|
|
|
|
|
is responsible. No NetKingdom contract defines the record that ties **one
|
|
|
|
|
execution** to its actor chain, artifact and result.
|
|
|
|
|
|
|
|
|
|
## Draft the receipt fields as a Playbook Capability Contract amendment
|
|
|
|
|
|
|
|
|
|
```task
|
|
|
|
|
id: NK-WP-0040-T01
|
|
|
|
|
status: todo
|
|
|
|
|
priority: medium
|
2026-09-23 20:10:51 +02:00
|
|
|
state_hub_task_id: "9d02685a-a3d9-5b9f-b09e-aef1f196a97f"
|
2026-09-23 20:08:46 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Draft a v0.2 amendment that adds an execution-attribution receipt with these
|
|
|
|
|
fields:
|
|
|
|
|
|
|
|
|
|
- issuer and subject of the initiating actor
|
|
|
|
|
- delegation reference (`actor_sub`/`act.sub`) when present
|
|
|
|
|
- executing workload binding and runtime principal
|
|
|
|
|
- tenant and environment
|
|
|
|
|
- run ID
|
|
|
|
|
- source commit and artifact digest
|
|
|
|
|
- target inventory reference and action
|
|
|
|
|
- decision and approval IDs
|
|
|
|
|
- attributed time interval, with its clock source and bound when one exists
|
|
|
|
|
|
|
|
|
|
The receipt must never embed bearer credentials. Unknown attribution is kept
|
|
|
|
|
explicit, not inferred. Start from the field list in railiance-clock's review.
|
|
|
|
|
|
|
|
|
|
## Agree the evidence holder and schema with audit-core and Railiance
|
|
|
|
|
|
|
|
|
|
```task
|
|
|
|
|
id: NK-WP-0040-T02
|
|
|
|
|
status: todo
|
|
|
|
|
priority: medium
|
2026-09-23 20:10:51 +02:00
|
|
|
state_hub_task_id: "963120c1-7c72-5806-942b-6f49e4c66e54"
|
2026-09-23 20:08:46 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
audit-core holds evidence (layer model §3.3, Evidence role). Railiance
|
|
|
|
|
executes and emits. Agree who emits, who holds and how the receipt is
|
|
|
|
|
validated. Add a schema under `canon/schemas/` and a validator beside the
|
|
|
|
|
existing playbook-capability tooling.
|
