OBSERVATORY 00 — MAINTENANCE SIGNALS
A spatial guide to the persistent AI roles that notice what falls out of orbit, wake with context, and keep engineering systems in motion.
Maintenance is not a task you finish. It is a role you keep.
40°42′46″ N / 74°00′21″ WSTATIC FALLBACK / SIGNAL FIELD
The maintained orbit remains legible without WebGL. Use the chapter rail or scroll to move through signal, role, and boundary states.A persistent role watches the system, wakes with context, and keeps the surfaces around your codebase healthy. No dashboard grid. No reminder loop. Just a maintained orbit.
Stale pull requests, drifted issue metadata, untriaged errors, aging dependencies, and docs that no longer match the code. Each task is small enough to skip. Together, they change the trajectory of a team.
A daemon is a directory with a DAEMON.md file: declarative frontmatter for identity and limits, then operational guidance for the work that happens after a wake.
---
id: pr-helper
purpose: Keeps PRs review-ready.
watch:
- when a pull request is opened
- when a check run changes
routines:
- fix failing checks
- keep the description accurate
deny:
- merge pull requests
- push to protected branches
schedule: "0 9 * * *"
---The file is a control surface, not a prompt. The runtime handles discovery and activation; the role defines intent, routines, policy, and limits.
Watch-driven daemons react to observable events. Schedule-driven daemons wake on a timer. Hybrid roles use both, independently. Switch the pattern to see how the observatory routes a different kind of signal.
An observable event becomes the wake reason.
Every activation is a bounded loop. The daemon receives why it woke, verifies current state, executes finite routines inside its deny rules, and produces a native artifact for the team to inspect.
A pull request opens, a schedule fires, or an alert changes.
The daemon receives the event, role file, and relevant support tree.
It checks what is true now before touching anything.
It acts only inside its purpose, routines, and deny rules.
A commit, comment, issue update, or message lands where the team works.
The maintained system emits the next useful state change.
PR Helper, Project Manager, Bug Triage, Codebase Maintainer, and Librarian are different orbits around the same codebase. Select a role to route its characteristic signal through the network.
Keeps pull requests review-ready without merging or overriding a human.
The watch list answers “when should this role wake?” Routines answer “what should it do?” Deny rules answer “what can it never override?” Keeping those layers separate is how autonomy stays legible and reversible.
“when a PR check changes”
observable event / activation inputUnlike a Unix daemon, cron-only job, fixed-rule bot, or one-off agent, an AI daemon combines persistence, self-initiation, and a role spec interpreted in context. It works in the tools where the work already lives.
END OF TRANSMISSION / NEXT STEP
Read the specification, then give a role a home in the systems your team already maintains.