folio turns a coding agent into the librarian of a knowledge library that lives inside a project, or on its own.

Every document has one genre, which fixes its job, its voice, its format and its checks. Documents link to each other, and maps give a reader the way in. You talk to your agent; it follows folio's seven skills and runs the gate before every commit.

This documentation is itself a folio library. Every page you read here was written and checked the way yours would be.

folio You ask in plain words Your agent picks a skill It writes linked documents folio check the gate Committed to git fails: fix it and check again folio serve renders the site A reader leaves a comment address skill answers, edits the edit goes through the gate too read it saved beside the page, in git
Follow the arrows from the top left. Nothing reaches git without passing the gate, and a reader's comment comes back in through a skill, so the answer is checked like any other change.
  1. Ask. "Add a concept for the gate", "file this paper", "tidy the maps". The agent picks the skill that covers it: set-up, configure, write, organise, address, run or publish.
  2. Write. The write skill picks the genre, writes in its voice, links the concepts it uses, flags what goes beyond its sources and puts the document on a map.
  3. Check. The gate reads every document: links resolve, maps list what they should, frozen records are unchanged, each genre's checks hold.
  4. Read and answer. The library renders as a site. A comment on a passage is saved in a file beside the page, and the address skill answers it on that page.

New here?

Start with the guide. It installs folio in a project and walks you to your first reviewed page. The cards above are the library's top-level maps: how to use it, its ideas, its specifications, and the record of how it is built.