Register the approver client now its callback exists

informed-decision submitted client_id informed-decision-approver and redirect
https://decisions.coulomb.social/auth/callback, with the origin already live and
verified by them rather than reported: both / and /auth/callback return 200 on a
Let's Encrypt certificate valid to 2026-12-09. The host is decisions, not the
decide of an earlier draft. Its path serves a placeholder for now, which does not
matter -- the redirect is matched as an exact string and never fetched.

Published as a public authorization_code client with S256 PKCE, audience
approval-engine, scopes openid/approval:read/approval:approve, mfaRequired true
and a declared tenant:platform. No secretRef, since PKCE is the whole proof.

TestApproverRegistrationShapeIsExact pins every field, so widening a scope or
relaxing MFA fails the build rather than reading as an edit, and asserts the
registration passes startup validation -- proving the KEY-WP-0028 tenant
exemption holds for the registration that actually depends on it.

Two existing guards fired on the way in and neither was loosened. The tenant pin
refused an unreviewed client carrying a tenant, which is its purpose, so the
approver was added to its reviewed set deliberately. And the audience test
panicked slicing secretRef[4:], an assumption that held while the fixture had
only confidential clients; the approver is the first public one, so the loop now
guards on the env: prefix.

The declared tenant reaches the token by the GH-DEC-2026-013 gap route by
construction, and tenant_source says so: registration, never directory.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 713576@bnt-lap001
Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6

docs/approval-engine-auth-contract.md

@@ -13,12 +13,32 @@ gets lifecycle/observation scopes without consume. Service tokens contain
 audience, issue time and expiry; the lifetime is 15 minutes. The issuer signs
 with RS256 and publishes its public key through `/jwks`.
 
-Human approvers need a separate authorization-code/PKCE registration with an
-exact deployment-owned callback, `audience: approval-engine`,
-`allowedScopes: [openid, approval:read, approval:approve]`, and
-`mfaRequired: true`. Do not add consume or other approval grants to that client.
-No callback is invented here. The ID token is for the login client; present the
-access token to approval-engine.
+Human approvers use the `informed-decision-approver` registration, submitted by
+informed-decision on 2026-09-10 (INFD-WP-0001-T07) and published in
+`config/service-clients.example.yaml`:
+
+| Field | Value |
+| --- | --- |
+| `clientId` | `informed-decision-approver` |
+| `redirectUris` | `https://decisions.coulomb.social/auth/callback` (exact, sole) |
+| `clientType` | `public` — PKCE is the whole proof; no secret |
+| `grantTypes` | `authorization_code` with S256 PKCE |
+| `audience` | `approval-engine` |
+| `allowedScopes` | `openid`, `approval:read`, `approval:approve` |
+| `mfaRequired` | `true` |
+| `tenant` | `tenant:platform`, declared |
+
+The host is `decisions.coulomb.social`, not the `decide.coulomb.social` an
+earlier draft proposed; the origin was verified live before submission. The path
+currently serves a placeholder while the surface is gated on
+APPROVAL-WP-0002-T01, which does not affect the registration — the redirect is
+matched as an exact string at `/authorize` and never fetched.
+
+Do not add consume or other approval grants to that client. The ID token is for
+the login client; present the access token to approval-engine.
+`TestApproverRegistrationShapeIsExact` pins every field above, so widening a
+scope or relaxing the MFA requirement fails the build rather than passing as an
+edit.
 
 That client must also declare `tenant: tenant:platform`. A human token's tenant
 comes from the directory record, which assigns none today, so without the
@@ -63,10 +83,10 @@ These fragments are not live registrations. The two service registrations requir
 custody-managed values for the named environment references and a reviewed
 rollout of this version, including the upstream issuer precondition. Platform's
 CCR-2026-0017/0018 use OpenBao field `CLIENT_SECRET`; their approval remains open.
-The separate human registration needs its actual UI-owned callback. A bearer-only
-approval resource server has no such callback; its absence does not prevent
-service-client issuance or service startup, and service credentials cannot be
-counted as human approval evidence. Never log the token or secret. Verify the resulting
+The human registration now carries its real UI-owned callback (above); a
+bearer-only approval resource server never owned that string, which is why it
+came from informed-decision. Service credentials still cannot be counted as human
+approval evidence. Never log the token or secret. Verify the resulting
 access token against the deployed issuer's `/jwks`, checking issuer, audience,
 expiry, subject, principal type, tenant, roles, scope and assurance. Verify that
 operator consume and human consume requests are rejected. Local tests verify

docs/approval-engine-provisioning-request.yaml

@@ -34,7 +34,16 @@ requests:
     custody_owner: railiance-platform
     consumer: approval-engine-operator
 human_registration:
-  status: awaiting-exact-callback
+  status: submitted-2026-09-10
+  client_id: informed-decision-approver
+  redirect_uri: https://decisions.coulomb.social/auth/callback
+  # Origin verified live before submission: / and /auth/callback both return 200
+  # from 92.205.62.239 on a Let's Encrypt certificate CN=decisions.coulomb.social
+  # valid 2026-09-10 to 2026-12-09, deployed by railiance-apps. The host is
+  # decisions.coulomb.social, NOT the decide.coulomb.social of an earlier draft.
+  # The path serves a placeholder while the surface is gated on
+  # APPROVAL-WP-0002-T01; the redirect is matched as a string and never fetched.
+  origin_verified: true
   blocks_service_client_rollout: false
   # Owner identified 2026-09-09: informed-decision (hub repo cf4c7da8). It
   # supplies client_id and callback URI from INFD-WP-0001-T07 once it has a
@@ -58,9 +67,16 @@ human_registration:
     directory has not placed the user, requires agreement when it has, and
     refuses issuance on conflict rather than relabelling. Safe only because
     registrations are static and deployment-owned. Still outstanding from
-    elsewhere: the exact client_id and callback URI from informed-decision
-    (INFD-WP-0001-T07), and whether the owners prefer the directory-sourced
-    resolution instead, which this implementation degrades into cleanly.
+    elsewhere: whether the owners prefer the directory-sourced resolution
+    instead, which this implementation degrades into cleanly.
+  resolved_2026_09_10: |
+    client_id and callback URI received and registered. GH-DEC-2026-013 granted
+    the registration-bound shape as a declared bounded gap, so the declared
+    tenant is admissible; the token says how it got there via tenant_source =
+    "registration", never "directory". Per gate-house's later correction the
+    tenant field carries three facts, and a registration-supplied value is
+    adequate for approval-engine's store-isolation gate and NEVER for doctrine
+    turning on this person's membership of the zone.
 verification:
   # The first two lines are now one runnable command per client; see
   # docs/native-authentication.md, "Verifying a live registration". It writes