You can always answer how something got here
Approving a change is a decision, and a decision needs evidence. You see what a change does to everything around it before you say yes, and afterwards you can reconstruct exactly how the record came to look the way it does.
- Link Impact
- History
- Audit Log
If proposal #52 is published
- 31links stay resolved
- 6new links created
- 4documents orphaned
- 2links would break
Shown before approval, not discovered three weeks later.
Link Impact
See exactly what a change will affect before it happens.
Before a proposal is approved, Link Impact shows what it will do to the rest of your knowledge base: which links it creates, which it breaks, and which documents would be left connected to nothing.
This is the part no code review tool can do for you, because in a knowledge base the connections are the substance. A text diff cannot tell you that publishing this quietly orphans four documents.
History
Every document keeps a full record of how it changed over time.
Every document keeps its full history. Look at how something read last month, see exactly what changed and who changed it, and roll back to an earlier version when something needs undoing.
Nothing is ever one wrong click from being gone, which is what makes people willing to edit in the first place.
Hybrid ranking.md
Ines Caetano rewrote the tuning section
2d ago
Dmitri Volkov added the benchmark table
3w ago
Priya Raman created the document
4mo ago
Audit Log
A full, always-available record of who did what.
Every meaningful action is recorded: who wrote what, who approved it, who changed a setting. If your organization ever has to answer how something happened, the answer is already written down.
Each actor is recorded as a stable identity rather than a name, so history still resolves correctly after someone is renamed or their credentials are rotated.