Require a bounded purpose record before support elevation
An agent opens account settings using permanent elevated access with no connection to a support case.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Privileged access · Scoping
Estimated field mix
- Security80%
- Backend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional support console can reveal protected account settings and run repairs. The team needs bounded elevation, clear reasons and durable records of what happened.
Setup prerequisites
- Create synthetic support actors and organizations.
- Implement a local authorization boundary and append-only audit store.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Record target organization, permitted actions, reason and expiry.
- Require an authorized actor to request elevation.
- Reject empty purpose or an excessive lifetime.
Implementation constraints
- Use synthetic case references without copying case conversations.
Verification to include
- Create a scoped time-limited elevation.
- Request a different organization's action outside the grant and deny it.
Deliverables
- Elevation request contract
Rollout and recovery
Canary grants for synthetic actors; revoke active test grants if policy checks fail.
Value of the work
For the engineer: Practice privileged workflows, denial paths and audit integrity.
For the team: Review accountable support operations without unnecessary access to customer data.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.