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
|
|
@ -2,7 +2,8 @@
|
|||
|
||||
2026-10-04; `INFD-WP-0007-T02/T03`. This is the internal persistence slice of
|
||||
`DecisionLifecycleService.md`. The protected application interface built on this
|
||||
slice is documented in `LifecycleServiceContract.md`; HTTP exposure is pending.
|
||||
slice is documented in `LifecycleServiceContract.md`; the deployed private HTTP
|
||||
adapter is specified in `LifecycleHTTPContract.md`.
|
||||
|
||||
## Implemented boundary
|
||||
|
||||
|
|
@ -16,8 +17,8 @@ Each call carries `Attribution(tenant, Actor(subject, kind))` from its trusted
|
|||
caller. This is audit attribution, not an authentication assertion. Like `Store`,
|
||||
the repository is an internal persistence interface: the application/API
|
||||
layer must authenticate callers and enforce current access-engine authorization
|
||||
before invoking it. Supplying a tenant string is not an access grant. No route
|
||||
or runtime configuration exposes these operations in this increment.
|
||||
before invoking it. Supplying a tenant string is not an access grant. The deployed application adapters authenticate and authorize these operations;
|
||||
this internal persistence interface is never exposed directly.
|
||||
|
||||
## Commands and reads
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue