AI and systems

How I use AI in my work.

I use AI and automation in my own business, Epiphany Dynamics, to organize information, develop software, and manage recurring work. This page explains the tools I use and where human review fits into the process.

01 Process

How AI fits into a project.

I use AI assistants to help organize information, write software, and review changes. Some can also carry out tasks in other tools; those are often called AI agents. I decide what work they can do and what needs my review.

  1. 01

    Start with a clear request.

    I write down what the project needs and the decisions we’ve made.

  2. 02

    Keep useful information together.

    Project notes give me and the assistants the context needed to continue the work.

  3. 03

    Build and check the change.

    Code changes are developed separately from the working version and reviewed before they are accepted.

  4. 04

    Review consequential actions.

    I set approval requirements for actions such as publishing, booking, or spending money.

02 Systems

The tools I use to run the business.

These tools handle different parts of my work. Open Technical details on any row to see how it's built.

  1. 01

    Meeting and activity notes

    Turns meetings, calls, and work activity into written notes I can refer to later.

    Technical details

    Three capture pipelines, one for screen, one for voice, one for chat, feeding a nightly summary job.

    Capture tools

  2. 02

    Shared project notes

    Keeps project context, decisions, and instructions together so the assistants and I can find them.

    Technical details

    Markdown notes on disk, a nightly ingestion job, shared memory files, and a local search index.

    Knowledge vault

  3. 03

    Software build and review

    Organizes code changes and routes them through a second review before they are accepted.

    Technical details

    A dispatch board, one isolated worktree per agent, and a review gate in front of every merge.

    Epiphany Loop

  4. 04

    Day-to-day assistance

    Helps with scheduled tasks, service checks, and daily updates.

    Technical details

    A skill library, jobs on a timer, and a fail-closed install gate that checks every new tool before it runs.

    Hermes

  5. 05

    Rules for automated actions

    Defines what an assistant may read or change and when it must stop for approval.

    Technical details

    Pre-run checks on writes, worktree isolation, routing rules for model tiers, and a plain-language style check on anything a client reads.

    Agent guardrails

  6. 06

    Code maintenance

    Watches the code projects I maintain and separates checking for problems from making changes.

    Technical details

    A read-mostly observer and a separate executor, with a transactional ledger of every merge it makes.

    GitHub Guardian

  7. 07

    Publishing review

    Organizes material for my websites and gives me a preview to approve before publication.

    Technical details

    A topic queue, per-site voice rules, and a preview step that ends in a human click.

    Gravity

  8. 08

    Article preparation

    Helps prepare article drafts, images, and related links for review.

    Technical details

    Keyword research, model-generated drafts and images, automatic internal linking, and a deploy pipeline.

    Mission Control

  9. 09

    Hosting and business services

    Runs services such as booking, document signing, search, and databases that my business uses.

    Technical details

    A Linux server with TLS, dashboards, relays, self-hosted search, a vector store, and managed databases.

    Operations tools

  10. 10

    Connections between tools

    Lets the assistants use information in the business accounts where the work already happens.

    Technical details

    Connections to my workspace and advertising accounts, sign-in handled through a password manager, and scheduled jobs that keep those connections working.

    Workspace integrations

03 Rules

Working rules.

  1. 01

    Give each task a useful result.

    I define where the result should go and how I’ll check it, whether that’s a project note, a draft, or an update in another tool.

  2. 02

    Set permissions before automating.

    An assistant that drafts text needs different permissions from software that can change accounts or make payments.

  3. 03

    Keep the site’s AI connection limited.

    Visitors’ AI apps can read my published information and open meeting times, and they can leave me a short note to review. Booking a call stays with the person, on my booking page.

Say hello.

Tell me what you'd like to build or improve.

Quick navigation

Find a page.

Use the arrow keys to choose a result, Enter to open it, or Escape to close.