# Operators Brief: Issue #004 *May 11, 2026 · The Weekly Drop*

Direction Drop

Know Your Gear Before You Build the Plan

Every operation runs on files. The SOP, the driver qualification checklist, the pricing sheet, the onboarding packet, the contract. Most shops have no rule for where a file goes, so the same document ends up living in three places, nobody knows which copy is real, and the answer to "where is the SOP" turns into a twenty minute search through email, a shared drive, and somebody's laptop.

This week is about the fix. Not a fancy tool. A field manual. When you know what every document, file, and folder is, what job it does, and where it goes, the search disappears. The rule that makes it stick is simple: if you cannot say where a file goes in five seconds, your structure is wrong, not the file.

What TNDS is building this week

On the build side this week: northbound-ai, our single-tenant DOT and FMCSA compliance answer engine for a fuel-hauler pilot, went deeper into citation grounding. Every answer it gives points back to the exact 49 CFR section it came from. No invented rules. Same principle as the teaching piece below. If you cannot cite where the answer lives, you do not trust the answer.

Command Drop

The Five-Second Rule for Where a File Goes

*Three buckets, one rule, and the end of the twenty minute file hunt.*

Start with the field manual, not the folder tree. A battalion field manual does not tell you how to win the fight. It tells you what every piece of gear is, what it is called, what job it does, and how the pieces fit together, so you can build the plan yourself. Your files are your gear. Before you reorganize anything, you name the gear. Everything else follows from that.

Three buckets, plain English. Every file in your operation drops into one of three buckets. Knowledge is the written stuff people read: how we win (the playbook), how we do a task the same way every time (the SOP), and what somebody reads while they are actually running the job (the runbook). System is the thing that runs: the sheets, the apps, the wiring that does the work. Execution is the doing it right now: the live checklist, the deploy, the run in progress.

The order is the point. Knowledge feeds System feeds Execution. Doctrine, then the unit and its equipment, then the operation happening in real time. If a file, a folder, or a piece of paper does not fit one of those three slots, it is almost always a duplicate or it is clutter. That is your first cut.

Now the five-second rule. Pick up any file and ask: is this something a person reads, is this the tool that runs, or is this a step being executed right now. If you can answer in five seconds, the file has a home. If you cannot, the structure is broken and you fix the structure, not the file. Run that test across your whole operation once and you will find the three copies, the dead-end folders nested five levels deep, and the SOP nobody can locate.

> BLUE COLLAR AI > > Here is the part that pays off later. Write your SOPs and playbooks in plain markdown or plain text, not locked inside a PDF or a proprietary app. Markdown is just text with light formatting. A person reads it fine, and when you bring in an AI tool to answer questions or draft the next document, it reads your files straight with no conversion step. The rule: if a human or a machine needs to read it, write it in markdown. If a machine needs to parse it as data, use JSON. Do that now and your future AI project starts on day one instead of after a month of cleanup.

Field Build

*This one is from our own shop.*

TNDS had its DevOps and AI reference files scattered across several folders and a few different sources. The same file lived in three places. There was no single source of truth, so finding the current version meant opening every copy and guessing which one was newest. Onboarding a new operator into the repo meant asking Jacob and waiting.

| Measure | Before | After | |---------|--------|-------| | Source of truth | Three copies in three folders, newest unknown | One canonical file, everything else compared to it | | Time to find the right doc | Ten minutes or more, open every copy | Under five seconds, five-second rule | | Folder depth | Nested five levels deep, dead ends | Capped at three levels | | New operator onboarding | Ask Jacob, wait for an answer | Read the index, self-serve |

What changed. Built one canonical field manual that names every document type, file type, and folder. Consolidated to one DevOps folder and one AI folder. Picked the canonical version of every duplicate, deleted the rest, and left a pointer where the old copy used to be. Capped nesting at three levels.

Time invested: About one working day.

Signal Check

*Three beats worth an operator's attention.*

1. The industry standardized on plain markdown for AI instructions. AGENTS.md, a plain text file you drop at the root of a project to tell an AI coding tool how to work, was handed to the Linux Foundation's Agentic AI Foundation in December 2025 and is now read by most major AI coding tools. Translation for operators: the whole industry just agreed that the way to talk to a machine is a plain markdown file a human can also read. Exactly the move in this issue.

2. FMCSA is retiring the paper medical card. Under National Registry II, medical examiners now upload DOT physical results electronically and the driver's motor vehicle record becomes the proof of medical certification. For carriers that means you verify medical status through the MVR, not a card in a glovebox. If you run driver qualification files, your records process has to match the new reality or you build audit risk into your own filing cabinet.

3. Registration modernization is a records trap. FMCSA's MOTUS overhaul keeps rolling through 2026, and MC numbers are gone with the USDOT number as the sole federal identifier since October 2025. System transitions are where administrative failures live: missed renewals, profile mismatches, incomplete submissions. The defense is boring and it is this issue's whole point. Keep your registration confirmations archived in one consistent folder system so a system change never turns into a violation.

Tool of the Week

Claude Code

Claude Code runs inside VS Code and reads your whole project, docs folder included. The reason it belongs in this issue: it works far better when your files are structured and your docs are in markdown. Point it at a clean repo with a plain-language docs folder and it understands the operation. Point it at a pile of PDFs in random folders and it struggles the same way a new hire would. It reads a CLAUDE.md file at the root, which is the same idea as the AGENTS.md standard above: one plain file telling the tool how your shop works.

Cheaper on-ramp: Not ready to pay for an AI coding tool. Start free: keep your SOPs and references in plain markdown files in one clean folder. That single habit is what makes every AI tool you adopt later actually useful. The structure is the moat, not the software.

Link: https://www.anthropic.com/claude-code

Free Drop

The DevOps and AI Wrapper Field Manual

The full cheatsheet behind this issue. Every document type, every file type, every folder, and the five-second rule for where each one goes. Written as a field manual, not a lecture. Military framing first, then the exact technical terms so you can hold your own on any call.

👉 Reply with the word FIELDMANUAL and I will send it to you.

True North Data Strategies Jacob Johnston | 719-204-6365 | jacob@truenorthstrategyops.com Subscribe: [opt-in link] Unsubscribe: [unsubscribe link]

Back to top