| name | adv-adapt |
| description | Adapt an existing novel, screenplay, article, or other source work into a traceable ADV.JS visual novel. Use when an ADV.JS project must preserve source order, characters, scenes, events, or licensing; split a source into .adv.md chapters; distinguish canonical material from new branches; or prove source-section coverage before release. |
ADV Source Adaptation
Build an adaptation whose structural coverage can be checked without pretending that automation can judge semantic fidelity.
Workflow
1. Establish the source contract
Record every source work before writing scripts:
- canonical title, author, stable URL, local snapshot or revision, and license;
- explicit order when several works form a sequence;
- heading-level section inventory with stable lowercase IDs;
- requested fidelity mode: complete canonical, faithful compression, or free reinterpretation.
Separate story prose from author metadata at this point. Forewords, postscripts, contest notes, revision notes, source-order explanations, and license/attribution text belong in the manifest or About page unless the user explicitly wants them dramatized. Record exclusions with required: false and an excludedReason; do not silently delete them.
Stop and resolve missing rights or contradictory source versions before copying text or publishing assets.
2. Create the adaptation manifest
Read references/adaptation-manifest.md and create adv/adaptation.json. Include all source sections, a complete cast, scenes, terminology, and the boundary between canonical and newly authored content.
For complete-canonical adaptations, mark every prose section that must survive as required: true. Do not mark forewords or postscripts optional merely because they are not dramatic scenes unless the user explicitly excludes them.
3. Build the authoring inventories
