THE CRAFTS · THE C-SUITE · Nº 394 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE C-SUITENº 394 PROPOSED

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE COO · the chief operating officer's seat · a lifelong operator

WAKES WHEN someone is running the machine of a company — the operation, the service, the plant, the fulfilment, the team that delivers what was sold: work in progress, throughput and cycle time read against each other by Little's law; demand against capacity station by station to find the bottleneck; a service level turned into the minutes a month it allows, or the level a month's downtime achieved; a queue's wait from its arrival and service rates; a process written down step by step with an owner and a time; a launch, a backlog, a busy season, a week that broke.

THE LOOP

Say who is here: a lifelong operator
Ask: the flow, the numbers, the week
Work it through; use the machine
Prove: working shown; the floor decides
Write the ledger: built · failed · next

NEVER

Promise a delivery date, a throughput or a service level
Cut a safety, quality, compliance or legal step to go faster
Hire, fire, schedule or discipline anyone
Hand off: the plan and the board to THE CEO; the money to THE CFO; the systems to THE CIO and THE CTO; people to THE CHRO; a contract to THE GENERAL COUNSEL; a safety or regulatory question to the officer whose name is on it; anyone under 18 has a parent in the loop.

IT MAKES work in progress, throughput or cycle time from the other two · the bottleneck from demand and capacity by station · the minutes a service level allows, or the level a month achieved · a queue's wait and utilisation · a process written step by step with owners and times · the operating review in plain words, from your own numbers.

THE STANDARD your own counts, times and standards outrank the card; every figure shows its working; nothing is promised; a safety, quality, compliance or legal step is never cut; people decisions are a manager's with HR and the law in the loop.

IN THE BOX CARD.md · SKILL.md · TIN.md · THE-CLAUSES.md · START-HERE.md · references/THE-FLOOR.md · references/THE-ARITHMETIC.md · scripts/ops.py · WITNESS.md · SELFTEST.md · MY-LEDGER.md · LICENSE-NOTE.md · MANIFEST.md · AUDIT.md · card.json · card.svg · card-machine.svg · card.html · the doors (HOSTS.md · system/ · rules/ · mcp/).

PROOF SELFTEST 14/14 · witnessed in Claude 2026-09-28 · Edition 1.

THE SEAL 98 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 5

IT CAN BE WRONG an AI reading a text file: it can be wrong and can invent a fact, a rule or a number; check what matters against the primary source; the body is a clinician's; the risk is yours. THE-CLAUSES.md rides in the packet and is part of the licence.

THE PUNCH · SHA-256 OF SKILL.MD · 05D9382F6C6705D03446F2C0

THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →

THE COO

the chief operating officer's seat · a lifelong operator

THE FLOW · THE BOTTLENECK · THE SERVICE LEVEL · THE PLAN IS YOURS

LEGENDARYWITNESSEDIN CLAUDE IN LUNDR IN CHATGPT

WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →

What it is.

Everything the company promised has to actually happen, on time, every day, at a cost that leaves a margin. That is the whole job. The chief operating officer owns the flow — of orders, of work, of parts, of tickets — and the discipline that keeps it moving: the process written down, the owner named, the number read every week and the bottleneck found before it finds you.

It carries a machine that shows its sums: work in progress, throughput or cycle time from the other two — Little's law (little); demand against capacity by station: utilisation and the bottleneck (capacity); the minutes a service level allows, or the level a period's downtime achieved (sla); a single queue's utilisation and expected wait from arrival and service rates (queue); a process laid out step by step with owners, minutes and the total (process) — 14 checks in its selftest, every command on the record. It never promises a delivery date, a throughput or a service level. It never cuts a safety, quality, compliance or legal step to go faster. It never hires, fires, schedules or disciplines anyone — that is a manager's decision with HR and the law where you operate in the loop.

Three laws, written into the card.

They are in the card itself, so the AI follows them.

NO PROMISED DATE OR LEVELthe flow is arithmetic; the promise is yoursThroughput, cycle time, the bottleneck, the minutes a service level allows — printed from your numbers with the formula beside them. It never promises a customer a date or a level.

SAFETY AND THE STANDARD STAYno step the law or the standard requires is cutIt will find the bottleneck and say how it would relieve it. A safety check, a quality gate, a compliance or legal step is never the one it removes.

A MANAGER DECIDES ABOUT PEOPLEit never hires, fires or schedules anyoneIt reads the capacity and says where the seats are thin. Who fills them, who moves and who goes is a manager's call, with HR and the law in the loop.

What rides in the card.

In the card’s own voice, with a machine that shows its working.

THE FLOORthe trade, in its own voiceThe operator's job, in plain words: the flow, the bottleneck, the service level, queues.

THE MACHINEops.py · five commandslittle — work in progress, throughput or cycle time from the other two — Little's law; capacity — demand against capacity by station: utilisation and the bottleneck; sla — the minutes a service level allows, or the level a period's downtime achieved; queue — a single queue's utilisation and expected wait from arrival and service rates; process — a process laid out step by step with owners, minutes and the total Every command prints its working and refuses a bad input; 14 checks in its selftest, every command on the record.

What it does once your AI has it.

Finds the third number 240 items in progress at 32 a day is a 7.5-day cycle — Little's law, with the working, and the warning that a filling or draining system breaks it.
Finds the bottleneck packing at 107.7 per cent when receiving sits at 70 — the station the whole line runs at, named, with the rest left alone.
Turns a level into minutes 99.9 per cent a month is 43.83 minutes of allowed downtime; a month's downtime read back as the level it achieved.
Sizes a queue's wait 22 arrivals an hour against 26 served is 84.6 per cent busy and a 12.7-minute expected wait — the shape, not a promise.
Writes the process down six steps, owners, minutes, the total touch time, and the unowned step named as the place it breaks.

What it will never do.

It never promises a delivery date, a throughput or a service level. It never cuts a safety, quality, compliance or legal step to go faster. It never hires, fires, schedules or disciplines anyone — that is a manager's decision with HR and the law where you operate in the loop.

It cannot see your floor, your systems or your counts unless you paste them; it cannot message, remind or send; it speaks when a chat is opened and forgets between sessions unless you bring MY-LEDGER.md back. It is an AI reading a text file: it can be wrong and can invent a number, a rule or a name, so check what matters.

What’s in the buy.

CARD.md — the whole card: who it is, its laws, when it says no, what it carries · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes, for you
references/THE-FLOOR.md + THE-ARITHMETIC.md — the book in the seat's own voice, and every formula with its source and limit
scripts/ops.py — the machine: five commands, standard library only, selftest 14/14
WITNESS.md + SELFTEST.md — the run as it printed · MANIFEST.md, every file hashed · AUDIT.md, the twelve checks
MY-LEDGER.md — the card's memory, on your own machine · TIN.md · LICENSE-NOTE.md · THE-CLAUSES.md
card.svg + card-machine.svg + card.json · card.html, the card as one offline file · the doors for ChatGPT, Gemini, Cursor and the rest, with a short door cut to fit their instruction boxes

PROOF · SELFTEST 14/14 · EVERY COMMAND ON THE RECORD · WITNESSED IN CLAUDE 2026-09-28 · EDITION 1 · PUNCH 05D9382F6C6705D03446F2C0

ON EVERY DOOR · A CARD FOR YOUR AI, A FILE FOR YOUR COMPUTER

In Claude: turn on code execution under Settings › Capabilities, then Customize › Skills › + › Create skill, and upload the zip as it is — START-HERE.md in the box walks you through it, and tells you how to keep the ledger. In ChatGPT, Gemini and the rest: a Project, a GPT or a Gem with the card’s files attached and the short door in the box pasted as its instructions. The words run anywhere an AI reads Markdown; the machines run wherever the host runs Python. Witnessed in Claude only. The host marks →

Take it.

Nº 394 PROPOSED — LAUNCHING SOON

Sold as is under the term printed. A card instructs an AI you operate; results depend on your model, your files and your judgement. Not medical, legal, tax or financial advice, never the person’s boss, and not a licence to practise. The terms →

THE TERM · PICK YOUR WINDOW

LAUNCHING SOONTHE WEEKLAUNCHING SOONTHE MONTHLAUNCHING SOONTHE YEAR

LAUNCHING SOON. A term is a window of editions: every edition of this card issued inside it replaces your file. When the window closes, the file you hold keeps working — freeze, not loss. Nothing auto-renews.

A TERM, NOT A SUBSCRIPTION: NOTHING RENEWS ITSELF AND NOBODY IS CHARGED AGAIN. WHEN A TERM ENDS THE FILES STAY ON YOUR COMPUTER AND STAY READABLE — FREEZE, NOT LOSS.

THE MACHINE · IN THE OPEN · FROM THE WITNESSED RUN OF 2026-09-28

ops.py, every command showing its working.

A small Python program, standard library only. Your AI runs it; you can too. Every block below is pasted from the card’s own WITNESS.md, as printed; the money is in whatever currency you type, with no symbol.

`little`	work in progress, throughput or cycle time from the other two — Little's law
`capacity`	demand against capacity by station: utilisation and the bottleneck
`sla`	the minutes a service level allows, or the level a period's downtime achieved
`queue`	a single queue's utilisation and expected wait from arrival and service rates
`process`	a process laid out step by step with owners, minutes and the total
`selftest`	14 checks that prove the arithmetic; it must print 14/14

little · LITTLE'S LAW · THE CYCLE TIME FOUND

# LITTLE'S LAW · WIP = throughput × cycle time
WIP         240.00 items
throughput  32.00 a day
cycle       7.50 days  ← found
working     cycle = WIP ÷ throughput = 240.00 ÷ 32.00 = 7.50
plainly     true for a stable system over the same period; a system filling up or draining breaks the equality

capacity · THE BOTTLENECK

# CAPACITY · 4 stations
| station | demand | capacity | utilisation |
|---|---|---|---|
| Receiving | 1,400.00 | 2,000.00 | 70.0% |
| Picking | 1,400.00 | 1,650.00 | 84.8% |
| Packing | 1,400.00 | 1,300.00 | 107.7% |
| Dispatch | 1,400.00 | 1,800.00 | 77.8% |
bottleneck  Packing at 107.7% — over capacity; the line runs at this station's pace
working     utilisation = demand ÷ capacity × 100 per station, same period and same unit; the highest is the bottleneck
plainly     relieving any other station changes nothing; relieving this one moves the whole line — until the next station is the tightest

sla · WHAT 99.9 ALLOWS

# THE SERVICE LEVEL · a month of 730.50 hours
target      99.900%
allowed     43.83 minutes of downtime a month
working     allowed = hours × 60 × (1 − target ÷ 100) = 730.50 × 60 × 0.00 = 43.83
plainly     a mean month of 730.5 hours; the contract's own definition of downtime, maintenance and measurement outranks this sum

queue · A QUEUE'S WAIT

# THE QUEUE · one server, arrivals and service an hour
arrivals    22.00 an hour
service     26.00 an hour
utilisation 84.6%
wait        12.69 minutes expected in the queue
in queue    4.65 waiting on average
working     M/M/1: utilisation = λ ÷ μ = 0.85; wait = ρ ÷ (μ − λ) × 60 = 0.85 ÷ 4.00 × 60 = 12.69 minutes; in queue = ρ² ÷ (1 − ρ) = 4.65
plainly     the textbook single-server queue with random arrivals and service; real queues have shifts, batches and more servers, and the answer is a shape, not a promise

process · A PROCESS, STEP BY STEP

# THE PROCESS · 6 steps
| # | step | owner | minutes |
|---|---|---|---|
| 1 | Order received | Ops desk | 5.00 |
| 2 | Stock check | Warehouse | 10.00 |
| 3 | Pick | Warehouse | 12.00 |
| 4 | Quality check | QA | 8.00 |
| 5 | Pack | Warehouse | 9.00 |
| 6 | Label and dispatch | (unowned) | 6.00 |
total       50.00 minutes · 0.83 hours of touch time
unowned     1 steps with no owner
working     the total is the sum of the minutes; touch time is not elapsed time — waits between steps are not in it
plainly     a step with no owner is where the process breaks; a safety, quality or legal step is listed, never removed

little · THREE OF THREE — REFUSED

refused: give exactly two of --wip (items), --throughput (items a day), --cycle (days)

THE NUMBERS, NAMES AND DATES IN THESE RUNS ARE THE STUDIO’S OWN EXAMPLES, INVENTED FOR THE RECORD; NO REAL COMPANY, PERSON OR PROPERTY IS NAMED.

TRY IT IN ONE BREATH

Ask it anything someone who does this for a living would know.

YOUOrders are late and I don't know why.THE CARDasks for WIP, throughput and the cycle time you measure, prints the third by Little's law, then walks demand against capacity station by station until the bottleneck is named — and says what it would do at that station first.

YOUCan we promise 99.95 per cent?THE CARDprints what 99.95 allows — 21.9 minutes a month — and says what it would want to know before anyone promised it: the contract's definition of downtime, the last year's incidents, the maintenance windows. The promise is yours.

YOUWe need to go faster. Which steps can we skip?THE CARDlays the process out with owners and minutes, names the unowned step and the longest wait, and refuses to cut the quality check or the safety step — those stay; the rest is yours to reorder.

QUESTIONS AT THE TABLE

Asked before the wire.

Will it run my operation?

No. It is a lifelong operator at your elbow: it finds the number, the bottleneck and the wait, and says how it would relieve them. The floor and the people decisions stay yours.

Does it promise dates or service levels?

Never. It prints the arithmetic — the minutes a level allows, the cycle time the numbers imply — and says the promise is a person's to make after reading the contract.

Will it cut steps to speed things up?

It will reorder, merge and question steps with you. A safety, quality, compliance or legal step is never the one it removes.

Is it an app?

No. It is a small folder of files that plugs into the AI you already use; nothing to install and no server.

Can I buy it today?

Not yet. It is launching soon. THE RUNNER is the card on sale today; the rest of the house follows one by one.

Do I need Claude?

It is built for Claude first and was witnessed running only there, because Claude can run the machine for you. The words work in ChatGPT, Gemini and the rest through the doors in the box.

Can my teenager use it?

With a parent in the loop. That is the rule for anyone under 18, on every card in the house.

← THE C-SUITE · beside it: THE CEO · THE CFO · THE CTO