# Operators Brief: Issue #005 *May 18, 2026 · The Weekly Drop*

Direction Drop

Write It Once, Ship It in Every Format

Operators rebuild the same information over and over. The capabilities sheet, the sales one-pager, the slide deck for the walk-through, the blurb on the website. Same facts, four formats, four places to update. The day you change your phone number or add a service, three of them go stale because you forgot they existed.

The fix is not more discipline. It is one source of truth that generates the rest. Write the facts once in a plain file. Let a tool render the polished versions. Change a fact in one place and every version updates. That is the whole move, and this week we shipped a tool that does exactly that.

What TNDS is building this week

This week we shipped present-genstack, an internal TNDS tool that turns a single plain README into a browser-ready slide presentation. One command, one self-contained HTML file, keyboard and swipe navigation, brand colors set in a small config file. Pure Python standard library, nothing to install. The point is not the slides. The point is that the README is the only thing we maintain, and the deck falls out of it.

Command Drop

One Source of Truth, Every Format You Need

*Write the facts once. Generate the pretty versions. Stop maintaining four copies of the same thing.*

Brief from one order, not four. In the field you write the operations order once. The squad leader, the platoon sergeant, and the commander all brief from the same document. Nobody rewrites it for each audience, because the second you have two versions you have two versions that disagree. Your business runs the same way. Your project name, what it does, your services, your phone number, your license: those facts live in one place or they drift.

Pick the copy that has to be true. For every piece of information, decide which file is the source of truth. That file is plain text so anything can read it: a person, a slide tool, an AI, your website. Every other version, the deck, the PDF, the one-pager, is generated from that source, not maintained by hand. When a fact changes you change the source and regenerate. You never chase the same change across four files again.

Let tools do the formatting. The reason people keep four copies is that making the pretty version feels like it requires the pretty tool. It does not. A plain README can become a themed slide deck, a PDF, or a web page with a single command and the right generator. The content is yours. The formatting is disposable and repeatable. Keep the content clean and let the tool rebuild the polish every time.

The test. Ask one question of any document in your shop: if a fact in here changes, how many other files do I have to touch. If the answer is more than one, you do not have a source of truth, you have copies that will betray you at the worst time, usually in front of a customer. Fix that and the maintenance disappears.

> BLUE COLLAR AI > > Here is where it compounds. The same plain README that generates your slide deck is also the cleanest possible input for an AI tool. Ask an AI to draft a proposal, summarize your capabilities, or answer a customer question, and it reads that one file straight. You are not writing for a person, then rewriting for a slide, then rewriting for the machine. You write the facts once in plain text and a human, a slide generator, and an AI all read the same source. One file, three jobs.

Field Build

*This one is from our own shop.*

Every time TNDS needed a client-facing presentation, the job was the same grind. Open a slide tool, copy the facts out of the project README, reformat them into slides, set the colors, export. Every time a detail changed, a service, a price, a contact, it had to be fixed in the README and again in the deck, and the two drifted apart within a week. The content already existed in plain text. We were paying the formatting tax over and over.

| Measure | Before | After | |---------|--------|-------| | Time to build a client deck | An hour or more, manual copy and paste | One command, seconds | | Source of truth | Deck and README drift apart | README is the only source, deck regenerates | | Tools required | Paid slide or design app | Python standard library, nothing to install | | Updating a changed fact | Fix it in two or three places | Fix the README, regenerate the deck |

What changed. Built present-genstack, one Python script that parses a README, pulls the title, tagline, features, tech, and contact, and builds a self-contained HTML slide deck. Theme comes from a small config file: gradient, accent color, brand colors. The output runs in any browser with keyboard and swipe navigation. Standard library only, so there is nothing to install and nothing to break when a dependency updates. MIT licensed.

Time invested: About a day of focused work, one file, zero dependencies to wrestle.

Signal Check

*Three beats worth an operator's attention.*

1. The industry is moving to slides as source. Markdown presentation tools like Marp, Slidev, and reveal.js picked up real momentum through 2026 as teams dropped slide software for decks they can version-control and rebuild from one plain text file. The shared idea, slides as source, is the same one behind this week's build: keep the content in plain text, generate the deck. When the whole field converges on a pattern, that is a signal it is the durable move, not a fad.

2. FMCSA rewrote how your safety score is calculated. The overhauled CSA Safety Measurement System, with consolidated violation categories, simplified severity weights, and a twelve-month violation window, moved into full enforcement in early 2026. If you have not looked at your CSA scores under the new math, you may sit in a different risk tier than you think, and that number drives your insurance rates and which shippers will work with you. Pull your scores and read them against the new methodology.

3. Clearinghouse enforcement got teeth. In 2026 the FMCSA Drug and Alcohol Clearinghouse tightened up. States now downgrade CDL privileges for any driver in prohibited status until return-to-duty is complete, and carriers still owe a limited query on every active CDL driver at least once every twelve months. This is a records discipline problem. If your query log and your return-to-duty paperwork are not in one place you can find fast, an audit will find the gap for you.

Tool of the Week

Python Standard Library

The entire present-genstack build runs on Python's standard library. No pip install, no dependency list, no subscription, no framework that breaks when it updates next month. Python already ships with the tools to read a file, parse text, and write HTML. For an operator the lesson is bigger than Python: the tool that has nothing to install and nothing to expire is the tool that will still work in two years. That is the opposite of the shiny AI product that changes its pricing every quarter.

Cheaper on-ramp: Python is free and runs on any machine. If you never touch code, the takeaway still holds: favor tools that are already paid for and already installed over the newest thing with a monthly fee. Boring and durable beats shiny and fragile.

Link: https://www.python.org

Free Drop

The present-genstack Generator

The tool behind this issue. Point it at a plain README and it builds a themed, browser-ready slide deck in one command. Python standard library only, MIT licensed, yours to run and modify. Turn one source of truth into a client-ready presentation without opening a slide tool.

👉 Reply with the word GENSTACK and I will send you the tool and a two-minute setup note.

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

Back to top