Design partner pilot · canon-risk audit
Start with a result, not a rollout.
Every pilot opens with a canon-risk audit. Give DragonKeep one real project corpus and receive a bounded, cited view of continuity risk—without replacing your wiki, authoring tools, or production tracker.
What you receive
A decision-ready findings package.
Corpus and coverage map
An agreed boundary for what was supplied, what was processed, and where source gaps or authority conflicts limit a conclusion.
Cited findings report
Supported contradiction and ambiguity findings with severity, the relevant claims, and the source evidence used for review.
Human-reviewed top 20
A prioritized risk list reviewed before delivery. Automation proposes evidence; the report does not pretend to be exhaustive truth.
Working readout
A focused session on the findings, corpus quality, and the recurring workflow that would be worth proving in a pilot.
The boundary
One corpus. One accountable close.
The audit is intentionally narrow enough to sign and finish. Corpus size, source authority, technical access, and the definition of delivery are agreed before work begins.
Not included by default
Workflow migration, bespoke connectors, continuous monitoring, SSO/SCIM, 24/7 support, additional titles, or an assurance that every possible contradiction will be found.
- 1
Before content moves
Agree the corpus, authority rules, deployment mode, access, retention, export, and deletion path.
- 2
Days 1–2
Ingest the bounded source set and produce the corpus and coverage map.
- 3
Days 3–7
Run checks, inspect source support, group related findings, and remove weak or duplicate items.
- 4
Days 8–9
Human-review the top 20 and prepare the cited findings report.
- 5
Day 10
Deliver the report, hold the readout, and complete the agreed export or deletion step.
Content handling is agreed before ingestion.
Pilots run on our managed cloud deployment by default — nothing to install, and the data flow, provider, access, retention, and deletion terms are disclosed for approval before content moves. Customer-hosted and local-model configurations can be scoped at enterprise level where the environment requires them.
Review deployment and data handlingCredit-forward path
You never pay for the same proof twice.
The $500 pilot fee is credited in full toward your first annual license — if you convert, the pilot cost you nothing extra. If you stop after the pilot, you keep the audit deliverables and the agreed data export or deletion.
See full pricingBring the corpus as it really is.
Bibles, scripts, quest documents, exports, and inherited files are all useful inputs to a scoping conversation.
Apply for a design partner pilot