Decide where the work belongs
Name the role cost
Describe what owners, reviewers, and observers can or cannot do from the event. Compare a hidden action with a visible rejection and a useful read-only destination. Keep a permission failure separate from a stale target.
Compare scope remedies
Set role-aware action visibility, disabled explanation, read-only detail, fallback route, and unchanged control beside one another. Consider target state and recovery. Prefer a repair that makes authority legible without exposing sensitive action controls.
Choose a bounded move
Record role, resource state, owner, and revisit evidence. Decide whether to adjust visibility, label, destination, or state fallback. Preserve current owner and read-only paths so the queue decision can be checked.
What to carry forward
Prioritize action-scope work where visible controls mislead a role or hide the safe review path. The decision should name role and state boundaries. If the response is clear and only one rare state is untested, queue that state separately.
Technical background: Apple developer documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow