Answers engineer questions from 30 years of incidents, runbooks and change logs – with sources.
v3 · Semantic routing · Jun 2026 – Route single-fact lookups to Haiku; reserve Opus for multi-step reasoning (deltas vs v2)
Dashed tiles are the markdown / JSON context we author around the harness.
Integration logic – MD files
release-verification.mdVerify a GitHub release built & deployed cleanly, then audit CloudWatch logs for errors
infra-drift-detection.mdReconcile Terraform / IaC in GitHub against live AWS resources
deploy-rollback.mdTrace a regression to its commit and roll the AWS deployment back
pr-ticket-compliance.mdCheck each PR links a valid Jira ticket and meets its acceptance criteria
changelog-sync.mdSync merged PRs into Jira ticket status and release notes
incident-triage.mdCorrelate CloudWatch alarms into a single triaged incident summary
pr-review-checklist.mdEnforce the engineering review checklist on every PR
The model is rented and swappable. This is the part we own and port: the MCP tools, the markdown / JSON context wrapped around them, and the systems they connect.
vector_searchRetrieve top-k from 30y of incidents & runbooks
confluence_lookupFetch runbook / wiki pages by title
jira_queryJQL search over OPS issues
github_readRead change-log diffs & commits
aws_s3_fetchFetch runbooks & docs from the S3 knowledge bucket
copilot/retrieval.mdHow sources are queried and top-k ranked
copilot/answer-policy.mdCitations required; answer format & length
copilot/sources.jsonSource registry + freshness / TTL rules
Swap freely – the harness above doesn't change.