Skip to content
arula

Follow one feature

One administrator requests an override. A different authorized administrator approves it. Pending, rejected and expired overrides stay inactive. Both actors, the reason, state and timestamps remain visible.

Translate the criteria into bounded tasks with permitted files, failing tests and verification commands. Plan approval authorizes implementation, not acceptance.

Apply the plan and retain changes, checks, failures and interventions.

Review finds that application code rejects self-approval but the database permits it. The gate recommends review and holds technical correctness.

Add the database constraint and bypass test, retain the original finding and re-evaluate. Named people sign claims, the client accepts or rejects the feature and live results become the next signal.