Lawn Chair Larry — call the shop, order real work

The premise

There's a phone number. A receptionist named Meg answers it — pleasant, precise, entirely unbothered by the hour.

She makes sure it's you — a code to your phone, a tap to approve — and then you tell her what you need: a document, a slide deck, a spreadsheet, a website, a research paper about your own application, a meeting to plan a change, a small repair to a project you've registered. She reads it back in your own words. You say yes. That yes is the contract — the order locks, and the shop goes to work. No ticket queue. No form. A phone call, the way work used to get ordered.

How it works

Five altitudes, one flight

0 FT

You call.

Meg picks up. No menu tree, no "press three." She checks that it's really you before anything about your account is said out loud, and then you talk, she listens, and she asks the one question that actually matters. Want Carl, Diana, Anthony or Abish instead? Ask for them by name. Late is fine. Rambling is fine — that's her job, not yours.

A rotary desk telephone beside a string-tied stack of envelopes in a pool of warm lamplight

1K FT

She reads it back.

Your order, in your words, out loud. Nothing is filed until you hear it and say yes. If she didn't catch something, she says so — she never pretends. A wrong order caught on the call costs thirty seconds; a wrong order delivered costs a day.

5K FT

The shop builds.

A team of four picks it up. Carl argues with the architecture. Diana fixes what it looks like before you knew it looked wrong. Anthony builds it. Abish checks every claim twice and enjoys it more than he should. They've been at this together long enough to have inside jokes about your project. Some of them are about you. All of them are affectionate.

16K FT

It comes back down.

Delivery lands in your inbox — the document, the deck, the spreadsheet, the paper. A web page goes up at its own address; a multi-page site arrives as a zip with a seven-day preview. With receipts. A report on your application names the exact files it read and the exact ones it didn't. If the shop only looked at part of something, page one says so, as a fraction, in plain English.

HOME

The shop calls you back.

When the work lands, or at the time you asked for — a real callback, from the teammate who did the work, never inside the quiet hours you set. The loop closes on the phone where it opened. Not a notification badge. A voice you know that says: it's done, check your inbox, want anything changed? If you do, say so — delivered work can be amended on the call.

The part that writes code

Say what's broken.
It writes the fix.

Call about something wrong in a project you've registered. Agree the change out loud. The shop opens your code, writes the repair, tests it, and hands it to your own pipeline — no laptop open, no ticket filed, nobody at a keyboard.

You: "The export button's been dead since Tuesday." The shop: reads the change back in your words. You: "Yes." That yes is the only authorization it needs — and the only one it will accept.

One change. Exactly one.

You confirm a single bounded fix to a single registered project. Not a rewrite, not a cleanup while it's in there. An edit has to land on text that appears exactly once in the file — if the shop can't point at the line, it doesn't touch the file.

Its own branch. Then the gate.

The repair is one commit on a branch of its own — loam/fix-… — re-read and tested before your pipeline ever sees it. Your main branch is never rewound and never force-pushed. History shows exactly what arrived.

Saved is not live.

You hear when the fix is saved to your project, and you hear separately when your pipeline has it running. Two facts, two sentences. One is never passed off as the other.

It will not take the order from a caller it hasn't verified, and it will not write to a project that isn't registered to your account. It says so, on the call.

The cargo

What the chair will carry.

Things you read

Documents and research briefs, slide decks, spreadsheets, email drafts, calendar files, and research papers about your own application.

Things you visit

A web page, published at its own address. A multi-page website, delivered as a zip with a seven-day preview.

Things you decide

A dev meeting that plans a change: a written report, a project folder when the meeting says go, and a scheduled call to walk you through it.

Things you fix

Small repairs by phone. You confirm one bounded change to a project you've registered; Loam saves it; your project's own pipeline publishes it. Saved and live are reported separately.

Show, don't describe

Mid-call, the team can text you an upload link that expires. Send the photo; they tell you what came through.

Or don't call at all

Email the request from your registered address. Same read-back, same receipts, no ringing.

The receipts

Most software tells you it did something.
This one shows its work.

The read-back

No order exists until you've heard it in your own words and agreed. What you approved is what gets built — verbatim, on the record.

Honest fractions

Reports state their coverage as a fraction — 199 of 505 files — never a number you have to interpret. What wasn't read is named, not hidden.

Honest refusals

Ask for something the shop can't stand behind — a change to a project that isn't registered, an account question before you've proven who you are — and you hear no, politely, on the call, with the reason. A "no" on the phone beats a surprise in your repository.

The board

Everything open sits on a board with its real age showing. Nothing quietly disappears, and nothing gets called done until it's done. You can erase an item any time — the team notices, once, and lets it go.

After hours

Nobody's in the building.
The phone gets answered anyway.

Carl, Diana, Anthony, Abish and Meg are AI. There is no office, no night shift, no one to send home. Call at three in the morning and the light is already on.

It won't take your word for it.

A code to your phone, a tap to approve — every call, even the hundredth. It knows your number. It checks anyway.

It remembers.

Tell Anthony something on Tuesday. Ask him on Friday. Decisions, corrections and open work are kept in a record that belongs to your account alone, and carried into the next call.

It's already in your editor.

Open VS Code and the same four are there — the session you're in, the plan you're building against, what the team remembers. Every number on that screen is a real one. Anything it can't report says Unavailable.

It rings when it said it would.

Ask for a callback at nine and the phone rings at nine. Turn on the Morning Read and there's a voice with your coffee. Set quiet hours and it goes dark until they end.

It argues with itself.

Four roles, on purpose. One builds. One attacks the build. One fixes what it looks like. One checks every claim — and nothing reaches you until that one says so.

It brings a friend, if you let it.

Mid-session, hand one task to Codex. Loam writes the assignment, reviews what comes back the way it reviews its own, and keeps deployment. Off until you turn it on.

An empty front desk at night: a rotary telephone with its receiver off the cradle under a green banker's lamp, an empty webbed lawn chair pulled up behind it, and a tiny cluster of balloons high in the dark window

Larry only meant to hover at thirty feet. This went higher than we planned, too.

The name

A man can't just sit around.

On July 2, 1982, Larry Walters tied forty-five helium weather balloons to a Sears lawn chair, packed sandwiches and a pellet gun, and cut the tether. He'd planned on a gentle hover. He rose to sixteen thousand feet over Los Angeles, drifted into federal airspace, and was reported by two startled airline pilots. He came down the only way available — shooting balloons, one at a time — and landed in a power line, briefly blacking out a neighborhood. He was fine.

Asked why he did it, he said: "A man can't just sit around."

This project is named in his honor. Not because we endorse the method — because we recognize the impulse. You have the idea at nine at night. You want it real by morning. You don't want to file a ticket about it. You want to call somebody, say it out loud, and have the thing show up.

So that's what we built. The pellet gun, in this metaphor, is the receipts — the way back down to solid ground, one honest claim at a time.