Ask Flex Auth list, not read, for each overview row (INFD-WP-0004-T03)
The overview now requests the new list action and its rows carry only the memo id, version, question, live approval status and the person's own responses without notes. Opening a memo still asks read; every act asks its own action. The fixture Flex Auth package admits list under a re-derived pin. Not deployable until flex-auth answers INFD-IN-0008. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 359683@bnt-lap001 Assistant-Session: eebdc939-7a9b-4e50-9d39-c8437e8a14ec
This commit is contained in:
parent
180370ed44
commit
98c8de078e
10 changed files with 85 additions and 33 deletions
|
|
@ -3,7 +3,7 @@
|
|||
**From:** informed-decision (`INFD-WP-0004`, intake `INFD-IN-0008`)
|
||||
**To:** flex-auth, as the owner of the `informed-decision.*` policy packages
|
||||
**Date:** 2026-09-21
|
||||
**Status:** draft, not yet sent
|
||||
**Status:** sent 2026-09-21 to the flex-auth inbox (State Hub message `a7b9ef3b-f95c-4c50-bfc5-7628d16881f6`)
|
||||
|
||||
## What we ask
|
||||
|
||||
|
|
|
|||
|
|
@ -61,8 +61,13 @@ mandate from membership, the named recipient match or a successful login.
|
|||
|
||||
The assurance object above is illustrative; `build_request` carries the verified
|
||||
issuer object without synthesizing stronger facts. Supported actions are
|
||||
`read`, `acknowledge`, `accept`, `return`, `discuss`, `decline`. Read covers memo
|
||||
rendering, original presentation retrieval and packet download. Other verbs
|
||||
`read`, `list`, `acknowledge`, `accept`, `return`, `discuss`, `decline`. Read covers memo
|
||||
rendering, original presentation retrieval and packet download. `list` covers only
|
||||
one row of the signed-in person's decision overview (`INFD-WP-0004`): the memo id,
|
||||
version and question, the live approval status, and the person's own responses
|
||||
(verb, version, time and submission state, without notes). It never covers the
|
||||
brief, terms, highlights, packet or others' responses, and it never stands in for
|
||||
`read` or an act. See [the list-action request](flex-auth-request-list-action.md). Other verbs
|
||||
always get their own decision. Only accept can cause an Approval Engine POST.
|
||||
No `consume`, wildcard action, `view_hash`, presentation id, acknowledgment
|
||||
state or presentation claim is supplied. This prevents the renderer's evidence
|
||||
|
|
|
|||
|
|
@ -99,9 +99,11 @@ responses on every version.
|
|||
The overview is not an inbox and not approval state:
|
||||
|
||||
- **It checks permission per row.** Each row gets its own fresh Flex Auth
|
||||
`read` decision before its question is shown. It is the same check the
|
||||
review uses, and each decision is stored as a policy observation. A refused
|
||||
row does not call Approval Engine.
|
||||
`list` decision before its question is shown, and each decision is stored as
|
||||
a policy observation (`INFD-WP-0004`). `list` is not `read`: opening the
|
||||
memo still asks `read`, and each act asks its own action. A refused row does
|
||||
not call Approval Engine. Until the served package answers `list`, every row
|
||||
shows as Not available.
|
||||
- **It reads Approval Engine by id only.** The overview looks up the approval
|
||||
id the memo already carries. It never polls for work. The status is shown
|
||||
live and never stored. An unavailable engine, or an act digest that no longer
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue