Documentation

Knowledge

Knowledge

Knowledge is documentation, the left-most panel Chat can search. It seeds Ideas and receives write-back after Complete. The walk between those ends is Ideas (ideation until ready) → Work (commitments) → Complete (proof).

Areas

The left rail lists areas this project named. There are no default shelves. Click + Add to name one. Rename the selected area from the header. Removing an area does not delete documents, they move to Unfiled.

Agents cannot mint areas. They may file into an existing area or Unfiled.

Needs a home

Unfiled is the only product-owned pile. Uploads land here until someone files them. Drag a document onto an area, or use Move.

Documentation

The right side lists that area’s documents. The human title is the row. Click anywhere on a row to open it. Upload adds a file to the current area (or Unfiled). Hub Upload accepts files up to 25 MB.

When the library has no documents yet, Documentation is a drop target: Upload a document to seed Knowledge. Drop a file, or use Upload. Develop Add to Knowledge opens Knowledge and that picker.

A connected agent can upload a file too (up to 8 MB). Larger files stay on this Upload button. Markdown notes, “what we now know”, are not files: they land from Complete Add this to documentation, or from the agent as a note, not as an upload.

Extract ideas pulls ideas from a document into Ideas, with a chip back to the source. Remove takes a document out of Knowledge.

After files land in Unfiled and the project still has no named areas, chips suggest names from those files. Confirm creates the areas you picked. Hub never mints an area on its own.

Read

Document text wraps naturally, with headings and nested lists preserved. Referenced specs links exact existing Spec identifiers mentioned in the document to the same full Spec drawer used by Work and Ideas. The document remains the original source; links do not add new stored relationships.

Edit

Text-like docs (markdown, plain text, JSON, YAML) have Edit in the drawer header, next to ✕. PDFs stay read-only, re-upload to replace the file.

Markdown is the document. Write is a markdown editor (headings, B, I, bullets, numbered lists, Insert image). Paste or drop a PNG, JPEG, or WebP, or use the toolbar, Hub stores the image and inserts it as markdown. Click a list tool on an empty line to start an item; Enter starts the next one; Enter on an empty item leaves the list. Preview shows the same rendering as the saved document, switching tabs does not change what you wrote.

JSON, YAML, and plain text edit as raw text so structure stays intact. They do not gain Insert image. A .md file still gets Write / Preview even if the upload landed as plain text.

Save and Cancel (or ⌘↵ / Escape). Nothing autosaves. Leaving with unsaved changes, ✕, Escape, the backdrop, Help, or another drawer, asks Discard or Keep editing. Empty Save is refused. The card title stays the document’s name, a heading in the body does not rename it.

After Complete

When you Accept a spec on Complete, Add this to documentation can record what deployed. Summarize under the Documentation field drafts it from the spec and its finished tickets. It does not pick the area or save, edit the draft, then Add or Update. Skip leaves Accept in place.

That write-back is a markdown note, not a file upload.

QA

QA is an area for interactive test checklists, usually a Tests document named after the Goal, generated when you Accept on Complete. Open one and mark each check Pass, , , or Fail. Clear resets the marks; they last for this open only.

A Fail can become an Idea: Create Idea from bug seeds Ideas with the check name and steps. Retry if that write misses.

Chat

Chat is the dock on the left of every panel, not a box in the top bar. It searches these documents and cites them under Documents. If nothing is uploaded yet, upload a file first. History, ticket rows, and chip permalinks live on Chat.

See also