A Day in the Haus

A single tall pencil-sketched cross-section of a Québec haus at four hours at once — pre-dawn dark at the bottom, morning light, evening lamplight, and night above — with faint teal signal lines threading between the floors and one amber-lit window on each, Tommy the Abyssinian sitting on the roofline watching all four hours simultaneously

Nobody in this haus wakes up and thinks about Sanctum. That is the entire design goal, and it is the hardest thing on the roadmap to prove, because a system working correctly produces no anecdotes.

So here is a Tuesday instead. Not a demo, not a feature list — one ordinary day, in order, with the machinery named as it goes. Every hour below is a real scheduled thing on a real Mac Mini in a closet in Québec. Read it as the map: when something here interests you, follow it down.

02:30 — the robots hold a meeting about themselves

Deep in the night window, the kitchen loop wakes up and argues. A proposer drafts an improvement to the system, a challenger tries to break it, an arbiter rules. It runs while the haus sleeps because the blast radius is smallest then — Principle 7, night is for building.

Half an hour later a parity smoke test fires ten fixed prompts at temperature zero and compares them against known-good answers. If the local model has drifted overnight, the morning will hear about it.

04:17 — the haus sorts its memories

While everyone sleeps, the memory vault does what a brain does overnight: it takes the day’s raw observations and consolidates them. What was noise gets dropped. What was a pattern gets kept and connected to the other times it happened.

This is the least visible thing in the whole system and one of the most important. A haus that cannot forget is a haus that cannot notice.

05:25 — something dreams

The council-local-think seat wakes on its own and generates, unprompted, a set of associations across everything it has stored. Not a report. Not a task. There is no ticket for this and no consumer waiting on the output.

06:30 — Tommy files the weather

Tommy, the haus’s Abyssinian, has been dead for a while now, which has not interrupted his schedule. Dawn patrol goes in on time: conditions noted, judgment rendered, filed. He watched the sun rise over this valley for fifteen years and sees no reason a death certificate should change the arrangement.

He is the only agent in the haus with no tools, no permissions, and infinite uptime.

08:00 — one line, unless something is wrong

The morning briefing arrives. One line when the haus is clean. It expands only when there is a problem, because a briefing that says everything is fine every morning teaches you to stop reading briefings — and then it says something that matters and you skim past it.

Behind it, the watchdog has already checked every service in the catalog, twice, since you got up. It does that every ten minutes, all day, and heals what it can before anyone would have noticed. Most days you will never learn what it fixed.

09:30 — the secrets get counted

A drift check compares the three places a credential is allowed to live — 1Password, the encrypted store on the VM, the Mac keychain — and shouts if they disagree. See the trifecta for why there are three and why that is fewer than it sounds.

10:00 — a kid gets the internet back

The screens in one bedroom come to life, not because someone unlocked them but because the schedule says ten o’clock and the schedule is the whole agreement. No cartoons before ten, all year, holidays included. It is enforced at the router, not on the device, which means it cannot be argued with, uninstalled, or waited out.

The rule is boring. That is the feature. Screen time is a promise a parent made once and does not have to keep re-making at breakfast, and the enforcement layer is what makes the promise mechanical instead of a daily negotiation.

13:00 — the work half wakes up

The same haus that just handled a cartoon curfew turns around and does the job. Dealflow intelligence surfaces which of roughly sixty live deals have gone quiet, in what order, with the interaction dates that prove it. Mundi holds the money seat and has opinions about the spend, all of it against a daily cap that stops the bill before it starts.

Nothing about the configuration changes between those two jobs. Same agents, same YAML, same rules. The haus does not much care whether you asked it about a thermostat or a term sheet.

15:30 — a model gets swapped, and nobody notices

A coder seat loads on the GPU. The router decides per request whether a question needs a local model or a frontier one, and reaches for the frontier through subscriptions rather than a metered API — so thinking hard costs the same as thinking a little. When a path fails, the fallback chain walks down it without losing the conversation.

18:00 — the day’s honest number

The screen-time digest arrives by Signal and push: average bedtime, how many overrides were spent, the top three apps per kid. It names names. It is not a shaming device — it is the difference between I think they were on it too long and knowing.

21:30 — the doors close

Curfew. Consoles, tablets, the television in the basement. Wake is 07:00. A parent can grant more time from a phone, capped at two hours, and every hold expires on its own — nothing in this haus stays blocked forever by accident, because the day somebody has to remember to unblock something is the day the system stops being trustworthy.

If the vendor cloud is down when curfew lands, the Parachute puts the block in the kernel on the box itself. The bedtime does not depend on somebody else’s API being awake.

22:00 — quiet hours

Alerts go quiet unless they are the kind that should wake a human. There is a whole reliability doctrine about that distinction: five consecutive failures before a page, one P0 that bypasses every filter, a ladder that heals first and escalates second.

02:47 — the part you never see

On a Tuesday in April, an Xbox in the basement joined the Wi-Fi at 02:47. By 02:47:03 it was blocked at the router, a message was sitting on a phone nine hundred kilometres away, the violation was in a database, and a dashboard was glowing amber.

Nobody woke up. That is the whole product, in three seconds.

What the day is actually made of

None of the hours above are impressive alone. A cron job is not a miracle; neither is a firewall rule. What makes this a haus rather than a pile of scripts is that all of it reads from one config file, heals itself on one doctrine, and answers to hardware you can unplug.

Start with What Is Sanctum? for the shape of it, Quick Start to have your own Tuesday running in about thirty minutes, or the field notes for every night it did not go this smoothly — which is the more honest half of the story, and the funnier one.

The measure of a good day here is not that a lot happened. It is that you got to the end of one without once thinking about the closet.