ENGINEERING
Monthly runbook coverage and freshness scorecard
Monthly, inventories all production services from GitHub, matches each to a Confluence runbook.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule starts the inventory
- ActionEnumerate production repos and last-commit dates from GitHubGitHub
- ActionSearch Confluence for a matching runbook per repoConfluence
- LogicClassify each service as missing, stale, or current
- ActionUpsert one scorecard row per service into AirtableAirtable
- OutputPost coverage summary counts to SlackSlack
What it does
Gives leadership a single source of truth for runbook health across the whole service catalog. It lists every production repo, attempts to match each to a Confluence runbook, and records two failure modes: services with no runbook, and services whose runbook predates their most recent commit. Results land in an Airtable scorecard with status, owner, and staleness columns.
When to use it
Run it monthly for an engineering reliability review or a maturity scorecard. Unlike point-in-time Slack pings, the Airtable record gives a trackable trend line of coverage improving (or slipping) over time.
How it works
- 1A monthly schedule kicks off the inventory.
- 2It enumerates production repos and their last-commit dates from GitHub.
- 3For each repo it searches Confluence for a matching runbook page.
- 4A logic step classifies each service as missing, stale, or current.
- 5It upserts one row per service into an Airtable scorecard with status and staleness days.
- 6It posts a summary count of missing and stale runbooks to Slack for the review meeting.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.