Add recipient-scoped review discovery and settle initial lifecycle contracts

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
tegwick 2026-10-05 01:03:05 +02:00
parent dfcef879d0
commit da2c5a720f
9 changed files with 224 additions and 10 deletions

View file

@ -42,7 +42,7 @@ boundary, revision/evidence semantics and acceptance without per-decision deploy
```task
id: INFD-WP-0007-T02
status: progress
status: done
priority: high
state_hub_task_id: "cde0c932-afce-5bec-8cee-a2f377955b9f"
```
@ -389,3 +389,21 @@ synthetic identity, including mobile and desktop inspection. Evidence is retaine
in docs/evidence/2026-10-05-lifecycle-authoring/. This source increment is not yet
released; production remains on the accepted initial cutover image. T02/T05 stay
in progress for broader contracts and attribute-based legacy review discovery.
## Authoring deployed; discovery continuation — 2026-10-05
Founder explicitly requested deployment and the remaining implementation.
ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED. Authoring image
79aabf37 is live through Argo source dfcef87 and Platform pin 0189965. Both health
endpoints and Argo Synced/Healthy pass. Fresh backup/isolated restore preserved
25 confirmed submissions, 174 delivered outbox rows, two records/nine events.
Native selected-workload GET retrieves the exact retained handoff and confirms
the prior human disposition. No new human acceptance is fabricated.
T02 now records explicit initial contracts in LifecycleAdmissionBoundary.md.
Expansion residuals have live records INFD-WP-0008-T01 through T04: external
identity/publication, connectors/retention controls, non-approval binding, optional
Hub write-back. T05 implements named-recipient review discovery in the consumer
and Access Engine FLEX-WP-0034 v13, with fresh read/act checks retained. Validation
671 passed, one skipped; 32 owner embedded policy checks plus owner regressions.
Discovery release and final native checks remain in progress.

View file

@ -0,0 +1,70 @@
---
id: INFD-WP-0008
type: workplan
title: "Lifecycle expansion beyond the initial production audience"
domain: infotech
repo: informed-decision
status: backlog
owner: codex
topic_slug: netkingdom
created: "2026-10-05"
updated: "2026-10-05"
origin: residual
origin_ref: INFD-WP-0007
---
Initial production choices are recorded in docs/specs/LifecycleAdmissionBoundary.md.
This workplan preserves expansion work without claiming it was delivered by the
initial organizational approval service. These tasks do not authorize live changes.
## External workload identity and expanded publication
```task
id: INFD-WP-0008-T01
status: todo
priority: medium
```
Contract with KeyCape and Access Engine for agents outside cluster TokenReview,
additional tenants/audiences and any anonymous publication. Retain per-record
policy and authentication-derived attribution; do not treat arbitrary JWT claims
as admission. Initial authenticated publication remains the supported path.
## Source connector and retention controls
```task
id: INFD-WP-0008-T02
status: todo
priority: medium
```
Select actual source connectors and define their retrieval/credential boundaries,
network restrictions, content limits and provenance. Define retention/export/
erasure requirements and owner review before introducing deletion. Existing
caller-supplied evidence and append-only custody remain the default.
## Non-approval binding profiles
```task
id: INFD-WP-0008-T03
status: todo
priority: medium
```
Define and implement non-approval L0/L2 presentation/disposition workflows against
the shared schema with the identity, authorization and audit owners. Do not create
an Approval Engine object solely to simulate an unrelated binding act. Preserve
schema compatibility, human-only binding and revision-specific evidence.
## Optional State Hub outcome write-back
```task
id: INFD-WP-0008-T04
status: todo
priority: low
```
Independently admit and verify optional resolution write-back with State Hub.
Keep explicit correlation, replay, and uncertain-outcome recovery; a human answer
must never become an execution authorization. Current notification delivery and
agent outcome retrieval remain available without automatic write-back.