Structure

What Structure is

Structure holds your company — who you are, how you talk, how you work, and what you've decided — as a set of plain documents on your own device. On top of those documents it runs AI agents that are steered by them, and it checks what those agents produce against them.

Two halves, and both matter:

  • The canon. Your mission, values, voices, departments, roles, skills, and the record of what you've decided. Ordinary markdown files you can read in any editor. Typed and checked, so the structure can't quietly rot.
  • The runtime. Agents that read the canon before they act, and a review step every change has to pass.

The one rule

Nothing lands in the company without a review — not even your own edits.

Change a canon document and the change does not become part of the company yet. It becomes a proposal: a described, reviewable change with your reason attached. You read it, you approve it, and that is the moment it becomes true of the company. Approving your own proposal is completely fine — that approval is the record.

The rule is the same whether the author was you or an agent. There's no separate lane where the agent's work skips the step yours has to take.

What you get for it

  • A company that reads the same way to every tool you point at it, because the agent-facing files are generated from the canon rather than hand-maintained.
  • A history of why, not just what — every decision arrives with the reason that carried it.
  • Everything on your device, in files you own, that you can take anywhere.

Who it's for

Anyone running a small company or a project who wants the company itself — not just the code — to be something they can direct, review, and hand to an agent. It works solo on one device with nothing else set up.

What is in this tree

A command, structure, and the terminal room it opens with structure tui. The command scaffolds a company, compiles it, checks it, and carries every change through review; structure serve is the runtime underneath. We also build a web cockpit, but it is the lab, not in this tree: nothing in this guide needs it, and a page here that sends you to it is a bug.

Where to go next

  • Install and first run — the command installed and a company standing.
  • Opening a company — the three doors in.
  • The review loop — the one motion you'll repeat.

Under the hood a company is a git repository and a proposal is a branch — Structure never asks you to know that, and this guide only mentions it so you know what you're standing on.