The working method behind every LABS property
Shipwright.
How the yard works.
Every property on labs.llc — some sixty of them — is built, verified, versioned and delivered the same way. This page is that way, written down: the method distilled from the session that carried the site through thirty-seven consecutive ships, for anyone (or any agent) who works the yard next.
The name is the covenant: every task, whatever it starts as — a rebuild, a bug, a question about a dot — ends the same way. Packaged, versioned, verified, delivered. Nothing merely discussed; everything shipped.
44tasks in the session of record
37consecutive ships
2sites carried — labs.llc & message.best
0invented data points
The ship cycle
Six stations, no exceptions.
One loop closes every unit of work, from a full property rebuild to a one-pixel fix.
Build
Work happens in a disposable working tree, never in the owner’s folders directly. The tree is rebuilt from the newest shipped archive whenever it is lost — the archives are the source of truth, not the workspace.
Verify
Nothing is claimed until the browser proves it: rendered pages in both editions, computed styles, live filter counts, real fetches. A text search proves the file changed; only the running page proves it works.
Package
Permissions set (644 files, 755 directories — the server refuses anything else), then the whole tree is archived. Full archive in, full archive out; never a loose patch of changed files.
Deliver
The archive lands in the owner’s hands unasked, every single build. Delivery is part of the work, not a favour at the end of it.
Version
The homepage footer carries a visible build number that matches the archive on every ship — anyone can read the live site and know exactly which build is running.
Record
A persistent ledger takes what changed, what was learned, and every trap disarmed — written for the next session, which opens cold and must know everything.
The two-edition system
Paper is the source. Dark is generated.
01
One source, one transform
The paper page is hand-crafted; its dark twin is produced by a mechanical transform — theme flag on the root, dark stylesheet appended, router constants swapped, both edition pills flipped, menu links retargeted dark-to-dark. The twins never drift because one is never edited by hand.
02
One mode, sitewide
A single stored key rules every property: choosing dark anywhere means dark everywhere. Forcing parameters record the choice and carry it across the redirect. Paper is the unconditional default — the operating system’s theme is never consulted.
03
One proven shell
New properties are generated from the same proven page shell — head, nav, menu, sections and footer swapped by configuration. Each property carries its own copies of the chassis (styles, scripts, fonts); assets never reach across a property’s border.
The wiring
A property exists on seven surfaces, or not at all.
Until every surface agrees, the property is not shipped. One data entry drives the first three.
The honesty rules
Everything on a page is real.
- No mock, everNo invented clients, no seeded stories, no fabricated stats, no stock imagery of unverifiable provenance. When mock content is found in a source site, it does not make the trip — and the page may say so out loud.
- Numbers are computedEvery figure on a page is computed from the data it describes, never hand-written. One guide claimed 671 restaurants while quietly serving 315 — the rebuild serves all 671 and derives every number from the file.
- Failures say soWhen a feed or fetch cannot answer, the page says “no answer” — never a spinner pretending, never a fabricated fallback.
- Licenses outrank featuresFree books are linked at their authors’ own editions; non-commercial-licensed files are never mirrored on a commercial site, however convenient hosting them would be.
- Dated claims carry datesResearched market data wears a visible “checked” stamp, and the stamp is refreshed — with the research — on every ship that touches the page.
The lore
Traps already sprung, written down.
Hard-won, verified in the field, and kept so nobody springs them twice.
- The stale stylesheetNew markup against a week-old cached stylesheet is the classic silent breakage — the version stamp on every changed asset is not optional.
- Black on blackAn accent colour must never carry a value that vanishes on its own ground: true ink on paper, near-white on dark — one palette entry, two legible faces.
- The hidden paneA hidden browser tab freezes animation frames and reports zero-height windows; timers that read clocks across a stop-and-restart fire phantom events. Cancel first, reset synchronously, restart after.
- Layers that fightTwo features writing one element’s background erase each other — when layers cannot share, invert the design instead of forcing it.
- Derived durationsRaising one lifetime without raising the ones derived from it can turn a “keep” into a “shorten” — check every duration against its neighbours.
- Sixteen pixelsTouch inputs hold sixteen pixels on coarse pointers or the phone zooms the page; one unwrappable row widens the whole document and every fixed element with it.
- Changing a defaultA changed default re-seats stored preferences exactly once, by flag — then never again. Real choices survive; stale defaults do not.
- RecoveryThe workspace is disposable and has been wiped mid-session without losing a byte: rebuild from the newest delivered archive and continue. Nothing durable ever lives only in a conversation.
The manual