Skip to content

The Retired Name: Kiosk

The doctrine was first captured on 2026-07-22 in a repository named Kiosk. The architecture already pointed toward thin outside surfaces, a capable pair inside, and governed domain operations behind the boundary. The name tried to describe the smallness of the surface.

It described the wrong reason for that smallness.

A kiosk is still a building: small, unstaffed, self-service, and designed for the fact that no capable person is present. It is the absence paradigm reduced in footprint, not replaced.

The doctrine therefore had to defend its own name. It had to explain that the surface was not a little portal, that the person outside was not being left to self-serve, and that a living pair stood behind it. Every use of the word activated the picture the argument was trying to kill.

That was not cosmetic. Vocabulary directs design. A builder starting from a kiosk asks what the little building must contain: its menus, workflows, settings, and fallbacks. A builder starting from a facet asks who stands at this angle and what the whole stone must show them. The first question grows an interior. The second preserves the mass.

The name died on 2026-07-29 when the cut-stone figure arrived. Facet carried the doctrine without a bodyguard:

  • a facet is a face of one mass, not an application in front of it;
  • it has no interior or parallel truth;
  • it is deliberately cut for an angle;
  • it can be recut without damaging the stone; and
  • its thinness implies a complete whole behind it.

The repository was reborn under that language. Nothing migrated merely because it had existed under the earlier name; seams still had to be paid for in Flow and re-expressed here.

Do not choose a metaphor that carries the failure inside it. A name is part of the rails for everyone who reads the doctrine, including models. If the language continually suggests a small standalone application, implementation will keep rebuilding one even when the prose says otherwise.

A name that needs a bodyguard is the wrong name. Explanation cannot permanently outvote the ordinary meaning of the word. Retire it while the cost is only history.

The corpse remains here because deletion is not erasure. The old name should teach once and never become live vocabulary again.