Knowledge base

Krrim's docs sit in the same workspace as the tasks. That is the entire point: the reason team wikis rot is that they are somewhere else, and updating them is a second job.

Writing

Rich text with the things you actually need:

• Headings, lists and tables
• Checklists you can tick off in place
• Code blocks with syntax highlighting
• Images, pasted or dragged in
• @mentions of people, which notify them
• Task references — paste a task key and it becomes a live link showing the task's current title and status

That last one is what keeps a doc honest. A link that renders "krrim-0042 — Investigate checkout timeout · Done" does not go stale the way a copied title does.

Where docs live

Docs belong to a project and inherit its permissions. Someone who cannot see the project cannot see its docs, and there is no separate sharing model to keep in sync with the first one.

Collaboration

Several people can edit the same doc at once, and you see who else is in it. Comments attach to the doc the way they attach to a task.

Attachments

Files attach to docs and tasks alike. They are stored per workspace, and a link to one enforces the same permission check as the thing it is attached to — so a URL that escapes into an email is still useless to somebody outside the project.

What it is good for

The things that are true for more than one task:

• How to run a release
• The decision record for why you chose the thing you chose
• Onboarding notes for whoever joins next
• Meeting notes that reference the tasks they produced

If it is about one task, put it in that task's description or a comment. A doc per task is how you end up with two places to look.