ScribeOS PressHouse Sheet · 01

First edition · Autumn 2026

The House Sheet

Point it at a real repository. Get back a book that has to survive the tree.

ScribeOS is a small, opinionated AgentOS for technical books. It turns a codebase — or a finished manuscript — into print-quality output. Two faces. One promise. The book must survive contact with the tree.

Article I

The problem

Software teams ship code faster than they ship understanding. READMEs rot. Confluence pages lie. Onboarding is “read the code and ask Slack.” The people who could write a real field guide are busy shipping. AI made that worse before it made it better: fluent prose about files that don’t exist.

Article II

Two faces

Book Mode

Point ScribeOS at a public repository. It walks the tree, plans a dual-voice field guide, and cites only paths that exist. If the file is missing, the chapter is missing.

Manuscript Mode

You already wrote it. The house lays it out: jackets, 6-by-9 type, print layout — without rewriting your words. BOTTLENECK Issue 01 was bound this way.

Article III

The promise

Non-negotiable: the book must survive contact with the tree. ScribeOS would rather fail than invent a file. Citations, fences, and structure are checked against what is actually on disk. Stubborn honesty about other people’s code — not a tour of the writer. That is the brand. Everything else is machinery.

Article IV

Two voices

Senior-engineer technical prose, plus additive “in plain words” callouts. The plain layer is not a dumbed-down rewrite. It sits beside the technical pass. A field guide a new hire can hand to someone who does not live in the repo.

Article V

What this house is not

Typical AI docsScribeOS
Sounds rightHas to be right against the tree
One voice (marketing)Two voices (technical + plain)
Chat transcriptA book — cover, chapters, formats
Hides the pipelineKeeps the harness honest
  • Not inventing paths, APIs, or modules to fill a chapter.
  • Not replacing the technical pass with a simplified rewrite.
  • Not a storefront that happens to typeset. Selling is optional.
  • Not a second language on top of the tree.

Article VI

The till, if you want it

When a title is ready, you may list it. You keep 90%. The house keeps 10%. You may also keep the PDF private. The bound file is the product either way.

Article VII

The closer

Documentation debt isn’t a writing problem. It’s a trust problem. ScribeOS doesn’t ask your team to become publishers. It asks your repository to sit still — and returns a book you can hand a new hire, a customer, or a future you who forgot why the system looks like that.

Author once from the tree. Review the proof. Ship the book.

Book a repository · Open the studio · Return to the press

ScribeOS

Would rather fail than invent a file.

Set in Fraunces and Figtree. Bound as a sheet, not a brochure.