Permissions, data & business rules · Verify

RBAC ABAC Matrix Check

Verify one RBAC/ABAC policy matrix or patch through bounded allow/deny scenarios. Prove the selected actor/resource/action/scope contract without reopening unrelated auth audit work.

Vibe Coding 1.3.0 · vibe-domain · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-domain, workflow “RBAC ABAC Matrix Check” (ID: rbac-abac-matrix-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Goal

Verify one RBAC/ABAC policy matrix or patch through bounded allow/deny scenarios. Prove the selected actor/resource/action/scope contract without reopening unrelated auth audit work.

Required input

Provide the selected role/attribute matrix, resource/action, expected allow/deny states, implementation summary or patch boundary, safe environment, fixtures/accounts, and repository-native commands.

Scenarios

Exercise allowed and denied actors across relevant tenant/resource scopes.
Verify ABAC attributes at their source: ownership, membership, region, status, relationship, plan, quota, or feature flag.
Check unauthenticated, wrong-tenant, missing attribute, stale attribute, no-plan, over-quota, and admin/impersonation cases when relevant.
Confirm UI affordance and backend enforcement agree, with safe error/no-access behavior.

Workflow ID: rbac-abac-matrix-check · View the versioned source · Shared workflow and authority rules