A retired working file: the expressions and words the house used to survey before writing code, posted as an example of the template.
By Bogdan Vladoiu, 2026-11-17
[This is a retired md file we used to grow our repository in a fast and precise way. We used it for frugal ontological surveys to find commonplace symbols and integrations before writing code for a given core package or core component, as well as keeping a lid on made-up names for the same functionality. It no longer reflects exigently the state of the code in our repository. We are posting this as an example, as it was the best template for the purpose. You can, of course, replace this with your own ontology or verbs or lifecycle. But it has to be loaded and enforced for it to work.]
- "Research / survey the pros": before a thing lands, find where current professional practice stands (Material, Apple, WCAG, Elastic for logs) and name what it has that we lack. It informs and does not bind: the outcome may be to change something, drop it, or keep our way and say why. The log find verb came out of exactly this.
- "Sweep the house": before building anything, look for a shape that already exists in the house packages (the companion, the package, a neighbour) and use or extend it. A new thing is the last resort.
- "House tools": capabilities are offered as house apis, tag_action over the registry, with a Docs row, a probe and logged runs; named by spec (tag.discriminator.version). Not shell scripts, Python or outside tooling.
- "House words", the verbs a component answers to; a new verb is a duplication until it is shown not to be one:
install/uninstall: a component installs another, or the runtime installs into one. Overloads carry the carrier:Settings.install(fs),.install(store),install(owner, link),Gun.install(part); a model list installs its sets withList<Body>.install(fs, rows)(and Gun, Hover); a package's own entry is<package>Install(fs)and lists its sets. A main'sinstall(saved)is the one entry a game calls.load/keep: the persisted pair behind install, private to the component;loadis answered at install or by theloadhook, never as a public verb.commit(): the update decoration on a model (Gun,Body,Hover,Settings): fire-and-forget off the ui thread intokeep; a setter without a commit is a draft.proxy(link),hosted,tether,test(): the component over a link, hosted by a daemon, tethered to the exchange, probed live.live,changed,stale(): the hooks a value change fires; a screen is marked stale, never redrawn by hand.- the loops law's
Read,Begin,Enter,Signal,Step,Advance(coreFArenaLoopsover anILoopWorld): the adventure words; a main signals its own verbs, it never keeps a second clock or ledger. Browser { }constructs and pools in the companion;browser("x") { }uses; a usage block never allocates.
- "House rules": CLAUDE.md. The ones that bite most here:
- no new named types without asking;
- defaulted arguments and overloads before new shapes;
- no renames, no comments;
- declarations as data in apis/common;
- every daemon multiplatform;
- the timing ladder.
- "House rigor": things are measured, not asserted (the benchmark files). A ruling is written once, in the package README, with what was rejected and why. Verification is a live probe.
- "Highway style": stateless top-level functions that return functions (keying(), dispatch(), caching(), items(), wire(write, read)).
- The carrier (a Sink, a css builder, a Compose scope) enters by closure capture, never by a type parameter.
- A nuance arrives as a defaulted argument or an overload.
- Assignments can be scrubbed without losing the structure.
- The same declarations feed Compose, the web and Unreal, so a renderer is a re-assignment and not a rewrite.