ENGINEERING
CEO-driven runbook drift triage and remediation drafts
On demand, an agent compares each service's recent GitHub commit history against its Confluence runbook, reasons about which runbook sections are likely outdated.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator triggers the triage run
- ActionPull recent commits and changed paths from GitHubGitHub
- ActionRead current runbook content from ConfluenceConfluence
- LogicReason about which runbook sections driftedOpenAI
- ActionPost inline suggested edits as Confluence commentsConfluence
- OutputOpen a Linear drift ticket per service for reviewLinear
What it does
Goes beyond date comparison to judge what content actually drifted. An agent reads recent merged changes for each service, reads the current runbook, and reasons about which steps, commands, or topology notes are now wrong. It writes suggested edits as comments on the Confluence page and files a Linear ticket summarizing the drift for the service owner.
When to use it
Use it when a simple timestamp check is too blunt and you want a human-reviewable starting point for the actual rewrite. Best for a quarterly deep clean across a service catalog, or before an on-call handoff to a new team.
How it works
- 1An operator triggers the run, optionally scoping it to a set of services.
- 2The agent pulls recent commit messages and changed paths per service from GitHub.
- 3It reads the matching runbook content from Confluence.
- 4It reasons about which sections the code changes likely invalidated.
- 5It posts inline suggested edits as comments on each runbook page.
- 6It opens a Linear ticket per service with a drift summary and a link to the suggestions for owner sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.