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:
parent
dfcef879d0
commit
da2c5a720f
9 changed files with 224 additions and 10 deletions
|
|
@ -163,8 +163,9 @@ document supersedes their exclusion of agent collaboration and human authoring
|
|||
for the new increment, while preserving human-only dispositions and the evidence
|
||||
and engine boundaries. L0 and L2 compatibility remain required.
|
||||
|
||||
Open implementation contracts: workload identity beyond cluster service accounts;
|
||||
publication audience policy and any later anonymous publication; source connector
|
||||
set and retention; non-approval L2 binding integration. T02 must make these
|
||||
explicit before implementation depends on them. None authorizes a production
|
||||
rollout or changes external owners' contracts by declaration.
|
||||
Initial implementation choices are explicit in `LifecycleAdmissionBoundary.md`:
|
||||
only the admitted cluster workload, authenticated publication, caller-supplied
|
||||
research provenance, append-only retention, organizational human approval, and
|
||||
no optional Hub outcome write-back. External identities, anonymous publication,
|
||||
source connectors/retention controls and non-approval binding are expansion work
|
||||
under INFD-WP-0008, not hidden prerequisites or enabled production capabilities.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue