flex-auth/examples/secrets-engine/check_request_deny_revoke_not_an_action.json

{
  "id": "check:secrets-engine-revoke",
  "tenant": "tenant:platform",
  "subject": {
    "id": "secrets-engine",
    "type": "service"
  },
  "action": "revoke",
  "resource": {
    "id": "lane:glas-primary",
    "type": "secret-catalog-lane",
    "system": "secrets-engine",
    "attributes": {
      "stage": "prod",
      "fields": [],
      "policy_targets": [],
      "auth_targets": []
    }
  },
  "context": {}
}
Publish secrets-engine.catalog-lane.lifecycle v1 (FLEX-WP-0021 T01, T02) secrets-engine delivered the action vocabulary T01 asked for: twelve actions read out of cli.py, not the example vocabulary. The gate earned its keep -- four would have been inferred wrongly, and revoke, the obvious thirteenth, does not exist as an action at all. It gates as deactivate, which is also reached from lifecycle deactivate. docs/secrets-engine-action-vocabulary.md records the list and the four traps. examples/secrets-engine/ carries the package, both manifests, a loadable registry snapshot, 26 fixtures, five check requests, and a README. validate -kind policy is valid with 22/22 Rego tests and 26/26 fixtures. allow_ttl is 15m, stated in the package rather than inherited from the engine default: these decisions authorize live secret operations, so the reliance window belongs where a reviewer sees it. Per FLEX-DEC-2026-004 it is authority to issue, not authority to keep using what the operation produced. destroy is the dual-control case, gated on a context.approval claim marked approved with two distinct approvers, repeated entries counting once. flex-auth checks what the claim says and deliberately does not re-derive its temporal validity, signature, or supersession -- those are approval-engine's to assert and the PEP's to verify against the live claim, per the split accepted in FLEX-DEC-2026-006. It stays in the package though its handler raises before the gate, so the rule is reviewed and fixtured before SECRETS-WP-0007-T04 opens the path. Following the FLEX-WP-0010-T02 precedent the denial ladder has no action_not_granted branch: one subject holding all twelve actions could never reach it, and a rule that cannot fail reads as control that is not there. Registering a second calling identity is the revisit trigger. Not deployed. No flex-auth-secrets-engine pin exists yet (T04), so their policy pin stays unset and fail-closed until T05. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JTbVXpEiXA7mNJVpDnEPcB Assistant: claude-code Assistant-Model: opus Assistant-Process: 412054@bnt-lap001 Assistant-Session: 3968fae1-8d59-4209-9bd6-c22594b8ab19 2026-09-06 08:02:52 +02:00			`{`
			`"id": "check:secrets-engine-revoke",`
			`"tenant": "tenant:platform",`
			`"subject": {`
			`"id": "secrets-engine",`
			`"type": "service"`
			`},`
			`"action": "revoke",`
			`"resource": {`
			`"id": "lane:glas-primary",`
			`"type": "secret-catalog-lane",`
			`"system": "secrets-engine",`
			`"attributes": {`
			`"stage": "prod",`
			`"fields": [],`
			`"policy_targets": [],`
			`"auth_targets": []`
			`}`
			`},`
			`"context": {}`
			`}`