Delivery module
Knowledge Base
Client and project background, written down next to the work.
Why you need it
Project background lives in one person's head or a buried chat thread. When someone new joins or a lead moves on, the team starts from scratch.
What you get
- New joiners get real project context, not tribal knowledge.
- Requirements and background are written once, per client and project.
See it in action
What you can do with Knowledge Base
Requirements, features and background, written in markdown and attached to the client and project they describe.
RequirementsFeaturesBackground
raven / knowledge — Atlas · overview.md
RequirementsFeaturesBackground
# Client · Atlas Financial
- SLA: 99.9% · Lead: R. Shah
- SLA: 99.9% · Lead: R. Shah
Connects to
Runs entirely inside Raven.
Access levelsViewer — reads reports and recordsMember — does the day-to-day workAdmin — sets up the moduleHow roles work