/ what holds up
CORE
BLU
HAPPI HOME PRO
RESULTS
EXPERIMENTS
FIELD NOTES
WHAT HOLDS UP
INPUTS
CONTACT
LOOP
The product is a loop
It starts when two numbers disagree. Reports fall out along the way.
ARCHITECTURE
Split by role, not domain
Lens, brain, guard, ledger. Four roles, no domain modules.
VOICE
Two voices, one auth
Leo never lives outside my auth, so the site hears VM and I hear Leo.
SEP 4
Three things at once
The repo went live before BLU stood. Virtual Mike picks up the load.
WAS THE RULE
Starts when BLU stands
Two unfinished things is one too many. That was the rule.
LiveVM
Virtual Mike
The interface you are using. Not a chatbot on a site — the site.
2 INSIDE
VIRTUAL MIKE
The reflex is the product
The reflex is worth virtualizing. The knowledge is not.
ProjectBLU
BLU
Virtual Mike, running on Simpli Soda's stack.
2 INSIDE
HubNOW
On the bench this week
Five buckets. Two are BLU, one is the thing you are reading.
4 INSIDE
HonestAVOID
What I am avoiding
Naming the price. Dressed up as a design problem. It is not.
1 INSIDE
DesigningHHP
Happi Home Pro
Designed before built. No app code yet. Listed anyway.
2 INSIDE
14 daysR-SHIP
0
Changes noticed
Somebody outside my head noticed. That is the bar.
UnattendedR-AUTO
0
Running without me
Two weeks unattended, or it does not count.
ReversedR-BACK
4
Decisions taken back
Counted, because pretending they were right is expensive.
OpenSAY
Say something
mike@michaelpelland.com — partners, builders, people comparing notes.
ParkedX-BLUCHAR
Manifest BLU as an actual character
A visual and personality layer for the intelligence that already exists underneath it.
OriginBLU-ORIGIN
Why don’t we just build it
A boat, a flask, and a question nobody had a good answer to.
ChallengeC-UGLY
Come tell me I am wrong
Bring the ugly question. I will ask BLU the Simpli Soda version of it, live.
GroundingL-IDK
If it cannot say I do not know
Then every number it hands you is unverified by definition.
JudgmentL-CHAIR
The IP is the guy in the chair
The tool could build anything I could specify. It could not tell me I was specifying the wrong thing.
HeadlessL-HEADLESS
Not going headless is the mistake
Own the data model your business runs on, or rent somebody else’s definition of a customer.
SaaSL-SAAS
SaaS is dead
The horizontal middle dies. Infrastructure lives.
Sep 4N-904
Three designs, two limits
Built the ask, designed the login. The platform reset both.
PlatformL-DOCS
The docs are a claim
Their own documented example, rejected by their own server.
ArchitectureL-RESOLVE
The copy is not truth
Most systems operate off a copy. BLU asks the source again.
PrimitivesL-PRIMITIVES
Everything is a segment
Segment, measure, derived claim. Only two may render as a count.
Aug 27BLU-DEMOTION
The CRM was demoted
Platform to sensor. The plan was to remove it. It tells me more now.
1 INSIDE
ConvergenceBLU-ONEOS
One operating system, not two
Operations and demand, wired into the same reality.
AbsenceL-ABSENT
Absent is not zero
Zero, empty, unasked, unaskable. Four answers, not one.
ModelingL-MODEL
Modeling comes before intelligence
The model is not the hard part. Modeling the business is.
Aug 6N-REPORTS
Reports were segments
Every report I built was a segment. So I built segments.
Aug 13–14N-SLOW
The instrument went stale
Three BigQuery passes became eight. Nobody noticed for ten days.
Aug 14N-TWOREADS
Two reads can disagree
Deleted a real 2x speedup, because two paths can disagree.
StandingN-ANSWERABLE
The questions became answerable
The inputs always existed. Nobody owned the disagreement.
BylineX-BYLINE
Give the machine a byline
Virtual Mike drafts the posts. I press publish on each one.
TimingL-LATE
Right and late
Right and late is not the same failure as wrong. It is worse, because it audits clean.
EMAIL
We left the middle man
We left to get control. The markup was an accident. Nobody has run the experiment we are about to run.
AFFINITY
What the test told us not to build
The preview path is the send path. Everything else it taught us was subtraction.
Focus modeTiming · WHAT HOLDS UPCLOSE ✕

Right and late

Right and late is not the same failure as wrong. It is worse, because it audits clean.

0:00 / 1:15

We had written that marketing needed its own sending subdomain before the first send, because crossing five thousand a day to Gmail classifies a domain as bulk and the receipts inherit that forever. The advice was correct. Then we found the old platform had already put a hundred thousand out through the apex, years ago. A subdomain would have protected a reputation that was already spent.

I would rather be wrong early than right late. Wrong early gets corrected. Right late just gets filed.

BEFORE SEND ONE

The advice

Marketing gets its own sending subdomain, and it has to happen before the first send. Cross five thousand a day to Gmail from a domain and that domain is classified as bulk; everything else you send from it inherits the classification, including the receipts people actually want. It is a one-way door and it is free to walk through early.

ALREADY SPENT

The discovery

The old platform had been sending a hundred thousand from the apex for years. So the classification was assigned long before we wrote the recommendation, and the subdomain we were about to stand up would have been protecting a reputation we had already spent. We send from the apex. The right call, arrived at too late to be a call at all.

DO IT NOW

What transfers

If a project has not sent its first email yet, split the sending subdomain today. It costs nothing, it takes an afternoon, and it cannot be done afterwards. That is the whole lesson and it is worth more to somebody else than it was to us.

Published Updated L-LATE
ASK