← Back to portfolio

╔═══════════════════════════════════════════════════════════╗ ║ RRJJBB: DECISION MEMO ║ ╚═══════════════════════════════════════════════════════════╝

Memo 05 / 05 · Decision record · 4 min read

RRJJBB: the dream machine

A product from zero, solo, with AI lanes — the night played behind the lock, the card that gives it back, a garment as the key

Goal

Ship a product with no team, no budget line and no permission: a machine people run at night, sold once, that pays for itself — and a garment run of fifty that the same machine sells, so the two engines bind into one brand.

Problem

The category sells subscriptions to noise. Every sleep app is a library of loops, a score in the morning and a monthly charge; every sportswear label is a logo on a blank. Neither gives anything back that the person did not already own, and both watch the customer to do it.

The opening: one instrument, not a library. A night with a number, printed on a card in the morning, that says what the machine did and nothing about the sleeper — and a serial grammar that lets a garment open a night and a night become a garment.

Customer Promise

"A machine you run at night that gives the night back in the morning — and never says a word about you."

Stakeholders

The sleeper needs sound that holds behind a locked phone all night, and a morning that reads true.
The brand needs a share that carries a number, so a night travels without a campaign.
The lanes — one for making, one for shipping, one for the mail, one for the registry — need every decision in writing, so a solo founder can run four hands without holding them.

Integration was the job again: three surfaces, two engines, four lanes, one registry of rulings.

Constraints

Refusals, as product: no account, no subscription, no ads, no telemetry. Every feature had to work with nothing leaving the phone.
Platform: a web page cannot play sound behind an iOS lock. The one thing the paid app does that the free page cannot had to be native, and everything else had to stay one page.
Budget: a monthly ceiling on build minutes, set by hand, with every run a decision.
Voice: nothing explains itself. Every key gives back or is not on the face.

Options Considered

Option A: the web page alone, free for ever. Honest, and silent the moment the phone locks.
Option B: a native shell around the live page, with a native engine that plays the same night behind the lock. One page, two engines held to one score.
Option C: a full native rewrite. Two products drifting from each other by the second week.

Decision

Option B. The page is the fascia and the logbook; the engine is native and plays behind the lock; the shell tells and never decides. A conformance check compiles the arithmetic on every push and holds the engine to the page's own score, sample for sample — so the two engines cannot become two machines.

The Mechanism

Two loops, one card. The night's loop turns in days once the store link is live; the garment's loop turns in months. The four places anything is counted are the brand's handle, the store, and the ledger — nothing on the phone is counted, by design.

Evidence

Renders of the real surfaces, taken by the machine's own scripts — nothing mocked, nothing drawn twice.

The lock screen of an iPhone while a night runs: the mark in a dark square, RRJJBB · NIGHT and the serial, play and pause answering the engine. — The lock screen, fed by the native engine. The one thing the paid app does that the free page cannot.

The receipt of a night: SLEEP, 100 minutes, the readings in a rail, the night's line falling to its floor with a mark, LIGHT 0.84, the address rrjjbb.com/#0344. — The card the machine prints in the morning. What it did, where the breath went, when the floor came. Never who you are.

A back panel on black cloth: one bone line falling to a single ember mark, the number 0344 in a serif at the foot. — The night as cloth: a night's line rendered as a print-ready back panel at the patch's ruled size, one ember on the floor. The far loop's first tool.

Metrics

Done, defined in writing: a live store link; net proceeds past the developer program's own fee; a night shared by someone who is not the founder; the run of fifty sold through.
Guardrails, measured on every push: ninety-odd gates across three surfaces; a compile proof and a conformance check on every native change; a brand gate that refuses any ink the one palette file lacks.
Strategic: a serial grammar no competitor in either category can copy — a garment's lot accrues nights, and a drop's back is cut from one.

Risks & Mitigations

Two clocks behind a lock → the engine's own sample clock is the night's clock; the page reads it on waking. A night on a real phone is the proof, and it is written into the launch list before submit.
Queues nobody controls (review, the agreement, the entitlement) → nothing waits on them; an icebox is what a lane pulls while it waits.
A microphone in a bedroom → a meter, never a recorder; hidden until it gave something back; on by one hand, with the system's own indicator, and its sentence read by the founder before it ships.
Runaway build spend → a ceiling by hand, a stop switch, and a build per batch on a written test.

What Changed

A method: crucible, then a ruling as multiple choice, then a build, then a gate — every one of them in a registry a reader can audit.
One person running four lanes, each with a written charter, none holding a hand.
A product that ships its refusals as its pitch, and a card that turns a night into an object worth handing over.

Where It Stands

The web instrument is live at rrjjbb.com. The app is on its tenth test build, with the native engine behind the lock, the card giving the night back, and the garment's address opening the app. Submission follows the first night that is not the founder's.