Connect lifecycle revisions to protected human review
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
parent
0e79d69e27
commit
f3b71b1521
16 changed files with 649 additions and 23 deletions
|
|
@ -16,9 +16,9 @@ rendering a button grants no authority.
|
|||
Publication records an audience for one revision. Access Engine determines access
|
||||
using authenticated identity and retained record facts. Publication creates no
|
||||
approval and no human disposition. New revisions require their own publication.
|
||||
The workspace explicitly states that human acceptance is unavailable for these
|
||||
drafts. Connecting a lifecycle revision to the existing protected presentation
|
||||
and Approval Engine path remains T03/T05 work.
|
||||
The workspace exposes authorized outcomes and a protected human review link
|
||||
when an exact revision handoff has been loaded by intake. Drafts without that
|
||||
handoff remain unavailable for acceptance. See LifecycleReviewHandoff.md.
|
||||
|
||||
## Runtime and deployment inputs
|
||||
|
||||
|
|
@ -64,7 +64,8 @@ and API ingress. The policy must cover all actions in LifecycleServiceContract,
|
|||
including collection search and per-record checks. Existing compact-sitting pins
|
||||
do not supply these grants. WP-0005 retains private intake composition work.
|
||||
|
||||
T03/T05 require the durable review handoff and human-only acceptance integration.
|
||||
The source handoff now integrates human-only acceptance for the admitted intake
|
||||
profile; T03/T05 retain broader profiles and browser authoring/forwarding work.
|
||||
T06 requires full acceptance evidence, sender/cadence admission, immutable image,
|
||||
database backup/migration and rollback verification. T07 requires the separately
|
||||
approved concrete live rollout. No production pins or resources changed here.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue