coulomb/informed-decision
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Ask Flex Auth list, not read, for each overview row (INFD-WP-0004-T03)

Browse source 
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:
tegwick 2026-09-21 22:53:31 +02:00
parent 180370ed44
commit 98c8de078e
10 changed files with 85 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/flex-auth-review-contract.md
View file

@ -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