Implement USER-WP-0024 security layer conformance
Declare Engine/PIP machine-readably, publish a total fail-closed PEP stance map, stop minting local decision ids on engine-unavailable DENY, bind allows to a 30s request lifetime, confine the local authorization double, classify evidence and emit a denial/revocation heartbeat, and prove access-control facts remain claims. Assistant: grok Assistant-Session: 01a04cea-f0d6-7ab3-9ffd-881eb6bea6cb
This commit is contained in:
parent
c7b6148a70
commit
4349758608
22 changed files with 1242 additions and 89 deletions
|
|
@ -1,12 +1,17 @@
|
|||
# Evidence Gap Examples
|
||||
|
||||
Status: candidate
|
||||
Updated: 2026-06-05
|
||||
Updated: 2026-08-29
|
||||
|
||||
`user-engine` should not pretend missing review or governance material exists.
|
||||
When identity-domain context lacks evidence, policy, control, review, or task
|
||||
references, the gap must be explicit and handoff-ready.
|
||||
|
||||
Local audit and the durable outbox prove the records they hold were not
|
||||
altered or truncated after arrival. Absence of a record is not evidence
|
||||
of non-occurrence. Classification and the denial/revocation heartbeat
|
||||
are in `docs/evidence-classification.md`. Completeness is not claimed.
|
||||
|
||||
## Gap Shape
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue