Tuturama is run by one person and a set of coding agents, organised the way a small engineering team would be. The unit of work is small, the gates are strict, and the output is measured by what shipped and what got merged, not by what was typed.
Small by design. The size is what lets us sit inside a client's team without becoming a vendor, and ship products without a roadmap committee.
The factory is organised as a set of skills, each one a written role with its own checklist: reviewer, security officer, release engineer, accountant. An agent loads the role, does the work, and hands over to the next. The founder holds the judgement calls.
Nothing ships on the first draft. Code goes through build, tests and a cold review before a pull request. Text goes through three passes and a hostile read. Upstream contributions then meet the hardest gate of all, the maintainers.
Every technical claim is checked against the code, the file, the line, before it is written down. A claim that was not verified does not go out. The rule exists because the alternative was tested and failed in public.
Decisions, corrections and state live in files, not in a chat window. A new session starts with what the last one learned. The company's own bookkeeping runs on the same method.
Client work, products and open source do not share accounts, secrets or repositories. What a client sees never leaks into a product. What we learn in a product never leaks into a client's name.