How it works

Four layers on one model of the company. Pipes bring each record in; the Frame holds them as one live picture; Predictions run that picture forward; Automations act on what it sees, today and ahead.

Underneath is the record of what actually happened: orders in, invoices out, jobs late, a Friday count. The record is the truth, and it belongs to the company.

Pipes Connected, not retyped. The Frame One live model, not twelve tabs. Predictions A forecast, not a guess. Automations Tasks delegated, not done by hand. Billing Accounting Maintenance system Business systems Job travelers Machines and sensors Added-work quotes Inboxes and quotes Stock list Spreadsheets, lists, and logs QuickBooks Accounting Your Frame Inventory Capacity Delivery Cash Quality Equipment Special-order blades 1 on receiving bench: Mon – Wed Order the next blades → Draft purchase order Technician hours booked,next week 104%: Sun – Mon Offer the open slot toa waiting owner → Email draft, forapproval Cases shorted this week 1,168: Mon – Thu Warn the buyer beforethe truck leaves → Email draft, forapproval Works through Microsoft Copilot agents · Google Gemini for Workspace · Slack AI · ChatGPT agents · Grok · anything with an API
Sample — illustrative mock-up

Pipes

Connected, not retyped.

Each number is entered once, where it is entered today, and a pipe carries it into the Frame with its age on it. The systems stay; the Frame never becomes another place to type. Pipes run on our servers, or on the company's own machines with nothing leaving the building.

Harbor Tool & Supply

Your Frame Counter & orders Orders this week Stock &receiving Special-order blades Office & cash Cash in Point of sale 41 Not recordedanywhere Saturday counter demand Receiving log 2 on receiving bench4 days old Bank feed 18400

Sample — illustrative mock-up

Pipes →

The Frame

One live model, not twelve tabs.

Every number in the picture carries one of three states. Current: a recent record backs it. Stale: the record is old enough to doubt. Dark: nobody records it, and the Frame says so instead of showing a zero.

What is pulling on what. A vendor slipping two days shows up as idle hours in one room and a pile in another a week later. The Frame draws the ties between rooms and watches whether the numbers at each end move together.

Why it moved. When a job goes late, the Frame shows which room the delay came out of and whether anyone was measuring it. In the machine-shop sample, three late jobs trace to the one room nobody counts: a chain to check, not a score.

Below, a sample Frame of a tool and supply distributor: eleven things an owner wants to know on a Friday, in the four rooms of the business, with two weeks of its records drawn above them. The company and the numbers are invented; the shape is not.

Sample — illustrative mock-up

Harbor Tool & Supply (sample)

The company and the numbers are invented. The shape is the one we find.

as of March 6, 2026 at 17:00 UTC

4 current 4 stale 3 dark

Counter & ordersStock & receivingPurchasingOffice & cashOrders this weekLate jobsSaturday counterdemandSpecial-orderbladesItems belowreorder pointVendor backordersSupplier leadtimesCash inCash outWillard invoiceFriday numbersrebuilt from
currentstaledark

Two weeks back, one week ahead

Each row is one record. The band pinches when the record changes and widens as it ages. Past today it is the Frame looking ahead, and it stops where it can no longer say.

Feb 20 Feb 27 today · Mar 6 Mar 13 how far ahead it could see 2.2d Orders this week 41 sees 7d Late jobs 3 sees 2d waits on vendor backorders, dark Saturday counter demand DARK dark · never counted Special-order blades 2 on receiving bench sees 2d waits on vendor backorders, dark Vendor backorders DARK dark · twelve inboxes; no single list yet
  • the record changed
  • top row: how far ahead the whole picture could see, day by day
  • your own move, marked so the Frame doesn't read it as a trend
  • already on the calendar, so it doesn't fade
  • Past this line the Frame can't say: Orders is dark.

The week ahead, as the Frame lays it out

Each bar is a job, laid out from how long this kind of work has really taken here. The solid part is as far as the record it waits on can be trusted; past that the end blurs by as much as that record is out of date, and where the Frame can no longer say, the bar is hatched.

todaySatSunMonTueWedThuFriThree late jobs outwaits on late jobs, currentSaturday counterwaits on saturday counter demand, darkContractor blade orderwaits on special-order blades, staleRestock below reorderwaits on items below reorder point, staleBackordered vendor itemswaits on vendor backorders, dark
  • as far as it can be trusted
  • the end blurs by how old the record behind it is
  • past the point the Frame can say

Counter & orders

3 sensors · 2 current · 0 stale · 1 dark

  • Orders this week current
    41 orders

    age 1h

    point-of-sale export

  • Late jobs current
    3 jobs

    age 2h

    job board

  • Saturday counter demand dark
    DARK

    age —

    never counted

    the decision waiting on a number

Stock & receiving

2 sensors · 0 current · 2 stale · 0 dark

  • Special-order blades stale
    2 on receiving bench

    age 3.5d

    receiving log, last entry Tuesday

  • Items below reorder point stale
    17 items

    age 8d

    cycle-count spreadsheet, last count two Fridays ago

Purchasing

2 sensors · 0 current · 0 stale · 2 dark

  • Vendor backorders dark
    DARK

    age —

    twelve inboxes; no single list yet

    the Build candidate

  • Supplier lead times dark
    DARK

    age —

    in the buyer's head

    asked before every big order

Office & cash

4 sensors · 2 current · 2 stale · 0 dark

  • Cash in current
    $18,400

    age 20h

    bank feed

  • Cash out current
    $12,150

    age 20h

    bank feed

  • Willard invoice stale
    $640

    age 38d

    AR aging

    write off or send once more

  • Friday numbers rebuilt from stale
    3 spreadsheets

    age 4d

    office manager, by hand

  • Orders this week feeds → Cash in
  • Late jobs feeds → Special-order blades
  • Vendor backorders feeds → Late jobs
  • Supplier lead times feeds → Items below reorder point

a value nobody measured is null and renders dark, never zero

Read it the way the owner would: the current tiles are the ones the week runs on, each stale tile earns one question, and the dark tiles are the map of what nobody counts, which is where the Build goes.

The first two weeks of a Build end with this page: the week's numbers, what slipped, what needs a decision, what the system already handled. One page, every Friday, from the Frame.

Sample — illustrative mock-up

Harbor Tool & Supply

Friday picture · week of March 6, 2026

This week’s numbers

Orders this week 41
Late jobs 3
Cash in $18,400
Cash out $12,150

What slipped

  • Two special-order blades still sitting on the receiving bench since Tuesday.
  • The Friday numbers were rebuilt from three spreadsheets again.
  • Nobody could say which vendor backorders are holding up the three late jobs.

What needs a decision

  • Hire a Saturday counter person, or cut Saturday hours in April.
  • Write off the $640 Willard invoice or send it one more time.

What the system already handled

  • Purchase orders under $200 now go out without a second signature.
  • Shipping labels print from the order screen instead of being retyped.

Example of the one-page picture. Your numbers, not these.

Predictions

A forecast, not a guess.

The same picture, rolled forward. It leans on the current numbers, discounts the stale ones, and goes dark where nobody counts, so every forecast says how far it can see.

Harbor Tool & Supply

Sample — illustrative mock-up Special-order blades
today the last blade · 1 on receiving bench 2 on receiving bench, counted 4 days ago counted today: Mon – Wed as last counted: Sun – Thu Saturday counter demand: nobody records it, so no forecast
Above, a fresh count puts special-order blades at the last blade between Monday and Wednesday, not between Sunday and Thursday.

On the tape above the rooms, five habits show:

  • Doubt grows with age. The band around a number widens every day nobody updates it.
  • It sees no further than what feeds it. Each row stops where it can no longer say, and names the record it waits on.
  • The company's own moves are marked. A rush order carries a mark, so the Frame does not read its own push as a trend.
  • The calendar does not fade. What is already promised is known ahead.
  • Changes travel between rooms. In the maintenance sample, overdue PMs show up as unplanned stops five days later.

Predictions →

Automations

Tasks delegated, not done by hand.

An AI agent takes a task off the list when its condition is met: on today's number, or on where the forecast lands, days before the date. Each one is suggested first and switched on by choice, works through the assistants already in the office, and logs what it does. AI works around the model, reading a messy export, writing a pipe, doing the task; it is never the source of a number.

Harbor Tool & Supply

Your Frame Special-order blades no update to special-order blades in3 days Ask for a recount → Message to whoever keeps it on the forecast reaches the last blade Order the next blades → Draft purchase order on it reaches the last blade within 2days Tell the owner → Text message off

Sample — illustrative mock-up

Solid: on today's number. Dashed: on the forecast. Each one is a switch.

Automations →

The big-company version

Large companies buy platforms like Palantir Foundry to do this: pull every system into one model of the business, show what is happening, and predict what comes next. Those contracts run to millions a year. A Frame is the same idea, built for a mid-sized company's records and budget.

Where it comes from

Luke first built the model to describe how a mind anticipates what comes next; it turned out to describe a company too. The engine under the Frame is Umwelt, which we built and run ourselves. It ran a real house until August 2026 and runs several projects today, and the same rule has held everywhere: an unmeasured value reads dark, never zero. A company is drawn the way a house is: each part of the business is a room, each record that feeds it is a sensor, and a room with no sensor is dark until someone puts one there.

If you want the mathematics, the Umwelt entry on the Broadcast has all of it. Umwelt on the Broadcast

How a Build starts: the first two weeks

Days 1–3. We sit with the operation and write down what gets asked every week and where the answer actually comes from.

Days 4–7. We wire read-only sources into a record the company owns. Nothing new to type into. Nothing writes back.

Days 8–9. The first Frame comes up, and we walk it tile by tile.

Day 10. The Friday picture and the short list: what to build first. The rest of the Build is the first thing on it.

Questions owners ask

What feeds it? Any system that can export: accounting, point of sale, job tickets, a shared sheet, a mailbox.

Who owns the data? You do. The record is yours and leaves with you. The model that reads it is ours to build and maintain.

What happens when a source stops? That number goes stale, visibly, after a window you set. A stale tile is a question; a dark tile is an admission.

Is there a dashboard? Yes: the Frame is the model, and the dashboard is how you see it. Predictions shows one.

What is it not? A chatbot. An ERP. Another place to type. A replacement for the person who knows the floor.

What do I keep? The Frame, the record under it, the Friday picture, the short list, and whatever we built. If we never speak again, they keep working.

See what yours could look like

Sample Frames, one for each kind of operation we work with, laid out room by room. The companies and numbers are invented; the shapes are the ones we find. See the samples.

What it costs

A $400 consultation, a generous half day, then a written proposal within a week. A Build is typically $10,000–$50,000, quoted toward the low end unless the problem is genuinely hard; a Hold is $1,000–$10,000 a month. Paid in thirds: signing, delivery, acceptance. The whole of it is on the Work page.