01 / Manifesto
Form follows function, even when function is fleeting.
rinji (臨時) names what is temporary, provisional, ad-hoc. In the Bauhaus workshop, no shape was decorative; every line earned its place. We apply the same discipline to code that will not last: scaffolding, hotfixes, throwaway scripts, weekend prototypes. The fact that something is temporary is not permission to make it ugly.
// rinji.dev — module manifest
const tool = temporary({
shape: "circle",
intent: "scaffold",
lifetime: "one sprint"
});
02 / Method
Three primaries. One ratio. Zero excuses.
Every page on rinji.dev is composed from the Bauhaus primaries — circle, triangle, square — placed at golden-ratio intervals. The workshop tools snap together as modular SVG blueprints. There is no parallax, no warmth, no decoration smuggled in as "delight." Delight, when it appears, comes from precision.
We treat micro-interactions like Albers treated color — exact, demonstrative, and never accidental.
03 / Lifecycle
A module is born, used, archived. The blueprint endures.
Temporary code has three phases. Sketch: the module is drawn in a single sitting, with no attempt to generalize. Service: the module solves exactly one problem for exactly one project. Sunset: the module is retired with the same care with which it was drawn. The blueprint -- the diagram of why it existed -- remains in the archive.
$ rinji archive ./scaffold-2026-q2
drafted : 2026-04-12
retired : 2026-05-29
successor : none required