Harden the PEP harness and KeyCape registration request
Close remaining in-repo APPROVAL-WP-0002 gaps: drive GH-DEC-2026-003 against the real HTTP surface, fail closed on JWT/human-consume/static-token paths, treat audit 200 duplicates as drained, and ask KeyCape for the production audience and client grants. Assistant: grok Assistant-Session: 01a06253-e557-7971-93d9-4f4c2cfbf455
This commit is contained in:
parent
2bd2d19a98
commit
2370f69927
11 changed files with 588 additions and 46 deletions
|
|
@ -22,6 +22,8 @@ Flexibility here would be a defect. Graded, evidence-based progression belongs t
|
|||
See [INTENT.md](INTENT.md) and [SCOPE.md](SCOPE.md). Declaration: [layer.yaml](layer.yaml).
|
||||
Claim: [docs/approval-claim.md](docs/approval-claim.md).
|
||||
Consume: [docs/approval-consumption.md](docs/approval-consumption.md).
|
||||
Caller auth: [docs/caller-authentication.md](docs/caller-authentication.md).
|
||||
PEP sequence: [docs/pep-integration.md](docs/pep-integration.md).
|
||||
Origin: `flex-auth` `FLEX-DEC-2026-001`, raised while assenting to the security
|
||||
layer model.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue