ENGINEERING
ADR-to-code traceability from review recordings
After a design sync is recorded, drafts the ADR in Confluence and opens a tracking pull request stub in GitHub that references the ADR.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completed for design syncZoom
- ActionTranscribe and extract decision rationaleOpenAI
- ActionPublish ADR draft and capture page URLConfluence
- LogicDerive branch name and PR title from decision
- OutputOpen draft GitHub PR linking the ADRGitHub
What it does
Closes the loop between a decision and its implementation. From a recorded Zoom architecture review it produces a Confluence ADR draft, then opens a GitHub pull request scaffold (branch plus PR body) that cites the ADR URL, so reviewers can trace why a change exists straight back to the meeting where it was decided.
When to use it
Use it when audits or onboarding repeatedly ask "why was this built this way?" and the answer is buried in a call nobody documented. Best for teams enforcing decision-to-code traceability across Confluence and GitHub.
How it works
- 1A Zoom recording-completed event fires for the design sync.
- 2Fetch the transcript and have an LLM extract the decision and its rationale.
- 3Publish a Confluence ADR draft and capture the returned page URL.
- 4A logic step derives a branch name and PR title from the decision summary.
- 5Open a draft GitHub pull request whose body embeds the ADR link, the rationale, and a checklist for the implementing engineer.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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.