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:
tegwick 2026-09-02 15:46:06 +02:00
parent 2bd2d19a98
commit 2370f69927
11 changed files with 588 additions and 46 deletions

View file

@ -96,14 +96,18 @@ systems. Consumption follows the assented `GH-DEC-2026-003` contract.
## Current State
- Status: **first-cut spine**. SQLite-backed object, closed machine, local
outbox, WSGI introspection API, claim contract. Not a production deploy.
- Status: **production-packaged spine, not yet live**. Authenticated HTTP
mutations, schema-v2 SQLite, outbox drain to audit-core, digest-pin-ready
image and single-writer StatefulSet, and a fail-closed PEP harness exist in
this repository. Live rollout, KeyCape audience/client proof, audit-core
sender registration, and a served secrets-engine consume binding remain
external gates on `APPROVAL-WP-0002`.
- Layer declaration: INTENT frontmatter + `layer.yaml`. Cadence declared in
`cadence.yaml`. No Tooling contacts.
- Consumption is public at `POST /v1/approvals/{id}/consume` under
`GH-DEC-2026-003`; the endpoint is a lifecycle mutation, never a decision.
- Taxonomy request-claim schema is still unassigned; the local claim yields.
- Work: `APPROVAL-WP-0001`. Tests: `make test`.
- Work: `APPROVAL-WP-0002`. Tests: `make test`.
## How It Fits