SUMMARIZATION

Leadership Reliability Digest from Axiom Logs

Distills the week's Axiom log patterns into a non-technical, trend-aware reliability summary written for executives, and emails it with a single green/yellow/red health rating.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery Friday afternoon
  • ActionPull this week vs last week patternsAxiom
  • LogicCompute deltas, derive health rating
  • ActionWrite executive plain-English summaryOpenAI
  • OutputEmail digest to leadershipGmailGmail

What it does

Produces a reliability digest aimed squarely at leadership rather than engineers. It reads the week's Axiom error patterns, compares them to the prior week to spot trends, strips out all jargon, and frames everything around customer impact and direction of travel. The output is a short email with one headline health rating and three bullets of context.

When to use it

Use it when execs or a board ask for a recurring reliability readout and you don't want an engineer hand-writing it every Friday. It keeps the language business-safe and consistent week to week.

How it works

  1. 1A schedule trigger runs every Friday afternoon.
  2. 2An Axiom action pulls this week's and last week's error pattern counts in one query.
  3. 3A logic step computes week-over-week deltas and derives a green/yellow/red rating from severity and trend.
  4. 4An OpenAI action writes a tight executive summary: the rating, what changed, and what it means for customers — no log syntax.
  5. 5A Gmail output sends the digest to the leadership distribution list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AxiomLog streams, queries, dashboards.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.