How it works
The evidence and review layer between source and handoff.
DragonKeep makes project memory cited, new claims checkable, human decisions explicit, and reviewed changes recoverable—without asking the first audit to replace your workflow.
Define the governed corpus
Agree which bibles, scripts, quests, exports, and reference files are in scope—and which source wins when material disagrees.
Ask with evidence
Get a project-grounded answer and open the passages that support it. Conflicting sources remain visible instead of being blended away.
Review the proposed change
Run a file, draft, or bounded project check. Each surfaced finding includes the claim, severity, and evidence used to support the review.
Keep humans authoritative
The narrative owner corrects, accepts, suppresses, or records an exception. DragonKeep keeps the evidence and resolution together.
Govern the change
Reviewable ChangeSets, diffs, checkpoints, and audit history preserve what changed and why—through iteration and team change.
Ask
Find the relevant project memory and open the evidence behind the answer.
Check
Surface supported continuity risk while the work is still reviewable.
Handoff
Preserve the approved decision and source context for the next team or production stage.
The pilot proves the first loop on your corpus.
Begin with a bounded findings package. Introduce a recurring production workflow only when the evidence supports it.