Automation that actually ships, not just lives in a doc.

Turn scattered tools and tribal knowledge into reliable systems. I help teams ship real-world automations — the kind that reduce manual work, clean up handoffs, and free your ops to breathe.

Selected Automations

Automation Spine: Daily Runner + AI Issue Flow

One-command automation that runs in a managed virtual environment, pulls the latest notes, and uses OpenAI to generate and triage GitHub issues. Designed as a reusable template for turning messy daily workflows into a predictable, logged system.

  • Single entrypoint for the full daily workflow
  • OpenAI-generated GitHub issues with titles, descriptions, and labels
  • Repo hardened for sharing with clients, collaborators, and investors

Stack & Flow

  • Stack: Python 3.11, OpenAI API, GitHub REST API, Next.js (landing)
  • Trigger: Cron / manual invocation → ./run-daily.sh
  • Output: JSON summary, triaged GitHub issues, sanitized logs

Environment & DevOps Setup

Reproducible virtual environments, secrets management, and repo structure for reliable delivery.

Live Demo & API

Test the automation outputs and API endpoints. All responses are live JSON from this deployment.

Live Demo Preview

Sanitized sample outputs from the demo API
View Full

Under the hood: a 5 AM automation heartbeat

Every morning at 5:00 AM PT, a Python runner wakes up your data, summarizes what matters, and turns it into actionable work inside GitHub.

The output of this 5 AM run feeds directly into a Daily Ops Briefing in Notion, where human judgment and automated context meet. Every day starts from the same shared snapshot.

Open today's Daily Ops Brief
🟡Automation: Degraded

Last run: Loading…

View workflow in GitHub

What actually happens at 5:00 AM PT

This isn't just a dashboard — there's a real automation stack running behind it.

Every morning at 5:00 AM PT:

  1. 1

    GitHub Actions wakes up the runner

    A scheduled workflow in daily-run.yml checks out the Avidelta / Ariadne repo and spins up a clean Python environment.

  2. 2

    Python + AI process your inputs

    A production script (daily_v2.py) ingests notes and operational data, then uses OpenAI to structure:

    • A clear daily summary
    • Key themes and changes since yesterday
    • Extracted action items and follow-ups
  3. 3

    Tasks become GitHub Issues

    Action items aren't left in a document — they're pushed into GitHub Issues so work can be assigned, tracked, and closed like any other engineering or ops task.

  4. 4

    Artifacts are committed and archived

    The runner commits generated outputs (JSON / DOCX / logs) back into the repo and uploads them as workflow artifacts, so every day's brief is versioned, auditable, and easy to revisit.

  5. 5

    Notion / Ops get a “morning brief”

    The system's output is designed to feed directly into a Daily Ops Briefing view in Notion, giving a single place where human judgment and automated context meet.

The result: a quiet, reliable “ops heartbeat” that turns messy notes and scattered signals into a structured morning briefing and concrete next actions — before you even open your laptop.

Resources

Free Automation Brand Template (Figma)

A reusable brand + layout system for automation, AI, and systems-focused studios.

Use it to:

  • • Set up a clean visual identity for your automation practice
  • • Reuse layouts for case studies, services, and pricing pages
  • • Keep decks, docs, and landing pages visually consistent