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
|
|
@ -4,9 +4,12 @@
|
|||
|
||||
Use `readiness()` for dependency checks and `operability_snapshot()` for
|
||||
runtime counters and invariant checks. The snapshot currently reports store
|
||||
readiness, audit correlation completeness, outbox diagnostic availability, and
|
||||
counts for users, accounts, tenant accounts, memberships, applications,
|
||||
catalogs, profile values, audit records, and pending outbox events.
|
||||
readiness, whether written audit records carry a correlation id, outbox
|
||||
diagnostic availability, and counts for users, accounts, tenant accounts,
|
||||
memberships, applications, catalogs, profile values, audit records, and
|
||||
pending outbox events. Those checks describe the records in hand. They
|
||||
do not prove that every event that should have been emitted was emitted.
|
||||
See `docs/evidence-classification.md`.
|
||||
|
||||
## Structured Logs
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue