Name access-engine as the only authorization decision point.

Assistant: grok
Assistant-Session: 01a0d25d-d358-7e13-b84a-d007fbb7e34f

INTENT.md

@@ -55,7 +55,8 @@ Core principle:
 
 - Fetches secrets only via the sanctioned OpenBao path (ops-warden catalog
   `binky-qonto-api` / CCR-2026-0008 pattern).
-- Optional flex-auth gate: `finance.qonto.read` (and later finer scopes).
+- Optional access-engine gate: `finance.qonto.read` (and later finer scopes).
+  The repository is still `flex-auth`.
 - Audit metadata (who/what/decision) without logging secret material.
 
 ### As dogfood for Operational Knowledge
@@ -85,8 +86,8 @@ them with operational bank visibility.
    assistant alone authenticates *to Qonto*.
 4. **Semantic policy, not vendor dump** — we design a safe catalog; we do
    not auto-mirror vendor write tools.
-5. **Platform fit** — flex-auth, OpenBao, ops-warden, State Hub evidence; no
-   parallel IAM.
+5. **Platform fit** — access-engine (repository `flex-auth`), OpenBao,
+   ops-warden, State Hub evidence; no parallel IAM and no second decision point.
 6. **Autonomy lanes** — map to binky-control AutonomyPolicy: reads Green/Blue;
    plan change / transfers / API key minting remain Red.
 
@@ -114,7 +115,7 @@ them with operational bank visibility.
 | `ops-warden` / `railiance-platform` | Credential front door and CCR/policy for `tenants/…/qonto-api` |
 | `agent-harness` | Grants profile `finance-qonto-read` pointing at this service only |
 | `llm-connect` | Models that *talk*; this service *acts* on bank data |
-| `flex-auth` | Authorization decisions for who may call |
+| `access-engine` (`flex-auth`) | Authorization decisions for who may call |
 | `email-connect` | Sibling pattern: purpose-built connector, not raw vendor wiring |
 
 ## Success looks like