What MANIFEST does
MANIFEST migrates a DITA map to MyST Markdown for Sphinx and proves that every topic arrived complete. The overview shows how the migration program is doing against its targets.
Teams moving from DITA to docs as code usually lose content without noticing: a conref that becomes a copy, a condition that disappears, an anchor that no longer exists. MANIFEST converts with DITA-OT 4.4, restores the reuse as MyST includes and substitutions, and then compares the result with DITA-OT's own HTML5 output of the source, topic by topic and build by build.
The checks decide whether a topic passes. The agent can propose a fix, but it can't change a check result, and a writer approves every rule before it is used again.
The numbers on the overview
- Unreported losses
- Content lost without appearing in the report. The target is 0.
- Reuse kept
- Conrefs and key references that arrived as includes and substitutions.
- Topics passed without a writer
- Topics with no difference and nothing to review.
- Fixes approved
- Mapping rules a writer has approved. Each one runs on every later map without the agent.
- Broken links
- Broken links, navigation differences and old URLs that no longer resolve. The target is 0.
- Writer hours saved
- A model, not a measurement: topics passed without a writer multiplied by the minutes a manual check takes.
- Cost per map
- Cloud Run seconds and Gemini tokens at list price. Inside the free tier the bill is zero; the calculation is shown.