The document

Pages that point at things.

Living documents wired to the system they describe — bound to your files, linked to your diagrams, and still true next month.

Written together

A page is edited where it sits, by several people at once, and an agent reads and writes the same page as markdown — no export, no import.

Live co-editing — everyone's changes merge as they type, and someone who opens the page late gets all of it, not a stale copy.
Comments in the margin — readers comment on a passage or pin a region of it, and the thread sits in a rail beside what it is about; threads scrolled out of view gather into a pill that walks you back to them one by one. A guest on an annotate link comments too, under a name they give and with no account, and their comments wait for the team.
One text, several readers — sections tagged by audience drop away when you switch the reader, so the team's copy and the customer's release notes come from one source — and a document leaves as PDF, HTML, an email draft or a Word file.

A page can be bound to a repository file, carrying a source and a revision, so it can be refreshed when that file changes — or written back to it.

Bound to a repo file — the page knows which file it came from and which revision it is at.
Refresh after edits — change the file, refresh the page, and the board catches up.
Write-back — the flow runs the other way too: edit on the board, write to the file, commit.

Deep-link a paragraph to the exact diagram element it explains, so the prose and the picture stop drifting apart.

Paragraph to node — a link lands on the specific element, not on the diagram in general.
Both directions — the diagram links back to the page, so either one is a way in.

The same text serves the board and the documentation, so nobody maintains a second copy that slowly stops matching the first.

Board and repo — one document, reachable from either side.
Markdown — pages are composed as markdown rather than trapped in a proprietary format.