Implement role ladder, Admin grants, and fail-closed authorization #4

Closed
opened 2026-07-19 23:26:30 +02:00 by thecrealm · 1 comment
Owner

Acceptance: §2.6 (ladder), §4.2 (Admin-only grants, audit-logged §10), §4.3 (permission matrix incl. approver≠author), §4.4 fail-closed. Tests reference CR-8.

Acceptance: §2.6 (ladder), §4.2 (Admin-only grants, audit-logged §10), §4.3 (permission matrix incl. approver≠author), §4.4 fail-closed. Tests reference CR-8.
thecrealm added
now
and removed
next
labels 2026-07-20 15:34:40 +02:00
Author
Owner

Live on prod (d031912): strictly ordered ladder with per-request role resolution (grants effective immediately, §4.2), Admin-only grant/revoke/suspend with actor+reason and append-only Admin-only audit log (§10, cursor-paginated §9.2), approver≠author rule with Admin break-glass (§4.3, enforcement point lands with proposals), BOOTSTRAP_ADMIN startup seed (D15). CR-8 verified in 12 new tests and live on prod: 401 unauthenticated, 404-indistinguishable staff surface. Admin elevation on prod intentionally left to the operator: register your account, append BOOTSTRAP_ADMIN= to /opt/mokuroku/.env, docker compose up -d server (runbook).

Live on prod (d031912): strictly ordered ladder with per-request role resolution (grants effective immediately, §4.2), Admin-only grant/revoke/suspend with actor+reason and append-only Admin-only audit log (§10, cursor-paginated §9.2), approver≠author rule with Admin break-glass (§4.3, enforcement point lands with proposals), BOOTSTRAP_ADMIN startup seed (D15). CR-8 verified in 12 new tests and live on prod: 401 unauthenticated, 404-indistinguishable staff surface. Admin elevation on prod intentionally left to the operator: register your account, append BOOTSTRAP_ADMIN=<name> to /opt/mokuroku/.env, docker compose up -d server (runbook).
thecrealm 2026-07-20 16:03:31 +02:00
  • closed this issue
  • removed the
    now
    label
Sign in to join this conversation.
No labels
M0
M1
M2
M3
M4
M5
blocked
next
now
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/mokuroku#4
No description provided.