Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Stale work tickets make it hard to tell which agent tasks still need attention and which can be closed.
Agent job
Check Code Queue records, report work status in Slack and propose stale-ticket cleanup.
Expected output
A status report and proposed ticket changes.
Where this framing comes from
Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
An old agent-work ticket can be genuinely abandoned, completed without a status update or blocked while someone still expects a result. Closing tickets by age alone makes the queue tidier but risks erasing unfinished commitments.
This job could separate completion evidence from inactivity in a review list. Linked artifacts and explicit uncertainty let the owner decide which tickets can close and which still need attention.
Why an agent / simpler alternative
Useful judgment
Reconcile ticket history with available work results and explain why a cleanup action is proposed.
Simpler alternative
Use a simple age report when the user only needs a list of inactive tickets.
Unsuitable when
Completion evidence is unavailable or the agent is expected to infer approval from silence.
Proposed inputs
Name
Queue snapshot
Owner
Queue owner
Minimum scope
Selected ticket IDs, statuses, assignees and update history
Quality check
Use a consistent capture time and retain linked work references.
Name
Cleanup criteria
Owner
Queue owner
Minimum scope
Definitions of completed, blocked, abandoned and still active
Quality check
Require explicit closure approval and identify exceptions.
Access and setup — proposed or unknown
Proposed minimum
Read scoped queue/API records and prepare a status report with proposed changes.
Compatibility unknowns
Unknown: Code Queue fields, MCP access, Slack routing and current scheduling support.
External actions requiring approval
Closing or editing tickets, posting reports or creating recurring status schedules.
Expected deliverable and review checks
Proposed artifact
Ticket review list with current state, evidence, proposed action and owner approval status.
Critical checks
No inactivity-only inference is presented as proof of completion.
Every proposed closure names the exact ticket and preserves unresolved dependencies.
Missing output evidence
No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.
Failure signals and proposed responses
Signal
A ticket has no recent comment but its linked task is still running.
Why it matters
Cleanup could conceal active work and confuse monitoring.
Proposed response
Retain it as active and report the latest verified task state.
Signal
A completion message lacks the expected artifact.
Why it matters
The queue may be closed while the deliverable remains missing.
Proposed response
Flag completion as unverified and request the artifact before proposing closure.
Effort and cost — unknown
Setup work
Define status evidence and map ticket links to their underlying work.
Ongoing review
Review stale candidates and reconcile approved changes with actual queue state.
Unknowns
Unknown: API limits, report costs and effort to verify older artifacts.
First check — proposed, unexecuted
Status
proposed_unexecuted
Synthetic fixture
A fictional queue contains an inactive-looking running task, a claimed completion without an artifact and a verified finished task.
Acceptance checks
Only the verified task receives a closure proposal.
All records remain unchanged until specific owner approval.
Stop conditions
The system requires unapproved closure or the underlying task state cannot be read.
Limits
A cleanup recommendation is not permission to close a ticket; completion evidence and owner approval remain separate requirements.
Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
OpenAI DotsIndependent testing: No
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.