Convert the tabletop RPG adventure I provide into a valid Codex Cryptica Adventure JSON v1 document. Schema: https://codexcryptica.com/schemas/adventure-json/v1.json Guide: https://codexcryptica.com/adventure-import Before converting, confirm you have this whole prompt, from the opening conversion instruction through the standalone line “END OF ADVENTURE JSON V1 CONVERSION PROMPT” after the final checklist. If it is missing or cut off, stop. Ask the user to select “Copy conversion prompt” on the guide and paste the entire prompt into this chat. Wait for it before making an inventory or generating any chunk. A “Continue” request does not replace the missing prompt. The complete prompt includes the field contract. If the separate schema URL is unavailable, use that contract without asking the user to paste the schema. Output contract (read this first): - Deliver ONE JSON object. If you can create files (a downloadable attachment, canvas or code-tool output), deliver it as a file named after the "id", such as "the-last-grind.json", containing only the JSON, and say only that the file is ready. If you cannot create files, your entire reply is the JSON object: it starts with "{" and ends with "}", with no Markdown code fences and no text before or after it. Never put JSON in a chat reply when you could have attached a file. - Include all 11 collection arrays, using [] when empty. - Use only the field names and exact values listed below. Do not add properties. - Never invent facts. When the source is unclear, record it in "unresolved". - Never shorten the conversion by dropping or merging entries. If the source is unreadable or inaccessible, name the missing input or page range and ask for readable text or a smaller upload. Never guess. - If a faithful full conversion will not fit, start staged conversion now. Do not just tell the user to use the staged method. Automatic staging when the full conversion will not fit: 1. Before generating JSON, inspect the source and make a numbered inventory of all visible sections and their source ranges. For paginated sources, record physical page ranges and flag unreadable or unseen pages separately. For sources without pagination, use headings, anchors or another stable source range; never invent page numbers. Split dense sections into small, non-overlapping chunks. If a page or source range has two sections, say which part each chunk owns. List every expected source-supported entry by collection with its name and planned ID, and mark the section that defines it. Write the exact top-level metadata values in the checkpoint, including the player-safe premise. Reuse them unchanged in every chunk. Assign one ID and defining chunk per shared entity. 2. Convert in source order. Each chunk is a separate JSON object with the same top-level metadata and all 11 arrays. Name files chunk-01.json, chunk-02.json, and so on. Define each entry only in its owning chunk. References to other known chunk IDs may remain pending until assembly. Before marking a chunk complete, compare its actual JSON IDs and per-collection counts with the expected IDs and counts for that section in the inventory; list every missing or unexpected ID and any count mismatch, and do not mark the chunk complete while any discrepancy remains unexplained. Record every completed chunk and any omitted material. Never present an unfinished chunk as complete. If a chunk is too large, split it and retry from the start. 3. If you can create files and keep working within the available limits, save the inventory and proceed with the chunks now. Otherwise return the inventory and checkpoint as plain text, with the next chunk's name and source range and the exact instruction "Continue with chunk 01" (use the actual next number). On continuation, use the existing checkpoint and convert only the requested chunk. Deliver one chunk as raw JSON if you cannot create files. Keep progress notes in separate messages or files, never in the JSON. Ask only for a source range or checkpoint you no longer have. 4. Assemble only after every planned chunk is present, each section's expected IDs and per-collection counts have been compared with its actual chunk JSON, coverage has been checked against the source, and shared metadata and IDs agree. Resolve references against the combined package. If you can run the v1 schema and semantic validator, validate before calling the file ready. Otherwise label the result unvalidated and ask the user to check it in Codex Cryptica. If you cannot assemble reliably, list the saved chunks and point to the assembler at https://codexcryptica.com/adventure-import#long-adventures. Never label an inventory, partial chunk set, or truncated reply as the final adventure. Conversion procedure (do this silently while writing JSON; return the checkpoint when staging needs another turn): - Inventory the source by section before writing JSON. Track keyed locations, actors, encounters and their resolutions, clues and alternate sources, rumours, important items, and authored endings. Preserve distinct entries and their source references. - Classify what the source states, what someone in the story claims, and what the GM decides. Use "unverified" when rumour truth is unspecified. Preserve optional routes and conditional actions without turning them into mandatory scene order. Leave unsupported fields out and record material gaps in "unresolved". - Audit the result against the inventory. Check each player-visible field and premise field for concealed information, and check that each reference points to the right collection and entity. For labelled PDF excerpts, use the original PDF file positions given in the source. Shape of a valid answer (trimmed: yours will have more entries and fields). Its ids, codes and wording are only illustrative; use your own, taken from the source: { "formatVersion": "adventure-json/v1", "id": "silent-watchtower", "title": "The Silent Watchtower", "version": "1.0.0", "premise": { "background": "A hillside watchtower has gone dark.", "hook": "The Reeve asks the party to relight the beacon." }, "source": { "title": "The Silent Watchtower" }, "locations": [ { "id": "loc-tower", "name": "Ridge Watchtower", "summary": "A stone signal tower above the valley road.", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "actors": [ { "id": "actor-tomas", "name": "Reeve Tomas", "summary": "The worried village official who hires the party.", "role": "Village reeve", "locationId": "loc-tower", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "factions": [], "scenes": [ { "id": "scene-beacon", "title": "The Cold Beacon", "summary": "The brazier at the top of the tower is unlit.", "locationId": "loc-tower", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "encounters": [ { "id": "enc-stuck-door", "title": "The Barred Door", "description": "The tower door is barred from the inside.", "alternativeSolutions": [ { "method": "Talk", "description": "Convince the watchman inside to lift the bar." } ], "locationId": "loc-tower", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "clues": [ { "id": "clue-oil-smell", "text": "The brazier smells of fresh lamp oil.", "reveals": "Someone tended the beacon recently.", "placedLocationId": "loc-tower", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "rumours": [ { "id": "rumour-ghost-light", "text": "A ghost puts the beacon out each night.", "truth": "false", "sourceActorId": "actor-tomas", "visibility": "player-visible", "epistemicStatus": "explicit" } ], "items": [], "secrets": [ { "id": "secret-tomas-motive", "text": "Tomas put the beacon out himself to hide a smuggling run.", "relatedEntityIds": [ "actor-tomas" ], "visibility": "gm-only", "epistemicStatus": "explicit" } ], "endings": [ { "id": "ending-lit", "description": "The beacon burns again and the caravan passes safely.", "epistemicStatus": "explicit" } ], "unresolved": [ { "id": "unresolved-oil", "code": "missing-detail", "message": "The source does not say where the lamp oil is kept.", "epistemicStatus": "unresolved" } ] } Strict output rules: 1. For a successful conversion, return ONLY valid JSON matching Adventure JSON v1 (no Markdown fences, no prose outside the JSON). Keep staging checkpoints and unreadable-source requests separate from all JSON. 2. Top-level fields: - Required: "formatVersion": "adventure-json/v1", "id" (/^[a-zA-Z0-9_-]{3,64}$/), "title" (1-200 chars), "version" (strict SemVer, e.g. "1.0.0"), "premise": { "background": string, "hook": string, "theme"?: string[], "tone"?: string }, "source": { "title": string, "authors"?: string[], "publisher"?: string, "publishedDate"?: string, "url"?: string, "license"?: string, "documentHash"?: string (64 lowercase hex chars) }. - Optional: "description": string, "system": { "name": string, "targetParty"?: { "sizeMin"?: integer >= 1, "sizeMax"?: integer >= 1, "levelMin"?: integer >= 0, "levelMax"?: integer >= 0 } }. - Required 11 collection arrays ([] when empty): "locations", "actors", "factions", "scenes", "encounters", "clues", "rumours", "items", "secrets", "endings", "unresolved". 3. Source certainty (CRITICAL): - Every entity requires "epistemicStatus": "explicit" | "inferred" | "ambiguous" | "unresolved". - Do not invent missing facts merely to fill fields. Omit optional fields when the source is silent. - Use "explicit" only for what the source states. Use "inferred" for anything you worked out yourself (links, endings, roles, unstated consequences). - For entries in "unresolved", use "ambiguous" when the source is unclear or contradictory, or "unresolved" when it does not answer the question; never use "explicit" or "inferred". 4. Collection entry contract (? = optional; non-empty strings required for id, name, title, text, description, code, message): - Every collection entry requires "id" (non-empty string) and "epistemicStatus"; "sourceRef" is optional. - locations: required name, summary, visibility; optional description: string, parentLocationId: string, connections: LocationConnection[]. - actors: required name, summary, visibility; optional description: string, role: string, motivation: string, disposition: string, factionId: string, locationId: string. - factions: required name, summary, visibility; optional description: string, goals: string[], dispositionTowardsParty: string. - scenes: required title, summary, visibility; optional locationId: string, readAloud: string | string[], body: string, conditions: string[], branches: SceneBranch[], optional: boolean. - encounters: required description, alternativeSolutions (an array, [] if absent), visibility; optional title: string, sceneId: string, locationId: string, conditions: string[], actorIds: string[]. - clues: required text, visibility; optional reveals: string, leadTargetId: string, placedLocationId: string, placedActorId: string, placedSceneId: string, alternativeSourceId: string. - rumours: required text, truth ("true" | "false" | "partially-true" | "unverified", all strings), visibility; optional sourceActorId: string, sourceLocationId: string, targetEntityId: string. - items: required name, summary, visibility; optional description: string, locationId: string, actorId: string. - secrets: required text, visibility ("gm-only" only); optional relatedEntityIds: string[]. - endings: required description; optional title: string, conditions: string[]; visibility is not allowed. - unresolved: required code, message; optional relatedEntityId: string, context: string; epistemicStatus is "ambiguous" | "unresolved" only; visibility is not allowed. - SceneBranch: required targetSceneId: string, description: string; optional condition: string, optional: boolean. - LocationConnection: required targetLocationId: string; optional description: string, travelConditions: string[]. - Each alternativeSolutions entry requires method: non-empty string and description: non-empty string; optional socialBypassOfCombat: boolean. - Do not emit properties absent from the strict schema. Common slips: encounters use "description" (not "summary"); clues use "placedLocationId" (not "locationId"); rumours use "truth" as a string (not a boolean such as "isTrue"). - Record named objects the source gives importance (clue objects, handouts, treasure) in "items", and give each "unresolved" entry a specific "code" that describes its own problem. 5. Visibility & secrets: - Keep the title, hook, background, and optional description player-safe and limited to source-supported facts; do not put concealed information in these fields. - Require "visibility": "player-visible" | "gm-only" on locations, actors, factions, scenes, encounters, clues, rumours, items, and secrets only. Do not add visibility to endings or unresolved. Every entry in "secrets" MUST have "visibility": "gm-only". - "visibility" applies to the WHOLE record, never to individual fields. Put only what players can know in a "player-visible" record, and move any concealed role, motive or detail into a separate "secrets" entry that lists the record in "relatedEntityIds". When a record cannot be split cleanly, mark it "gm-only" and add an "unresolved" entry. - Do not over-hide. Keep on the visible record whatever players can learn in play (a stated role, public detail, or harmless goal). Do NOT promote NPC testimony, rumours, or handouts to objective truth unless confirmed by the authored text. 6. Structural integrity: - Every entity ID across all collections must be unique and non-empty. All cross-references (parentLocationId, locationId, factionId, sceneId, targetSceneId, actorIds, placedLocationId, placedActorId, placedSceneId, leadTargetId, relatedEntityIds, relatedEntityId) must point to existing IDs and never self-reference. Location parentLocationId chains must not form cycles. - Every non-entry scene with source-supported progression must be reachable via scene branches from scenes[0], with no inescapable mandatory dead-end loops. If progression is unknown, preserve the scene as ambiguous without inventing a branch. - If the source has no authored order (a sandbox or location-based module), list scenes in source order, add branches only where the source states them, set "epistemicStatus": "ambiguous" on every scene that no earlier scene links to, and add one "unresolved" entry saying the order is left to the GM. Do not invent a flow or an ending. 7. Provenance & copyright: - Add "sourceRef" ({ page?: integer >= 1, pageEnd?: integer >= 1, chapter?: non-empty string, section?: non-empty string, anchor?: non-empty string, textQuote?: non-empty string }) wherever known. For a PDF, include "page" (and "pageEnd" when it spans pages) on every entry using the page position in the file, not a number printed on the page. - Write concise structured summaries, key dialogue, and room briefs rather than copying large blocks of prose verbatim. Omit playthrough state or session history. 8. Self-audit before returning (do not output this check): - Confirm every source section/page, named actor, location, mandatory/optional scene (marked "optional"), missable clue ("alternativeSourceId"), encounter option ("alternativeSolutions"), and intended ending is accounted for, and anything missing, cut or uncertain has an "unresolved" entry naming the source section. 9. Revisions and stable IDs: - If an earlier Adventure JSON for the same adventure is supplied, keep its "id" exactly, keep every unchanged entity ID exactly, and raise "version" by SemVer. - Add a top-level "extensions" entry "codex-cryptica.adventure-correspondence" (a list of { "previousId", "currentId", "collection" }) only for renames, splits or merges the source clearly supports. Never infer correspondence from names, titles or order, and never put "extensions" inside an entity. If no earlier package is supplied, use "version" "1.0.0" and omit the correspondence extension. 10. Game mechanics and maps: - Never add fields outside the v1 schema for stats, DCs, hit points, maps, grids or images, and never put mechanics in "extensions". Keep mechanics only as a short source-grounded paraphrase with "sourceRef" inside "description", "body", "conditions" or "alternativeSolutions[].description", and record any unrepresentable mechanic, stat block or map as an "unresolved" entry naming the source section (never invent values for it). Sandbox conversion: Put keyed rooms in "locations" and their hazards, opponents and tactical responses in "encounters" or other appropriate collections. Add "scenes" only for authored beats. If any scene outside scenes[0] is unreachable by following branches from scenes[0], give it epistemicStatus "ambiguous" rather than inventing links. A link from another unreachable scene does not make it reachable. Keys, room adjacency and conditional enemy tactics alone do not establish scene progression. Final visibility audit: Adding a fact to "secrets" is not enough. Check every copy of it across locations, actors, scenes, encounters, clues, summaries, and the premise. Before discovery, a hidden creature, trap, concealed access, or ambush plan must be absent from all player-visible names, text, IDs, and linked details. Preserve discoverable information in a GM-only record until it is revealed. Keep only sensory details or public facts in visible entries. Do not reproduce stat blocks in visible or GM fields; paraphrase the action or consequence and cite an unresolved entry for mechanics the schema cannot represent. Evidence and citations: Put each source-supported investigative observation in "clues" even when its text also appears in a room description or scene. Preserve where the evidence can be found, and add a revelation only if the source supports it. Do not turn incidental colour into a clue. For paginated sources, cite the page position and heading that describe the entry itself. For unpaginated sources, cite a supported section, anchor or other stable source range; never invent page numbers. For a keyed room, cite its key entry rather than an earlier mention, direction or cross-reference. Before you reply with a successful conversion, check each of these: - The result is only the JSON object (as a file, or as your whole reply), with no code fences or commentary. - All 11 collection arrays are present, every id is unique, and every cross-reference points to an existing id. - Every "secrets" entry is "gm-only", and no "player-visible" record reveals a hidden role, motive or detail. - Every entry has "epistemicStatus"; endings and unresolved have no "visibility". - Nothing outside the schema was added and nothing was invented. END OF ADVENTURE JSON V1 CONVERSION PROMPT