Record GH-DEC-2026-005; strike the spent G3 revisit trigger
Gate House confirmed all three requested dispositions as GH-DEC-2026-005 (GH-IN-0002, closed); flex-auth accepted as FLEX-DEC-2026-006. The approval-claim is the step-1 artifact, ActionAuthorization is not required and MUST NOT be served from the claim endpoint, and a PEP validates across the claim and the step-2 DecisionEnvelope. Gate House recorded the split as doctrine rather than convenience -- a PIP must not republish the PDP's decision -- and struck the provenance.authority == state-hub requirement explicitly. This engine's claim schema is unchanged. Correct the deferred option D trigger list. The G3 trigger was written conditional on G3 being settled by composition; flex-auth reports FLEX-WP-0019 closed it by adding a lifetime field to DecisionEnvelope on 2026-09-02, so a decision now states its own end without borrowing ActionAuthorizationValidity. That was the one structural thing the bundle did that the split does not, so the trigger is not merely spent -- it resolved against ratification. Struck with reasons; a future revisit needs a fresh argument. The trigger came from a stale row in a dated 2026-08-29 review record that flex-auth does not rewrite. Also record the root cause of the bad authority constant: it came from a flex-auth fixture, not prose. A contract whose examples contradict its prose will be implemented as its examples. Close APPROVAL-IN-0002. Docs only; 84 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TvyJPAaVCGsVheVhcCwNND Assistant: claude-code Assistant-Model: opus Assistant-Process: 411227@bnt-lap001 Assistant-Session: d566f6d3-bcaf-43c3-bc5e-3ddd0f64b535
This commit is contained in:
parent
54ced98b84
commit
564534dbcb
4 changed files with 61 additions and 8 deletions
|
|
@ -32,7 +32,7 @@ state_hub_intake_id: "01a05ef0-a034-7ef8-bae1-45840392f40e"
|
|||
id: APPROVAL-IN-0002
|
||||
kind: intake
|
||||
title: Confirm the claim envelope on the PEP consumption path
|
||||
status: open
|
||||
status: closed
|
||||
origin: coordination
|
||||
origin_ref: APPROVAL-WP-0002-T05
|
||||
priority: high
|
||||
|
|
@ -44,6 +44,15 @@ tags:
|
|||
- cross-repo
|
||||
created: '2026-09-06'
|
||||
updated: '2026-09-06'
|
||||
resolution: >-
|
||||
Resolved 2026-09-06. Confirmed in full as GH-DEC-2026-005 (recorded at
|
||||
gate-house as GH-IN-0002 and closed) and accepted as FLEX-DEC-2026-006. The
|
||||
approval-claim is the step-1 artifact; ActionAuthorization is not required
|
||||
and MUST NOT be served from the claim endpoint; PEPs validate across the
|
||||
claim and the step-2 DecisionEnvelope. The provenance.authority ==
|
||||
state-hub requirement was struck explicitly. approval-engine's claim schema
|
||||
is unchanged. The deferred option D G3 revisit trigger is spent: G3 closed
|
||||
by adding a lifetime field, not by composition.
|
||||
description: >-
|
||||
secrets-engine's PEP validator expects a flex-auth ActionAuthorization but
|
||||
calls GET /v1/approvals/{id}/claim, which serves approval-engine's governed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue