Connect the source to the right docs.
Choose a service and link it to the documentation you manage in DragonKeep. That gives Systems a defined set of material to maintain.
For engineering teams
The code changed.
The docs shouldn’t be another task.
Systems handles routine updates to the documentation you keep in DragonKeep. Your team can get on with the next change, without hunting down every paragraph the last one affected.
Early access · Start with one service
Five attempts became six. The docs already know.
The service changed. Systems checked the new value and updated the delivery guide automatically. Nobody had to find that paragraph and rewrite it.
The change comes with its explanation.
Open the update to see the source behind it and the checks it passed. The answer to “why did this change?” is already attached.
A changed setting.An updated paragraph.One less task to assign.
Let the routine work happen
“Update the docs”
can stop being
the next ticket.
The value is a piece of maintenance finished. Here’s how that happens.
Let Systems handle the routine updates.
When source changes arrive, Systems prepares targeted edits, checks them, and applies the updates that meet its checks.
Spend your attention on the decisions.
Routine updates get done. When a change touches a customer commitment, your team gets the context to make the decision.
A clear place to start
Which paragraph
does someone keep
having to fix?
A configuration default. A renamed setting. A service guide that trails behind the implementation.
Start with a recurring update your team can point to. Systems maintains the connected documents inside DragonKeep, so choosing and bringing in that documentation is part of setup.
Then see how much of that maintenance your team can leave to it.
One-service documentation pilot
Try it on work
you actually have.
Bring one changing service, a small set of docs, and the person who looks after them. We’ll follow real changes through to the resulting updates.
Discuss your serviceWhat we’ll look at togetherA service that moves.
A service that moves.
Docs that move with it.
- Your routine documentation updates, completed
- A clear record of what changed and why
- Your team focused on the decisions that matter
We agree the scope and price with you before the pilot begins. Systems is in early access.
A few useful answers
Before you begin.
Where does our documentation live?
The documentation Systems maintains lives in DragonKeep. You connect the relevant source material to those documents during setup.
Does someone have to approve every update?
Routine factual updates can be checked and applied automatically. Your team stays in charge of decisions such as changing a customer commitment, with the relevant context close by.
Can we see what it changed?
Yes. The edits, supporting evidence, and change history are available to inspect, so your team can review what happened and follow up on exceptions.
What makes a good first pilot?
One service that changes regularly, a small documentation set, and a person who can tell whether an update is right. A repeated task, such as updating a configuration default in a service guide, is a useful starting point.