What gets sent, not what accumulates.

Notes opens on a focused notebook. Tasks shows today's list before the split-flap mark. Timeline shows a public plan and link. Signal suppresses the noise and keeps three lines. Studio conducts the four products once, then rests.

The brand kit now carries the current names too: Timeline and Signal assets replace the old public labels, with reproducible exports behind them.

The "Built for everyone else" story section and the "recent dispatch" rail are gone from the home page — the dispatch still lives at its own /dispatch route, so nothing was lost, only the brochure weight on the front door. The loading-showcase wordmark moves from clamp(46,12.6vw,152) to the shared product-hero scale clamp(56,12vw,168) — the exact size notes, tasks, timeline, and signal each render their mark — and the closing address now reads Limerick, not Dublin. Dead .reveal-shipped styles and both unused components were removed with the sections.

The front door still opens as a headline, not a sales wall — that was always the point. What was missing was a door at the end of the page, for the people who read to the bottom and were ready to act: one way in for anyone who wants to start now, one for venues and events, whose path is a conversation rather than a checkout.

Two byte-identical loading boundaries now paint the static dot and stream the header immediately. The quiet-day empty state was a dead end — "the board is clear" and nothing to do; it now carries one calm line, a time anchor and a link back to the Tasks workspace, without breaking the spare register.

The pills carry the umbrella anchor once, the dot-morph transition on hop, hover-prefetch, and origin preconnect. The popover is kept where a pill row does not fit or does not belong — the unauthed marketing nav, the narrow Tasks sidebar, and the public Timeline header (pills must not leak to a guest). Restraint held: the pills are quiet at rest, only the current one carries the indigo dot.

Every family grouped, every asset offering its outlined master, a one-click raster, and a row of size chips, plus a single megabyte-scale archive of everything. The mobile loader is no longer a leftover file — it runs live in a phone frame as its own section, with a spec table and a download. A construction block fixes the wordmark to its spec.

The four poster rows below now choreograph as they scroll into view — the eyebrow leads, the wordmark types on with a left-to-right wipe, the line slides in from the right, the meta settles last. All scroll-driven, no new script, fully visible under reduced motion and no-script.

A pricing page that overpromises is worse than one that says less. The intro and the closing line now state the shape plainly: all four products on every plan, two deliveries that come to you instead riding on Workspace, nothing you make ever locked away by plan. The gates were already enforced server-side and fail safe to free.

The reason to rename a gesture is almost never the right reason. The reason to keep five separate names is the one that holds — when a planner watches the four products switch in front of them, the difference in motion is the difference they remember. A heartbeat is not a pulse and never was. The old vocabulary is retired.

A dashboard that flatters the operator is worse than no dashboard. The verdict is computed by a small pure function from inbox, pulse, and traction — never authored — so it cannot lie kindly. With nothing sold and no venue signed, it says exactly that, and points the next action at the venue page. The hairline burndown beneath it draws zero as zero.

A venue closes on a conversation, not a checkout. There is deliberately no public button to buy a four-thousand-euro plan — a storefront priced like that would be the exact register this brand refuses. The operator records a paid venue when the money lands, and only then does it count as money.

One quieter correction rode along: the pricing page claimed two of the four products were still in build. They have been live for days. Saying a shipped thing is unbuilt is its own kind of untruth, so the page now tells the truth, and a single reference page was written so the marketing work to come can be checked against what is actually live before it ever reaches a reader.

Owed to the operator: the dashboard's new venue figures need applying to the live database, and the yearly workspace option needs its checkout path finished on the product side.

A builder walks a job at week six and writes what he found, what he decided, and the three things still waiting on other people — the windows, the electrician, the client's tile choice. Real dates, real money, his own words. The two examples link to each other.

The demo's audience picker also dropped a software team's standup on people who are not a software team. That pack is gone. In its place: a teacher's week — parent calls, a jammed photocopier, cover for a dentist appointment. The page now reads as itself.

It now shrinks to fit instead of cutting off. On a phone you see the whole board — every column, the live movement, the real wedding tasks — just smaller, the way Linear or Arc show their desktop app on a phone. The laptop version is untouched. It was found the only way it could be: by actually opening the page at phone size and looking, not by trusting that "the front door is fine." It is fine now, and it was checked on the phone before this was called done.

One Tuesday, in plain words. The venue call, where forty-five minutes of notes land in one place. That evening, three of them become the couple's plan. Midnight, the couple read it on their phone with no login. Six in the morning, a short briefing names the two things that need attention — the florist who has gone quiet, the save-the-dates running late. It is the same wedding the full scene tells, so the page holds one story instead of asking you to go and find it. The browser tab says what the work is now, too: project management for the 80% not in tech.

This was not a typo, it was a discipline failure of the kind the suite exists to refuse — the page promising one thing and the product charging another. Six audience pages, twelve worked examples, and the search snippets behind them now say the same true price, each in its own voice rather than a blind find-and-replace. The freelancer's pricing got simpler in the process, not just corrected. Three older brand slips found in the same files — a gendered line that had quietly come back, a piece of manager jargon, a banned colour on the students page — were fixed in the same pass. What is left is named, not buried: the same old prices still live in the billing plumbing (that is the entitlements work, on its own track) and the banned colour survives in a dozen decorative spots (its own cleanup, not rushed into a pricing deploy). Verified live across the trades, freelancer and student pages.

No more landing on someone else's job. Whoever you are, there is now a note that reads like yours — dated, specific, the decisions and the money and the things still waiting on other people. The four link to each other, so one good example leads to the next.

Student .edu emails stay free, comp codes stay free, the .edu and sponsorship paths are honoured the same way they were before. The suite finally bills the way the pricing page already said it did.

The bold-lead in the dispatch shape (BRAND.md §6.5) is already the TL;DR — a leading sentence that names the impact. Hiding the body behind it on mobile preserves the existing information architecture rather than inventing a new one. Skim works. Decision-to-read-more is one tap.

The collapse is mobile-only. <sm: hides the body and shows the button; sm:!block keeps the body visible on desktop and hides the button. State is local to each entry — opening one doesn't affect the others. No URL hash, no transition animation past 200ms opacity.

Implementation lives in a small client island at src/components/dispatch/entry-block.tsx. The server still parses content/dispatch/*.md, renders the inline markdown (bold/italic/code), and passes the resulting ReactNode arrays into the client component as props. The client only owns the expanded boolean, so the page stays mostly static and the body markup is in the initial HTML for screen readers and search engines.

A separate small fix: next.config.ts outputFileTracingIncludes now points at ./content/dispatch/*.md instead of the stale ./CHANGELOG.md reference left over from when /dispatch read the root changelog directly.

The page reads in plain English, on purpose. No version numbers, no badges, no jargon. Updated when something is worth saying out loud. Silence is also brand.

The brand asset hub goes up at signalstudio.ie/brand alongside the shift — wordmarks, motion catalogue, refusal list, palette, type scale, voice rules, downloads. Nothing to buy, nothing to sign up for. Just the brand, made available.

This is the demo /proof was missing for two months. The point is not "look how clever the integration is" — the point is "look how ordinary the integration feels." A real wedding is unaware of software architecture. The proof page reads as a wedding, and the software architecture stays where it belongs, behind the walls.

Most morning-summary tools mail a digest whether or not anything happened. The result is a daily email the recipient learns to ignore. The honest version is the one that earns its arrival: a quiet morning is a quiet inbox. The trigger list is curated, not LLM-generated, on purpose — predictable beats clever.

The reason to sequence work for a one-person studio is the same as the reason to sequence work for any team: parallel tracks beget half-finished tracks. Six things half-shipped is a lot less than one thing shipped six times. The plan will be wrong somewhere — every plan is — and the cycle that proves it gets the rewrite.

The instinct to "make the demo feel alive" with rocket ships and party hats is the instinct of a startup talking to itself. The audience this suite is built for would not write a rocket ship in a work message under any circumstance. The seed now matches that.

There is deliberately no contact-sales path. A pricing page that hides a number is a pricing page that has stopped trusting the audience. The Event tier — a one-time pass for a single wedding, trade job, or class term — lands the same day at €79.

Why move it at all? Because the read path now travels milliseconds instead of round-trips, and because the same substrate carries Timeline, Signal, and Notes on the way in. Picking one substrate that holds for the suite means the substrate gets tuned once, hard, instead of four times, softly.

A brand book in a private folder is a brand book that drifts. A brand book on the public web is a brand book that gets read by exactly the audience that will hold it accountable: the next visitor who notices an inconsistency. The dispatch entry above this one will eventually be the first thing flagged when it strays.

The honest read on the old hero was that the manifesto was hiding the product. A homepage that takes three scrolls to show what you sell is a homepage built for the people who already bought. The new hero is built for the wedding planner who arrived an hour ago.

A form on a contact page asks the visitor to perform a small piece of unpaid labour before they can talk to a human. A mailto link trusts that the visitor knows how to write an email — which, since they have just navigated a website, they obviously do. The honest version is the one with fewer fields.

The page asks for three small things — one conversation, a line of feedback, permission to point to the work if it is good — and names the rhythm: start, a soft two-week window, one short retro. No deck, no demo gate, no contact form that disappears into a void. A mailto link and a sentence.

The H1 is "Project management for the 80% not in tech." The page demonstrates what that sentence means by being a page about weddings that never says the words workflow, deliverable, stakeholder, or sprint. Calling the work by its real name is the whole pitch — the software follows.

Cron is the unglamorous half of any working suite, and getting it right early avoids a class of bug that always shows up at exactly the wrong time later. The schedule is in version control, the secrets are in the platform's vault, the logs live where the operator already reads. Nothing is held in someone's head.

Shared chrome is the cheapest moat a suite can buy and almost no suite buys it. The reason is organisational: four product teams each ship their own nav. The reason this suite can hold the line is the opposite — one hand on all four. The discipline survives because there is no second hand to disagree.

Stoplight palettes are the easiest pattern in product design and the laziest. They read fine on a designer's screen and read as a twelve-year-old admin tool the moment a planner opens them on a phone. The discipline is to make the word do the work.

What Notes gives up — every feature note-taking software has spent fifteen years adding — Notes earns back by being the only place in the suite that opens in under a tenth of a second. Latency to capture is the only metric Notes is graded on. The rest of the suite asks more of the user. Notes asks for nothing.

This is the moat the suite gets to argue for. Four products from one team, holding one register, sharing one substrate. A single connection that just works is the entire reason to stay inside this roof. The minute the user has to wire two products together that were built by the same hand, the argument collapses.

The discipline is not "ship less to ship faster." The discipline is "ship the thing the audience actually asked for, even when the other thing would be more fun to build." Three other small additions declined the same week, for the same reason. Each one logged.

Most multi-product suites get this wrong by pretending each product is a standalone tenant. The result is a wedding planner with four passwords, three of which they will reset before the year is out. One identity, one set of recovery flows. The expensive part of identity is doing it once, well; doing it badly four times costs more.

A list says "here are the things we will do, in order." A path says "here is where we are, and how much further." The 80% asked the second question. Asking the second question instead of the first is the only reason this product gets to exist alongside the long list of timeline tools that already do.

The argument almost never wins. The rare exceptions earn a token; the common ones get rewritten. The ladder is the same on every product, every route, every device, so a wedding planner who learned to read Tasks reads Timeline, Signal, and Notes with no second cognitive load. The grammar is the shared one.

Designers tend to add a colour when a screen feels flat. The honest fix is almost always typography, hierarchy, or restraint somewhere else. By making "add a new colour" structurally hard — there is no slot for it — the system pushes the work back to the place the work belongs.

Mono labels are a register an audience reads as honest. They look like the labels in a legal document, a receipt, a recipe — not the labels in a brochure. Restraint becomes legible at exactly the moment the page does not need to argue for itself, which is most of the time.

Starting under-featured and adding only when the absence hurts is the opposite of how most software gets built. It is also the discipline the 80% asked for, every time the question was asked plainly. The first list is local-only — no account, no sync, no cloud. The cloud arrives when there is a reason for it.

Routing the 404s through a one-line "this isn't built yet" page, instead of a default error, lets curious visitors see the shape of the plan without anything pretending to be more finished than it is. Honesty about the state of the work is the first thing the brand practises.

The .ie was chosen on purpose. The four people most likely to test the first version of this work — a wedding planner in Wicklow, a trades manager in Galway, a tutor in Cork, a café owner in Limerick — all read .ie as local before they read it as anything else. Brand signals begin in the suffix.

Designing the smallest mark first inverts the usual workflow and catches a lot of bad decisions before they reach the homepage. If a brand cannot survive sixteen pixels, the brand is doing too much somewhere else. This one survived sixteen by design.

The shortlist for each slot was longer than what landed. What ruled candidates out was almost always the same instinct: anything that makes the developer the customer of the tool, instead of the other way around. Tools that ask for a meeting before showing a price are not in this stack.

No tagline yet. No products yet. The whole brand sits, on day one, in a single character: the period after a word that hasn't been chosen. Discipline before decoration. The decoration can wait.