Axioms Studio Studio operations
Studio operations
How Round Online runs day to day — the Three Cycle base, working rhythm, and what stays consistent across launches.
Overview
The operations axioms describe the studio’s working rhythm — what gets done daily, weekly, and monthly; how decisions are recorded; how the studio survives between launches.
The base layer is the Three Cycle — a daily / weekly / monthly cadence that holds across all projects. Additional axioms (review process, scope discipline, when to stop) are being derived.
The Three Cycle
Daily · ATOM. One smallest visible move per day. A function shipped, a paragraph written, a price decided. Never zero.
Weekly · compound. One synthesis activity per week — a long-form post, an audit, a stress test. The week’s ATOMs converge into something readable.
Monthly · milestone. One substantial artefact per month — a feature locked, a system shipped, a release cut. The studio’s pulse is monthly.
Working principles (paraphrased — not yet formally numbered)
- Axioms before architecture. Name the rules before building the system.
- Locked unless versioned. Every system has a version; every change has a changelog.
- Solo studio scale. Decisions optimise for one operator with a long horizon, not a team with a deadline.
- Catalog stays small on purpose. Adding work is easier than removing it.
What this page becomes
Once the system is named and numbered (S1, S2, …), each axiom appears with its statement and derivation. The Three Cycle is already operating and will lock first.
Coming soon — the full system is being formalised.