# Ticket: Autonomous ticket execution and scheduled audits

## Metadata
- Type: Ticket
- Status: Done
- Project: Nimrod / Agent Operations
- Created: 2026-06-06
- Updated: 2026-06-06
- Priority: High

## Goal

Move Nimrod toward safe autonomous ticket execution: selecting tickets, creating focused subagents, obtaining appropriate authorization, implementing bounded slices, independently verifying work, closing tickets, and eventually running scheduled audit/improvement agents.

## Why

The user wants Nimrod to complete tickets proactively, not just create process. Tickets often intertwine, people and agents make mistakes, and meaningful work should be checked by multiple context-isolated agents before completion.

## Scope

Included:
- Document autonomous ticket execution model
- Define multi-agent verification before done
- Define authorization levels for ticket work
- Define how intertwined tickets/dependencies are handled
- Define future scheduled audit agent categories
- Connect the model to existing QRSPI, DevOps, handover, and ticket triage docs

Not included:
- Implementing always-on scheduled agents yet
- Granting mutation autonomy without controls
- Replacing user approval for risky/security-sensitive changes

## Acceptance Criteria

This ticket is done when:
- [x] `docs/autonomous-ticket-execution-model.md` exists
- [x] `AGENTS.md` links to the model — line 195 in the Key Retrieval Map
- [x] Ticket closeout/review expectations are reflected in relevant workflow docs
- [x] At least one active ticket is completed using triager → implementer → reviewer/closer pattern — used throughout this session (backup standard, repo isolation, Unbound restore test, etc.)
- [x] Future scheduled audit agents are tracked as follow-up work — listed in the model doc under 'Scheduled Agents — Future Direction'

All ACs satisfied.

## Notes

- Verification/Definition of Done standard: `docs/verification-and-definition-of-done.md`.
- User emphasized that completing tickets should be the focus.
- User emphasized multiple contexted agents checking work before completion.
- Example dependency issue: Vaultwarden work created an Nginx server inside the same container while a broader Nginx reverse-proxy standard ticket exists.