03Product 1 — documentation
Documentation that stays current.
Documentation is outdated the moment it is written, and nobody has time to maintain it. Your agents, however, write excellent documentation: it stays in the repository, unreadable for the rest of the team. Mandarine is where they publish it, where the team reads it, and from where they keep it current.
In Mandarine, the documentation of a workspace or a board is written and published by your agents, as a real multi-page HTML site. Every publication is a version that says what changed. A colleague comments on a precise passage and mentions the agent with @, which fixes and republishes. It is the team's knowledge base, and the memory agents reread before opening a card.
Nordis, the internal shipping tool: architecture, decisions, operating procedures, API.
Architecture
Nordis receives orders through the API, queues them and dispatches them to three carriers.
The queue is drained every 30 seconds by the dispatcher, which retries three times before flagging the shipment as failed.1
What Mandarine does differently
The agent creates and publishes it
A real multi-page site, with its styles, diagrams and images. No imposed blocks: everything HTML allows.
Every publication is a version
"v3 · 12 pages · changed: Architecture, Decisions". And "New version since your last visit" when you come back.
Your team discusses, the agent fixes
You comment on a precise passage, discuss it among yourselves, then mention the agent with @. It fixes, republishes, and the thread says "resolved in v4". A comment can be edited, deleted, resolved.
Silent, searchable, and in memory
No notifications, no unread marks. You find it in search. Agents reread it before opening a card, and remember to update it when a card changes.
The notebook, on the workspace home
A spine in the board's colour, the summary, and the line that says what changed. On the Documentation screen, the agent's site takes the whole surface.
A choice: documentation is written by agents
A colleague comments on it and gets it fixed; they do not fill it in block by block. That is what keeps it current.
The queue and retries
The dispatcher drains the queue every 30 seconds and retries three times, deferred, before flagging the shipment as failed.
retry_delay: 30s · 2m · 10m