Ymur Studio · House
These are defaults, not aspirations: what we do first when nobody has said otherwise, and what we check against when something feels off. Each thing the studio makes tailors its own language and style from here. None of them change these.
Your worlds, your songs, your data live where you can take them, in formats you can read without us. The sensitive parts go behind auth. Everything else stays open.
The default invocation of anything we ship does nothing destructive and nothing surprising. The dangerous path is a flag, never the default.
Anything cloud-specific, game-specific or hardware-specific lives behind an interface, so the center stays small and the edges can be replaced. We reach for the boring foundation first and add a layer only when the edge demands it.
When we depend on something we don't control, we keep a plain copy and validate it regardless. Failure is a degraded mode, never data loss.
A claim comes with the thing that backs it: a verdict, a chart, a log, a link. Prose stays understated. Docs are organized by decay rate; a plan becomes a decision, and then it gets deleted.
A word gets one meaning across everything we make. We'd rather borrow an old word with the right weight than coin a vague one, and a reserved word stays reserved.
The target state of anything we run is that it runs itself and a person tends it on a schedule. Stewardship over ownership, for the operator as much as the user.
Automation and models work inside conventions we wrote down, and their output lands as a proposal: a pull request, an issue, a draft, a report for review. A person reads it before it influences anything real.
Notes
Why House is written as defaults, and what gets held to it.