Skip to content
Work

OpsGraph · Ops map · In use

OpsGraph is a local-first, Markdown-native operations map: units, roles, people, tools and step-by-step flows, with the SOP living inside every step. Agents read it through an MCP server, so they know who owns what before they act.

FlowsWeekly episodeNew flowEdit flow
Flow · Production

Weekly episode

One episode a week, from the recording to the report on how it did.

Who is in it
JMHost
AREditor
SKProducer
LTPublisher
DNManager
Every week
1RecordCADR
JMHost
2EditEDDR
AREditor
3ReviewEDDR
SKProducer
4PublishDRCA
LTPublisher
5ReportSHDR
SKProducer
End
A flow, step by step. Each step names who is responsible, the tools and what done means. Demo data.
Type
Ops map
Status
In use
Built with
Markdown · TypeScript · MCP · Convex

How it flows

You decide. Agents do.

Scroll and follow the signal. On the top lane a person makes the call. On the bottom lane the agents do the work.

You
Agents

01 / 05You

Write.

Describe units, roles and flows in plain files.

A person makes this call.

OpsGraph · 01 / 06

In people's heads.

Who does what is never written down.

A company map made of plain files. First the knowledge is loose in people's heads, then people and tools settle into units, a flow is drawn as numbered steps each with an owner, a step opens to show its checklist, an agent looks up the owner of a step before acting, and finally a change to the map appears as a dashed proposal that the owner approves.

Why it exists

How a company actually works lives in people's heads. A new hire has to ask, and an agent has no way to know who owns what.

  • Without it: Processes in people's headsWith it: Every flow written step by step
  • Without it: Documents nobody updatesWith it: The how-to lives inside the step
  • Without it: Agents acting without contextWith it: Agents read the same map as people

What it does

  • Units, roles, people and tools as plain Markdown records

  • Flows written step by step, with the procedure inside each step

  • A validator that reports broken references

  • An MCP server, so agents can read the map

  • A hosted, read-only hub where changes are proposals a person approves

  • A local editor for one team, over the same model

Where the AI sits

Four layers, you on top.

  1. 01

    You

    You own the map and approve every change to it.

  2. 02

    Agents

    Read the map and propose changes.

  3. 03

    Map

    Units, roles, people, tools and flows.

  4. 04

    Files

    Plain text in a folder you own.

Inside the product

People

TeamRolesRequests
SK

Producer

Keeps every episode on schedule and books what it needs.

You own

Episode schedule
Guest and slot booking

You're measured by

Whether each episode goes out on the day it was planned.

You're not responsible for

Cutting the episode
Final say on the cut

Steps this role is in

RReviewWeekly episode · step 3EDDR
RReportWeekly episode · step 5SHDR
ARecordWeekly episode · step 1CADR

Weekly episode

  1. 1RecordJM
  2. 2EditAR
  3. 3ReviewSK
  4. 4PublishLT
  5. 5ReportSK
Roles: what one role owns, how it is measured, what it is not responsible for. Demo data.
ProposalsWeekly episode Waiting for the owner Applied
Proposed change · flows/weekly-episode.md

Add a step, Captions, after Edit

AR Owned by the Editor. The owner decides.

flows/weekly-episode.md
 ## Edit responsible: role/editor tools: [editor, drive]+ ## Captions+ responsible: role/editor+ tools: [editor] ## Review responsible: role/producer

Before

1Record
2Edit
3Review
4Publish
5Report

After

1Record
2Edit
3Captions
4Review
5Publish
6Report
Weekly episode
RecordEditCaptionsReviewPublishReport
The owner approves, then the map changes.Applied. The map now has six steps.DeclineApprove
A change to the map is a proposal. The owner approves it, and then it applies. Demo data.

Check

1 problem All clear

Every reference in the map is followed to the record it names.

Every unit names an ownerPassed
Every flow belongs to a unitPassed
broken-referenceStep ‘Review’ names a role that does not existflows/weekly-episode.md:24 · role/produser
Point it to role/producer
FixedStep ‘Review’ is held by the Producerflows/weekly-episode.md:24 · role/producer
Every step has a responsible rolePassed
Every tool a step uses is listedPassed
Every role is held by a personPassed
Check: broken references are reported, with the line to fix. Demo data.

Your version

Want one built?

Bring the workflow you have today. We will show you what this looks like for your team.

Book a call

Next project

Workflow engine

Self-hosted workflows that connect the tools a production already uses, with scripts kept in version control.