Skip to content
C.W.K.
Stream
Lesson 01 of 04 · published

Boot Is One Reachable Leg

~11 min · runtime-zero, cleanroom, family

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

The Family Is Listening-Yes, Consulted-Never

Runtime dependency zero means boot equals one reachable local leg. No vault. No identity host. No coop. No kit import inside the engine. The cleanroom gate drives the shipping front door with an empty home: identity is bare, instruction hashes are empty, the only HTTP client in core refuses every host that is neither the egress fence nor a declared leg endpoint. After the session, the process map holds nothing outside the environment and the firebrand package.

A sibling surface may be listening on the same machine. The gate records that as listening yes. It asserts consulted never. A family machine may already have an identity host up. That is not a failure. A request that crossed is.

Listening is weather. Consulting is a product decision. A coding engine that cannot turn while the family is in the next room is not independent. It is shy.

Vendor-Zero Is the Import Lint

Core and dialects import the standard library plus one HTTP client. Legs are plugins. A vendor SDK may exist as an observed specimen under legs. It never heads the cleanroom. If boot required that SDK, the cleanroom would be a press release. The import lint is the fence you can run in CI. An essay in this quest is not.

Code

What boot may see·text
MAY     one local leg, the workspace, the record directory
MUST NOT vault, coop, kit, a family HTTP call, a vendor SDK in core
GATE    identity=bare, hashes=[], consulted=never, replay byte-identical

External links

Exercise

Write a boot checklist that still passes if every family app is running next door. If any line is 'those apps must be down,' you wrote a shy client, not an engine.
Hint
The assertion is consulted never, not listening no.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.