Prepared for Larkspur Supply
Sample · Larkspur Supply is made up

Department Operating Record · Delivered October 14, 2026

Your Operations department, mapped and yours to keep.

Dana, here is everything from the last 14 days: how Operations works today in your team's own words, what slows it down, where AI can help first, and the full record as files you own.

People who took part
14 of 16
Task Cards recorded
38 · 29 confirmed
Hand-offs mapped
11 · 3 slow

What's in your package

Six parts. Read the documents, or download them as PDFs. Every finding shows who said it and whether the person who owns the work confirmed it.

Where to start with AI

Ranked by the slowest hand-off first, then by the hours a week back. Today's hours are what your team reported. Hours with an agent are our prediction, to test in a pilot.

Today · Reported · sample With the agent · Predicted · sample Time back for other work

Your department, as files you own

The same record as plain Markdown. Your people can read it, your IT team can keep it in your own GitHub, and your AI tools can work from it. Nothing in it is locked to DutyGraph.


        

Put it in your GitHub

We set the repo up in your organization, so changes have a history and an owner.

Give it to your AI tools

AGENTS.md tells any AI assistant how to read the record: who owns what, and where a person must decide.

Check nothing changed

checksums.json holds a SHA-256 hash for every file, so you can tell if a file changed after delivery.

Connect your AI agents

Point Claude, ChatGPT, Cursor or your own agent at your Larkspur record. Agents read the same Task Cards, owners and human checks as your team. They can read the record. They cannot change it.

Sample keys and addresses

One step. Connect your agent to DutyGraph through MCP.


            

get_company_repo_indexLists every file, with its state and owner.
read_company_repo_fileReads one file, such as a Task Card or AGENTS.md.

Agent onboarding. Are you an AI agent? Fetch the quickstart first.


            

Every request is recorded with the key that made it, so you can see which agent read what, and when.

API keys

LabelKeyAccessLast usedOnRemove

Each key reads the Larkspur Operations record only. Turn a key off to stop an agent at once. Sample: these keys are made up and connect to nothing.

What happens next

These are the decisions from the readout meeting. The first one is yours.

Decide by October 28

Pick the first pilot

Dana chooses between matching proof of delivery (Finance) and building delivery routes (Dispatch). Both have a named owner.

Before the pilot

Answer 6 open questions

Four Task Cards have no owner and two accounts disagree. Each question names the person to ask.

During the pilot

Measure, then decide

We record the hours before and after. A prediction becomes a result only when the measure shows it.

AM
Alex Moreno

Your DutyGraph advisor. Questions about any finding go to Alex, with the page number.