ENGINEERING
Weekly architecture-decision digest from recordings
On a weekly schedule, gathers all of the week's recorded architecture syncs, summarizes the decisions made across them.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList past week's Zoom design-sync recordingsZoom
- ActionSummarize each recording's decisionOpenAI
- LogicAggregate into one table, drop empty calls
- ActionPublish digest page to ConfluenceConfluence
- OutputPost digest link to engineering Slack channelSlack
What it does
Produces a once-a-week digest of every architectural decision the team made on Zoom. Instead of one page per call, it batches the week's recordings into a single Confluence rollup - decision, owner, and meeting link per row - and pings the engineering channel in Slack so leadership reads it without hunting through recordings.
When to use it
Use it when individual ADR pages are too granular for stakeholders who just want a weekly pulse of what changed and why. Good for engineering managers and staff engineers who run a Friday review ritual.
How it works
- 1A weekly schedule fires (e.g. Friday afternoon).
- 2List all Zoom design-sync recordings from the past seven days via the Zoom API.
- 3For each recording, fetch the transcript and have an LLM summarize the decision in one paragraph.
- 4A logic step aggregates the summaries into a single ordered table, dropping calls with no decisions.
- 5Publish the digest page to Confluence and post a link to the engineering Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.