Rituals views: parlays and approvals (requester and approver) #183
Labels
No labels
build-dist
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Toilville/toilville-design#183
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #177. Revised: widened from "waiting on approval" to the full set of parlay and approval views.
What it's for: house-style views for parlays (steward decisions) and grant approvals, on both sides: the person waiting and the person deciding. Approve, dismiss and deny are commands with inputs (dismiss and deny need a reason).
Today
ritual parlay list/show/approve/dismissin the terminal; dismissing needs--whyritual steward grantopens a browser sign-in and the terminal waitsparlayblock renderer, but no served view uses itPlease design
Acceptance criteria
peterswimm referenced this issue from Toilville/rituals-api-spec2026-10-04 20:21:33 +00:00
Rituals pattern: waiting on approval (grants, stewards, sign-in)to Rituals views: parlays and approvals (requester and approver)