{
  "schemaVersion": "2.0.0",
  "project": "Namewoven",
  "asOf": "2026-11-01",
  "countingUnit": "one proposed primary user task; locale variants excluded",
  "target": 967,
  "productionOrigin": null,
  "categories": [
    {
      "id": "character-foundations",
      "name": "Character foundations",
      "audience": "novelists and character designers",
      "count": 34,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "kinship",
      "name": "Kinship and households",
      "audience": "family saga authors and comics writers",
      "count": 37,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "ensemble",
      "name": "Ensembles and relationship casts",
      "audience": "ensemble fiction and manga creators",
      "count": 41,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "identities",
      "name": "Aliases and identity reveals",
      "audience": "mystery, thriller and transformation writers",
      "count": 37,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "address",
      "name": "Names in dialogue and relationships",
      "audience": "dialogue writers and manga letterers",
      "count": 32,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "pen-names",
      "name": "Pen names and author identity",
      "audience": "fiction writers and manga authors",
      "count": 30,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "japanese-writing",
      "name": "Japanese character names and readings",
      "audience": "Japanese language fiction and manga creators",
      "count": 38,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "localization",
      "name": "English Japanese localization",
      "audience": "translators and bilingual creators",
      "count": 36,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "manga-production",
      "name": "Manga and comic production",
      "audience": "manga writers, artists and letterers",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "audio-drama",
      "name": "Motion comics and performed names",
      "audience": "motion comic writers and voice teams",
      "count": 25,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "game-characters",
      "name": "Game character naming systems",
      "audience": "narrative designers and game writers",
      "count": 41,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "game-ui",
      "name": "Game name presentation and production",
      "audience": "UI designers and technical narrative teams",
      "count": 29,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "tabletop",
      "name": "Tabletop and live collaborative fiction",
      "audience": "game masters and collaborative storytellers",
      "count": 29,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "world-grammar",
      "name": "Invented culture naming grammars",
      "audience": "worldbuilders and speculative fiction writers",
      "count": 40,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "titles",
      "name": "Titles, epithets and earned identities",
      "audience": "fantasy, historical fiction and game writers",
      "count": 33,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "nonhuman",
      "name": "Nonhuman and constructed identities",
      "audience": "speculative fiction and game creators",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "mystery",
      "name": "Mystery and fair naming clues",
      "audience": "mystery authors and puzzle narrative designers",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "speculative-plots",
      "name": "Names driving speculative plots",
      "audience": "speculative novel and comic creators",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "narrative-arcs",
      "name": "Names across character arcs",
      "audience": "novelists and serial storytellers",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "setting-linked",
      "name": "Personal names tied to settings",
      "audience": "worldbuilders and setting focused writers",
      "count": 35,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "institutions",
      "name": "Groups that shape personal naming",
      "audience": "worldbuilders and ensemble creators",
      "count": 34,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "historical-research",
      "name": "Historical and cultural evidence workflows",
      "audience": "historically situated fiction creators",
      "count": 29,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "manuscript-audit",
      "name": "Manuscript and series name maintenance",
      "audience": "novel editors and serial creators",
      "count": 38,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "reader-tests",
      "name": "Reader testing and name evaluation",
      "audience": "authors and editorial teams",
      "count": 24,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "editorial-content",
      "name": "Name related creative exercises",
      "audience": "writers learning naming through practice",
      "count": 29,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "data-methods",
      "name": "Name data and evidence management",
      "audience": "creators building reusable naming resources",
      "count": 20,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    },
    {
      "id": "project-workflows",
      "name": "Creative project naming decisions",
      "audience": "authors and production collaborators",
      "count": 19,
      "basis": "Counts follow the written scenario inventory; no equal allocation or demand weighting. Demand and page eligibility remain unvalidated."
    }
  ],
  "sources": [
    {
      "id": "w3c-names",
      "title": "W3C: Personal names around the world",
      "url": "https://www.w3.org/International/questions/qa-personal-names",
      "checked": "2026-11-01",
      "type": "primary-technical-guidance",
      "supports": "Avoid assuming one universal first-name / last-name structure; retain flexible forms.",
      "limits": "Introductory guidance is not proof of a particular candidate name, pronunciation, or every culture's practices.",
      "license": "Reference only; no name corpus copied.",
      "imported": false
    },
    {
      "id": "scrivener",
      "title": "Literature & Latte: How to Manage Your Characters in Scrivener",
      "url": "https://www.literatureandlatte.com/blog/how-to-manage-your-characters-in-scrivener",
      "checked": "2026-10-31",
      "type": "first-party-product-documentation",
      "supports": "An established writing workflow already supports name lists, component locks, initials and alliteration. These settings alone are weak independent-page rationales.",
      "limits": "Shows product behavior, not market size or demand for Namewoven.",
      "license": "Reference only; no proprietary lists copied.",
      "imported": false
    },
    {
      "id": "ink",
      "title": "inkle: Writing with ink",
      "url": "https://github.com/inkle/ink/blob/master/Documentation/WritingWithInk.md",
      "checked": "2026-10-31",
      "type": "first-party-technical-documentation",
      "supports": "Interactive stories have variable and branching state; naming architecture should distinguish identity state and display.",
      "limits": "Identity-ledger design is this project's inference, not an Ink feature claim.",
      "license": "Reference only; no code copied.",
      "imported": false
    },
    {
      "id": "renpy",
      "title": "Ren'Py: Translation",
      "url": "https://www.renpy.org/doc/html/translation.html",
      "checked": "2026-11-01",
      "type": "first-party-technical-documentation",
      "supports": "Dialogue, interface text, images and styles are distinct localization surfaces.",
      "limits": "Does not establish a translation choice or promise an existing integration.",
      "license": "Reference only; no runtime dependency or code imported.",
      "imported": false
    },
    {
      "id": "moj-reading",
      "title": "法務省：戸籍にフリガナが記載されます",
      "url": "https://www.moj.go.jp/MINJI/furigana/",
      "checked": "2026-10-31",
      "type": "government-primary-source",
      "supports": "In the specified Japanese registry context, readings became recorded name information following the reform effective 2025-05-26.",
      "limits": "Not a source of candidate name readings, registration approval, period-wide custom or legal advice; institutional scope only.",
      "license": "Reference only; no personal registry data collected.",
      "imported": false,
      "latestAttempt": {
        "date": "2026-11-01",
        "status": 403,
        "note": "Latest re-fetch blocked; historical checked date preserved. Not freshly reverified."
      }
    },
    {
      "id": "edrdg",
      "title": "EDRDG: General Dictionary Licence Statement",
      "url": "https://www.edrdg.org/edrdg/licence.html",
      "checked": "2026-11-01",
      "type": "primary-license-source",
      "supports": "General dictionary licence, attribution, share-alike derived data and update conditions verified; licence copies retained.",
      "limits": "Dictionary evidence is not etymology, popularity or universal cultural suitability.",
      "license": "CC-BY-SA-4.0; imported personal-component subset with notices.",
      "imported": true
    },
    {
      "id": "google-js",
      "title": "Google Search Central: JavaScript SEO basics",
      "url": "https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics",
      "checked": "2026-10-31",
      "type": "first-party-search-documentation",
      "supports": "Initial HTML, crawlable links and correct status codes support discoverability; pre-rendering remains useful.",
      "limits": "No indexing or ranking guarantee.",
      "license": "Reference only; no documentation republished.",
      "imported": false
    },
    {
      "id": "google-locales",
      "title": "Google Search Central: Localized versions of pages",
      "url": "https://developers.google.com/search/docs/specialty/international/localized-versions",
      "checked": "2026-10-31",
      "type": "first-party-search-documentation",
      "supports": "Plan explicit language versions and corresponding language-alternate relationships.",
      "limits": "Applied only when independently complete locales are publicly released.",
      "license": "Reference only.",
      "imported": false
    },
    {
      "id": "google-robots",
      "title": "Google Search Central: Robots meta tags",
      "url": "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag",
      "checked": "2026-10-31",
      "type": "first-party-search-documentation",
      "supports": "Use crawl-visible noindex for internal review pages; do not assume robots disallow removes indexed URLs.",
      "limits": "Local staging is not a production indexing test.",
      "license": "Reference only.",
      "imported": false
    },
    {
      "id": "google-ai",
      "title": "Google Search Central: AI features and your website",
      "url": "https://developers.google.com/search/docs/appearance/ai-features",
      "checked": "2026-10-31",
      "type": "first-party-search-documentation",
      "supports": "Google documents no additional special technical requirements for its AI features; inclusion is not guaranteed.",
      "limits": "Does not generalize to every AI provider. Project clarity and evidence policies are internal quality requirements.",
      "license": "Reference only.",
      "imported": false
    },
    {
      "id": "wcag22",
      "title": "W3C: How to Meet WCAG 2.2",
      "url": "https://www.w3.org/WAI/WCAG22/quickref/",
      "checked": "2026-10-31",
      "type": "primary-accessibility-standard-guidance",
      "supports": "Use labeled inputs, keyboard access, readable contrast, semantic structure and reflow checks.",
      "limits": "No certification or full accessibility conformance claimed; manual assistive technology testing remains outstanding.",
      "license": "Reference only.",
      "imported": false
    },
    {
      "id": "whatwg-canvas",
      "title": "WHATWG HTML: Canvas text metrics",
      "url": "https://html.spec.whatwg.org/multipage/canvas.html#dom-context-2d-measuretext-dev",
      "supports": "Browser measureText returns font text metrics.",
      "limits": "Not evidence of font coverage, readability, layout certification or cultural appropriateness.",
      "checked": "2026-11-01",
      "type": "primary-technical-standard",
      "license": "Reference only; no code or corpus copied.",
      "imported": false
    },
    {
      "id": "whatwg-media",
      "title": "WHATWG HTML: Media duration",
      "url": "https://html.spec.whatwg.org/multipage/media.html#dom-media-duration-dev",
      "supports": "Media duration metadata can be read by the browser.",
      "limits": "Clip length only; no intelligibility or pronunciation measurement.",
      "checked": "2026-11-01",
      "type": "primary-technical-standard",
      "license": "Reference only; no code or corpus copied.",
      "imported": false
    },
    {
      "id": "ssa-source",
      "title": "SSA national names: source qualifications",
      "url": "https://www.ssa.gov/oact/babynames/background.html",
      "supports": "US application records, spelling tabulation, incomplete coverage and privacy suppression.",
      "license": "US government source; dataset catalog marks CC0.",
      "checked": "2026-11-01",
      "type": "primary-source",
      "limits": "Source-specific scope, no naturalness or rights clearance guarantee.",
      "imported": true
    },
    {
      "id": "ssa-license",
      "title": "Data.gov: SSA national names metadata",
      "url": "https://catalog.data.gov/dataset/baby-names-from-social-security-card-applications-national-data",
      "supports": "Publisher, coverage and explicit CC0 metadata.",
      "license": "CC0 metadata reference.",
      "checked": "2026-11-01",
      "type": "primary-source",
      "limits": "Source-specific scope, no naturalness or rights clearance guarantee.",
      "imported": true
    },
    {
      "id": "jmnedict-source",
      "title": "EDRDG: ENAMDICT/JMnedict documentation",
      "url": "https://www.edrdg.org/pub/Nihongo/enamdict_doc.html",
      "supports": "Source types and written/reading structure.",
      "license": "CC BY-SA 4.0; attribution, documentation and derived-data notices retained.",
      "checked": "2026-11-01",
      "type": "primary-source",
      "limits": "Source-specific scope, no naturalness or rights clearance guarantee.",
      "imported": true
    },
    {
      "id": "unicode-normalization",
      "title": "Unicode UAX #15: Unicode Normalization Forms",
      "url": "https://www.unicode.org/reports/tr15/",
      "checked": "2026-11-01",
      "type": "primary-technical-standard",
      "supports": "Normalization concerns encoded-text equivalence; original display preservation and fictional identity/asset approval are separately designed here.",
      "limits": "Not evidence that any two real personal-name glyph forms may be substituted, or that a font supports a sequence.",
      "license": "Reference only; no tables or prose imported.",
      "imported": false
    },
    {
      "id": "austen-pride-prejudice",
      "title": "Jane Austen: Pride and Prejudice, chapters I and XIX",
      "url": "https://www.gutenberg.org/cache/epub/1342/pg1342-images.html",
      "checked": "2026-11-01",
      "type": "primary-literary-text",
      "supports": "The opening dialogue uses Lizzy; chapter XIX explicitly places Elizabeth and Lizzy in the same exchange. A narrow example of variable address for one identity.",
      "limits": "Our practical naming interpretation is original editorial advice, not an Austen-authored naming rule or historical family-law claim.",
      "license": "Reference and original paraphrase only; no passage, name corpus, illustration or translated text copied.",
      "imported": false
    },
    {
      "id": "unicode-segmentation",
      "title": "Unicode UAX #29: Unicode Text Segmentation",
      "url": "https://www.unicode.org/reports/tr29/",
      "checked": "2026-11-01",
      "type": "primary-technical-standard",
      "supports": "Text segmentation distinguishes grapheme, word and sentence boundaries. Runtime grapheme segmentation is used for authored clue extraction; whitespace-token extraction is our separate explicit policy.",
      "limits": "No claim that runtime data matches every newest revision, that one cluster is one printed glyph/syllable, or that a clue is fair.",
      "license": "Reference only; no tables or prose imported.",
      "imported": false
    },
    {
      "id": "ecmascript-string-operations",
      "title": "ECMAScript language specification: text processing",
      "url": "https://tc39.es/ecma262/multipage/text-processing.html",
      "checked": "2026-11-01",
      "type": "primary-technical-specification",
      "supports": "Specification of String.prototype.trim, toLowerCase and normalize. Applied only to explicitly declared pipeline operations.",
      "limits": "Runtime Unicode support and destination integration are separate; no full case-folding, locale or game-engine certification.",
      "license": "Reference only; no prose or algorithm tables redistributed.",
      "imported": false
    },
    {
      "id": "html-media-playback",
      "title": "WHATWG HTML Living Standard: media elements",
      "url": "https://html.spec.whatwg.org/multipage/media.html",
      "checked": "2026-11-01",
      "type": "primary-technical-specification",
      "supports": "Media events, played ranges and audio controls. Used to describe actual browser state, not human hearing.",
      "limits": "No proof of audibility, attention, independent participants or intelligibility. Internal coverage tolerance is not a standard requirement.",
      "license": "Reference only; no prose or tables imported.",
      "imported": false
    },
    {
      "id": "file-api-local",
      "title": "W3C File API: selected files and object URLs",
      "url": "https://www.w3.org/TR/FileAPI/",
      "checked": "2026-11-01",
      "type": "primary-technical-working-draft",
      "supports": "Selected file objects and local object URL lifecycle. Implementation uses no clip-upload request.",
      "limits": "Working draft; reference does not itself guarantee privacy of an arbitrary application. No external audio rights clearance.",
      "license": "Reference only; no prose or tables imported.",
      "imported": false
    },
    {
      "id": "w3c-simple-ruby",
      "title": "W3C — Rules for Simple Placement of Japanese Ruby",
      "url": "https://www.w3.org/TR/simple-ruby/",
      "checked": "2026-11-01",
      "type": "primary-technical-working-draft",
      "supports": "Terminology distinguishing mono, group and jukugo associations and placement considerations.",
      "limits": "First Public Working Draft dated 9 June 2020; not W3C endorsement. The Namewoven proof is a documented browser policy, not complete Japanese-composition conformance.",
      "license": "Reference only, paraphrased attribution; no illustrations or source prose imported.",
      "imported": false
    }
  ],
  "tools": [
    {
      "id": "nw-character-naming-brief",
      "slug": "character-naming-brief",
      "name": "Character naming brief",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-naming-brief/",
        "ja": "/ja/tools/character-naming-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Convert a role, setting and narrative distance into a testable name brief",
      "task": "Convert a role, setting and narrative distance into a testable name brief",
      "searchIntent": {
        "primary": "Complete the task: Convert a role, setting and narrative distance into a testable name brief",
        "queryHypothesis": "character naming brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to convert a role, setting and narrative distance into a testable name brief?",
        "When should character naming brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "role",
          "use": "Define narrative job and actual scenes."
        },
        {
          "key": "mustPreserve",
          "use": "Declare fixed story facts and existing names."
        },
        {
          "key": "evidenceNeeds",
          "use": "List real-language and historical claims needing support."
        }
      ],
      "rules": [
        "Separate hard constraints from preferences.",
        "Flag contradictory constraints and missing setting details.",
        "Convert each preference into a scene or reader check; do not invent a cultural fact.",
        "Recommend a task workflow based on the required decision, not a genre keyword."
      ],
      "requiredData": [
        {
          "description": "Author story brief",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Existing cast and source questions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Separate hard constraints from preferences.",
        "Flag contradictory constraints and missing setting details.",
        "Convert each preference into a scene or reader check; do not invent a cultural fact.",
        "Recommend a task workflow based on the required decision, not a genre keyword."
      ],
      "outputs": [
        "Prioritized decision brief",
        "Conflict list",
        "Suggested next task with reason"
      ],
      "capabilities": [
        "Explain which requested conditions cannot jointly be met.",
        "Create a scene-specific review checklist from the author's own stakes."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Turn an underspecified story request into ranked, testable naming requirements before choosing names; output is an actionable brief, not a candidate list.",
        "proposedDifferenceAxes": [
          "inputs",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "pen-name-designer",
          "difference": "Specifies a fictional identity's story obligations rather than an author's public credit."
        }
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-brief",
          "score": 0.21562499999999998,
          "sharedProfile": false,
          "difference": "Convert a role, setting and narrative distance into a testable name brief versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Convert a role, setting and narrative distance into a testable name brief versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-translation-brief",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Convert a role, setting and narrative distance into a testable name brief versus Preserve author intent across localized bylines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A good name begins with a decision brief that can reject an attractive but unusable candidate.",
        "outline": [
          "Separate wishes from obligations",
          "Name the scene where the choice matters",
          "Repair a contradictory brief",
          "Use evidence questions before a word pool"
        ],
        "story": "Fictional example: a novelist asks for a secret heir's conspicuously royal name, then discovers it spoils the opening disguise. The brief instead reserves the royal form for a later document.",
        "storyAnalysis": "The useful change is a revised information constraint, not a more unusual syllable.",
        "evidence": "Original brief and before-after knowledge constraints; demand unvalidated.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/brief.md",
        "localizedBodies": {
          "en": "content/en/brief.md",
          "ja": "content/ja/brief.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A locked name also excluded as an exact match creates a conflict.",
        "Unknown period stays unknown, not contemporary by default.",
        "A symbol request is labeled a creative preference.",
        "A family inheritance requirement routes to a graph task."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:2",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-01",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "brief",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/editorial-engines.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/editorial.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "role",
          "label": [
            "Character’s narrative action",
            "人物が物語で行うこと"
          ],
          "type": "textarea",
          "default": "A courier hides an inheritance claim while delivering a public invitation.",
          "help": null
        },
        {
          "key": "period",
          "label": [
            "Authored period · blank stays unknown",
            "設定した年代・空欄は不明"
          ],
          "type": "text",
          "default": "Invented late-industrial port",
          "help": null
        },
        {
          "key": "scope",
          "label": [
            "Language or evidence scope · blank stays unknown",
            "言語・根拠の範囲・空欄は不明"
          ],
          "type": "text",
          "default": "Invented naming conventions; no real etymology claimed",
          "help": null
        },
        {
          "key": "requirements",
          "label": [
            "Typed requirements and scene tests",
            "種類を指定した要件と場面の確認"
          ],
          "type": "textarea",
          "default": "r1 | fixed | Sela Morrow | must | Opening invitation signature\nr2 | exclude | Sela Vale | must | Existing cast list\nr3 | secret-until | 6 | must | Chapter 1 public introduction\nr4 | family | Shared family marker after reveal | must | Chapter 6 inheritance ledger\nr5 | symbol | Returning tide | prefer | Final voluntary signature",
          "help": [
            "ID | kind | value | must/prefer | scene or check location. Kinds: fixed, exclude (exact), prefix, min/max (graphemes), family, secret-until (chapter), reading, cast, prop, symbol. One identity per brief; no natural-language inference.",
            "ID | 種類 | 値 | must/prefer | 場面または確認箇所。種類：fixed、exclude（完全一致）、prefix、min/max（文字単位）、family、secret-until（章）、reading、cast、prop、symbol。一つの要件書は一人の人物。文章の意味は自動推定しません。"
          ]
        },
        {
          "key": "readingWorkflow",
          "label": [
            "Reading evidence workflow",
            "読みの根拠を確認する作業"
          ],
          "type": "select",
          "default": "unselected",
          "help": null,
          "options": [
            [
              "unselected",
              [
                "Not selected / another writing system",
                "未選択・別の文字体系"
              ]
            ],
            [
              "kana-ledger",
              [
                "Japanese written form + supplied kana ledger",
                "日本語の表記と入力した仮名の台帳"
              ]
            ]
          ]
        }
      ]
    },
    {
      "id": "nw-protagonist-name-shortlist",
      "slug": "protagonist-name-shortlist",
      "name": "Protagonist name shortlist",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/protagonist-name-shortlist/",
        "ja": "/ja/tools/protagonist-name-shortlist/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fiction and comic authors who have an existing shortlist for one protagonist.",
      "scenario": "A theatre-clock repairer learns to leave an ending for an apprentice to choose. Three name drafts support firmness, compact address and a quiet final pause in different ways; the writer must acknowledge a preference cycle rather than seek a fabricated quality score.",
      "task": "Compare supplied alternative names for one naming decision in an identical authored scene, inspect incomplete and cyclic preferences, preview a single uncommitted change, and record an explicit reasoned selection.",
      "searchIntent": {
        "primary": "Choose among an existing shortlist of protagonist names with scene-specific reasons.",
        "queryHypothesis": "choose between protagonist names shortlist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Does a cycle mean my naming preferences are wrong?",
        "Can a candidate be a winner before every direct pair is reviewed?",
        "How can I test one changed preference without replacing my real decisions?"
      ],
      "inputs": [
        {
          "key": "candidates",
          "type": "textarea",
          "purpose": "2–12 objects with exactly id/name/note. IDs are unique ASCII-letter-led identifiers ≤40; name is a single line ≤120, note ≤400. Repeated display names remain separate candidates. Notes are your own interpretation."
        },
        {
          "key": "scene",
          "type": "textarea",
          "purpose": "Use {name} exactly once, ≤1200 UTF-16 units. Every candidate gets the identical frame. The tool substitutes literal text; it does not generate dialogue or predict a reader reaction."
        },
        {
          "key": "context",
          "type": "textarea",
          "purpose": "Nonblank, ≤300. Changing this context stales previous comparisons and the final selection. This is one author’s decision scope, not a pooled audience study."
        },
        {
          "key": "judgments",
          "type": "textarea",
          "purpose": "Use the pair controls to prefer either candidate, tie or defer with a reason. Each decision binds its two candidate records, scene and context. No transitive decision fills a missing pair."
        },
        {
          "key": "selection",
          "type": "textarea",
          "purpose": "Choose a candidate and explain the tradeoff after reviewing the board. The choice binds all candidate and comparison records; later edits require a fresh decision. A cycle does not prevent a reasoned author choice."
        },
        {
          "key": "trial",
          "type": "textarea",
          "purpose": "Use the what-if controls to replace one comparison only in a separate preview. It never writes a real judgment, changes the explicit selection or enters the complete decision memo."
        }
      ],
      "rules": [
        "2–12 exact id/name/note records; identical scene frame with {name} once and an explicit decision context. Names are candidate alternatives for one author task, not a cast assignment.",
        "Every unordered pair has a direct a/b/tie/defer judgment with reason and exact candidate/scene/context expectation; absent, deferred, stale and orphan decisions remain unresolved. No preference path fills a missing comparison.",
        "Only current strict preferences form directed edges. Report one concrete cycle witness per mutually reachable cyclic component, not every circuit. A cycle is a tradeoff, not a logical contradiction or defect.",
        "Direct winner requires a win over every other supplied candidate. Possible winners have no current loss or tie. Counts are not artistic scores or reader-study statistics.",
        "One exact-context uncommitted trial replaces one preference in a separate graph without changing actual judgments, selection or memo. Stale/orphan trial is not applied and does not block a complete real memo.",
        "Final author selection needs a nonblank reason and all source candidates, scene, purpose and actual judgments as basis. Later edits stale it. Full memo requires every direct pair resolved and current selection; a cycle is allowed.",
        "Exports preserve original candidate notes and actual reasons. Trial is excluded from the complete memo; private audit preserves unfinished work and hypothetical records."
      ],
      "requiredData": [
        {
          "description": "Original fictional theatre-clock scene, alternative candidate names and author-interpretation notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied direct preference declarations and explicit naming choice, not fabricated reader responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "2–12 exact id/name/note records; identical scene frame with {name} once and an explicit decision context. Names are candidate alternatives for one author task, not a cast assignment.",
        "Every unordered pair has a direct a/b/tie/defer judgment with reason and exact candidate/scene/context expectation; absent, deferred, stale and orphan decisions remain unresolved. No preference path fills a missing comparison.",
        "Only current strict preferences form directed edges. Report one concrete cycle witness per mutually reachable cyclic component, not every circuit. A cycle is a tradeoff, not a logical contradiction or defect.",
        "Direct winner requires a win over every other supplied candidate. Possible winners have no current loss or tie. Counts are not artistic scores or reader-study statistics.",
        "One exact-context uncommitted trial replaces one preference in a separate graph without changing actual judgments, selection or memo. Stale/orphan trial is not applied and does not block a complete real memo.",
        "Final author selection needs a nonblank reason and all source candidates, scene, purpose and actual judgments as basis. Later edits stale it. Full memo requires every direct pair resolved and current selection; a cycle is allowed.",
        "Exports preserve original candidate notes and actual reasons. Trial is excluded from the complete memo; private audit preserves unfinished work and hypothetical records."
      ],
      "outputs": [
        "Literal scene previews, per-candidate direct wins/losses/ties/pending opponents and context-specific copy.",
        "All bounded direct pair questions, state and reason; graph cycle nodes and judgment IDs, actual and hypothetical direct/possible winners.",
        "Unresolved and orphan obligations, current/stale final choice, private worksheet always and complete naming decision memo only after required checks."
      ],
      "capabilities": [
        "Expose nontransitive author preferences with actual cyclic paths while refusing to infer unreviewed direct comparisons.",
        "Change one comparison in a separately labelled what-if graph without committing the preference or contaminating the final memo.",
        "Bind a reasoned final author choice to all candidates, scene, purpose and comparisons; preserve stale/orphan reasoning instead of silently discarding it."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The brief defines typed obligations before candidates exist, assignment distributes a name pool across several roles, and recall compares actual supplied participant responses. This board instead captures one author’s direct pairwise tradeoffs in a shared scene, refuses transitive filling, explains cyclic preferences, compares an isolated what-if graph and binds a final decision to its exact basis.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "character-naming-brief",
          "difference": "A requirements brief checks declared obligations and contradictions without comparing actual names. This tool compares concrete supplied alternatives with per-pair reasons, incomplete direct relationships, cycle witnesses and an explicit selected-name memo; preferences are not factual contradiction constraints."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-shortlist-blind-test",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare supplied alternative names for one naming decision in an identical authored scene, inspect incomplete and cyclic preferences, preview a single uncommitted change, and record an explicit reasoned selection. versus Collect unaided impressions without showing author explanations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Compare supplied alternative names for one naming decision in an identical authored scene, inspect incomplete and cyclic preferences, preview a single uncommitted change, and record an explicit reasoned selection. versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-scene-laboratory",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Compare supplied alternative names for one naming decision in an identical authored scene, inspect incomplete and cyclic preferences, preview a single uncommitted change, and record an explicit reasoned selection. versus Compare one scene written with three explicitly different naming decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A shortlist should lead to a scene-specific author decision, with tradeoffs and uncertainty retained rather than concealed by a quality score.",
        "outline": [
          "When generating more names stops helping",
          "Original theatre-clock scene and alternative-name counterfactual",
          "Prepare comparable candidate and scene scopes",
          "Record three direct comparisons without transitive assumptions",
          "Read preference cycles and narrow winner definitions",
          "Isolated one-comparison what-if",
          "Explicit final choice and complete memo",
          "Context invalidation, recovery and private handoffs"
        ],
        "story": "A miniature theatre clock repeats the same ending until an apprentice asks Oru Vale to leave one wheel unrepaired. The repairer leaves the last door under manual control, accepting a pause where different audience members imagine sea or sky. The name is compared at the exact line asking the repairer to relinquish automatic completion.",
        "storyAnalysis": "Changing Oru to Taren does not impose personality, but may lead this author to lengthen the reply’s hesitation. Character action still establishes the change. Firmness, compact address and quiet ending can support a cyclic preference rather than an objective ranking.",
        "evidence": "Complete original EN/JA theatre-clock guides with explicit name counterfactual, CHOICE-01–20, CHOICE-HTML, 34 persisted fresh browser reruns and four final bilingual viewport keyboard submissions. No measured audience response, attested name meaning or real clockmaking claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/nameChoice.md",
        "localizedBodies": {
          "en": "content/en/nameChoice.md",
          "ja": "content/ja/nameChoice.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default has three candidates, three unreviewed pairs, no inferred reader observations and no selected name.",
        "lan > mio > oru > lan shows a genuine closed preference cycle and no direct winner; all three resolved pairs permit an explicit reasoned author choice.",
        "A two-edge preference path never resolves the missing third pair. Ties count as completed comparisons but prevent strict direct wins.",
        "Reversing lan/oru only in trial yields a separate direct winner while the real cycle, stored judgments and complete memo stay unchanged.",
        "Source, purpose, actual reason and hidden judgment edits invalidate appropriate controls or selections. Orphans require explicit removal. Invalid input clears results; all 66 bounded pairs remain visible.",
        "Actual copies, favorites, complete memo/audit/project/results files, project restoration and both localized desktop/mobile keyboard submissions require recorded evidence."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:3",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-12",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Exact-context judgments and final decisions, bounded full pair matrix, directed cycle witnesses and isolated hypothetical graph; no fabricated effort or demand estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "nameChoice",
        "engineFiles": [
          "web/name-choice.mjs",
          "web/name-choice-tool.mjs",
          "web/name-choice-view.mjs",
          "web/name-choice-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/name-choice.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "candidates",
          "label": [
            "Name candidates · JSON",
            "名前候補・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"lan\",\n    \"name\": \"Taren Vale\",\n    \"note\": \"Strong opening consonant; the writer worries about a formal tone.\"\n  },\n  {\n    \"id\": \"mio\",\n    \"name\": \"Mio Vale\",\n    \"note\": \"Short call in the workshop; the writer worries it sounds too light.\"\n  },\n  {\n    \"id\": \"oru\",\n    \"name\": \"Oru Vale\",\n    \"note\": \"Open ending; the writer wants the final repair scene to feel calm.\"\n  }\n]",
          "help": [
            "2–12 objects with exactly id/name/note. IDs are unique ASCII-letter-led identifiers ≤40; name is a single line ≤120, note ≤400. Repeated display names remain separate candidates. Notes are your own interpretation.",
            "id/name/noteだけを持つ2〜12件。idは英字始まりの固有識別子で40以内、nameは一行120以内、noteは400以内。同じ表示名も別候補として保持。メモは作者の解釈です。"
          ],
          "maxLength": 750000
        },
        {
          "key": "scene",
          "label": [
            "Shared scene frame",
            "共通の場面の型"
          ],
          "type": "textarea",
          "default": "The clock stopped before the last chime. “{name}, can you leave one wheel unrepaired?” asked the apprentice.",
          "help": [
            "Use {name} exactly once, ≤1200 UTF-16 units. Every candidate gets the identical frame. The tool substitutes literal text; it does not generate dialogue or predict a reader reaction.",
            "{name}を一度だけ、全体1200 UTF-16単位以内で指定。全候補へ同じ型を使います。文字列を代入するだけで、台詞生成や読者の反応予測ではありません。"
          ],
          "maxLength": 1200
        },
        {
          "key": "context",
          "label": [
            "What this decision must serve",
            "この選択で重視すること"
          ],
          "type": "textarea",
          "default": "A clock repairer learns to leave space for another person’s choice. Compare the apprentice’s spoken address in the final scene.",
          "help": [
            "Nonblank, ≤300. Changing this context stales previous comparisons and the final selection. This is one author’s decision scope, not a pooled audience study.",
            "空でない300以内の文脈。変更すると以前の比較と最終選択は古い判断になります。一人の作者の選択範囲で、読者調査の集計ではありません。"
          ],
          "maxLength": 300
        },
        {
          "key": "judgments",
          "label": [
            "Recorded pair judgments · JSON",
            "組ごとの保存判断・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Use the pair controls to prefer either candidate, tie or defer with a reason. Each decision binds its two candidate records, scene and context. No transitive decision fills a missing pair.",
            "比較欄から片方優先、同程度、保留を理由付きで指定。判断は二候補、場面、文脈に結び付きます。推移によって未比較を埋めません。"
          ],
          "maxLength": 750000
        },
        {
          "key": "selection",
          "label": [
            "Explicit naming selection · JSON",
            "明示した名前の選択・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Choose a candidate and explain the tradeoff after reviewing the board. The choice binds all candidate and comparison records; later edits require a fresh decision. A cycle does not prevent a reasoned author choice.",
            "全体を確認して候補と取捨の理由を選択。全候補と比較記録に結び付くため、後の編集には再判断が必要です。循環があっても作者の選択は可能です。"
          ],
          "maxLength": 750000
        },
        {
          "key": "trial",
          "label": [
            "Uncommitted what-if · JSON",
            "未確定の仮の比較・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Use the what-if controls to replace one comparison only in a separate preview. It never writes a real judgment, changes the explicit selection or enters the complete decision memo.",
            "仮の比較欄で一組だけ変え、別の試案として表示。実判断、明示した選択、完成決定メモへ書き込みません。"
          ],
          "maxLength": 750000
        }
      ]
    },
    {
      "id": "nw-supporting-character-name-assignment",
      "slug": "supporting-character-name-assignment",
      "name": "Supporting character name assignment",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/supporting-character-name-assignment/",
        "ja": "/ja/tools/supporting-character-name-assignment/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Allocate names by scene exposure without eclipsing the lead",
      "task": "Assign a supplied name pool jointly to an authored cast under eligibility, locks and scene-collision constraints.",
      "searchIntent": {
        "primary": "Complete the task: Allocate names by scene exposure without eclipsing the lead",
        "queryHypothesis": "supporting character name assignment",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to allocate names by scene exposure without eclipsing the lead?",
        "When should supporting character name assignment be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "roles",
          "use": "Stable role IDs, display labels, editorial priority and optional locked candidate ID."
        },
        {
          "key": "candidates",
          "use": "Stable candidate IDs, full display, dialogue form and confirmed reading."
        },
        {
          "key": "eligibility",
          "use": "Explicit allowed or forbidden role-candidate pairs."
        },
        {
          "key": "scenes",
          "use": "Role pairs that must not share supplied short or reading forms."
        },
        {
          "key": "searchLimit",
          "use": "Fixed bounded search ceiling disclosed with explored-node count, not an unlimited guarantee."
        }
      ],
      "rules": [
        "Candidate IDs are allocated at most once; locks consume the same pool as free roles.",
        "Validate missing IDs, conflicting locks and empty role domains before search.",
        "Normalize only comparisons with a disclosed rule; retain original candidate displays.",
        "Use deterministic most-constrained-role search, with editorial priority only as a tie-break.",
        "Check scene-specific exact short/approved-reading collisions during allocation.",
        "Return partial assignments as partial, and distinguish exhausted search from a limit reached.",
        "Do not infer genre fit, gender, social class or whether a name eclipses the protagonist."
      ],
      "requiredData": [
        {
          "description": "Author-supplied cast roles and candidate pool",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Explicit eligibility and shared-scene restrictions; no external popularity scoring",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Candidate IDs are allocated at most once; locks consume the same pool as free roles.",
        "Validate missing IDs, conflicting locks and empty role domains before search.",
        "Normalize only comparisons with a disclosed rule; retain original candidate displays.",
        "Use deterministic most-constrained-role search, with editorial priority only as a tie-break.",
        "Check scene-specific exact short/approved-reading collisions during allocation.",
        "Return partial assignments as partial, and distinguish exhausted search from a limit reached.",
        "Do not infer genre fit, gender, social class or whether a name eclipses the protagonist."
      ],
      "outputs": [
        "Identity-to-candidate assignment with original forms",
        "Unfilled roles, eligibility reasons and lock trace",
        "Search status, explored nodes and bounded failure explanation"
      ],
      "capabilities": [
        "Repair a greedy dead end by backtracking instead of quietly reusing a name.",
        "Show how a fixed casting decision constrains other roles without inventing taste scores."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The user needs one feasible joint allocation, not another list or a diagnosis of an existing cast. A choice for one role consumes a candidate and can make other roles impossible.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "ensemble-name-separation",
          "difference": "Ensemble audits already assigned names; this solver searches a coupled assignment problem and returns a complete allocation, a bounded partial result or a traceable contradiction."
        }
      },
      "nearestTools": [
        {
          "id": "nw-mage-council-title-assignment",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Assign a supplied name pool jointly to an authored cast under eligibility, locks and scene-collision constraints. versus Model offices and personal names under a declared constitution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-quest-marker-name-labels",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Assign a supplied name pool jointly to an authored cast under eligibility, locks and scene-collision constraints. versus Preserve discovered identity under map space constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-brief",
          "score": 0.07647058823529412,
          "sharedProfile": false,
          "difference": "Assign a supplied name pool jointly to an authored cast under eligibility, locks and scene-collision constraints. versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Allocate the cast together because the last available name is a consequence of earlier choices.",
        "outline": [
          "Draw role domains before judging candidates",
          "A greedy allocation can strand the last role",
          "Fictional scene: a rehearsal roster and two fixed credits",
          "Compare a complete solution with an honest partial assignment",
          "Keep suitability judgments outside feasibility"
        ],
        "story": "A small comic production assigns three established credits to three speaking roles. A hurried first choice leaves the last role without an eligible form. Swapping the first two allocations solves the constraint without inventing a fourth person.",
        "storyAnalysis": "Changing one lock can make the joint plan impossible. Explain why an individually attractive choice differs from a feasible cast allocation.",
        "evidence": "Original finite constraint fixtures; no claim of reader study or artistic-quality optimization.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/assignment.md",
        "localizedBodies": {
          "en": "content/en/assignment.md",
          "ja": "content/ja/assignment.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A fixture where greedy allocation fails but a feasible swapped assignment exists is solved.",
        "Two roles cannot lock the same candidate.",
        "A forbidden scene pair changes the feasible result.",
        "An exhausted finite case is distinguished from a node-limit case.",
        "Export preserves IDs, input scope and whether the allocation is complete."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:4",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-02",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "assignment",
        "engineFiles": [
          "web/cast-assignment.mjs",
          "web/assignment-worker.mjs",
          "web/assignment-client.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/assignment.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "roles",
          "label": [
            "Roles and locks",
            "役割と固定"
          ],
          "type": "textarea",
          "default": "lead | Lead courier | 0 |\nguest | Guest witness | 1 |\nclerk | Registry clerk | 2 |",
          "help": [
            "Role ID | role label | numeric priority, lower first | locked candidate ID, optional. Priority breaks search ties; it is not an artistic score.",
            "役割ID | ラベル | 数値の優先順位・小さい値が先 | 固定する候補ID・任意。優先順位は探索の同順位を解決し、芸術的な点数ではありません。"
          ]
        },
        {
          "key": "candidates",
          "label": [
            "Supplied candidate pool",
            "入力する候補集"
          ],
          "type": "textarea",
          "default": "n1 | Aven Reed | Ave | ay-ven\nn2 | Sela Morrow | Sela | seh-la\nn3 | Orin Vale | Ori | or-in\nn4 | Arden Rowe | Ave | ar-den",
          "help": [
            "Candidate ID | exact display | dialogue short form, optional | approved reading, optional. Original displays are preserved.",
            "候補ID | 正確な表記 | 会話の短称・任意 | 確認した読み・任意。元の表記を保持します。"
          ]
        },
        {
          "key": "eligibility",
          "label": [
            "Role-specific eligibility",
            "役割ごとの適用範囲"
          ],
          "type": "textarea",
          "default": "lead | n1 | allow\nlead | n2 | allow\nguest | n1 | allow\nclerk | n3 | allow\nclerk | n4 | allow",
          "help": [
            "Role ID | candidate ID | allow/block. If a role has any allow rows, only those candidates are eligible; block removes a pair. A pair can be declared only once.",
            "役割ID | 候補ID | allow/block。allowがあればその候補だけ、blockは組合せを除外。同じ組合せは一度だけ。"
          ]
        },
        {
          "key": "scenes",
          "label": [
            "Scene pair restrictions",
            "同時登場する組の制約"
          ],
          "type": "textarea",
          "default": "lead | guest | both\nguest | clerk | short",
          "help": [
            "Role ID | other role ID | short/reading/both. Exact normalized collisions in supplied forms are blocked; unknown readings are not guessed.",
            "役割ID | 別の役割ID | short/reading/both。入力した表記の正規化後の一致を避けます。不明な読みは推測しません。"
          ]
        },
        {
          "key": "nodeLimit",
          "label": [
            "Candidate-attempt limit · 1–10,000",
            "候補試行の上限・1〜10,000"
          ],
          "type": "number",
          "default": 2000,
          "help": null
        }
      ]
    },
    {
      "id": "nw-unreliable-narrator-naming",
      "slug": "unreliable-narrator-naming",
      "name": "Unreliable narrator naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/unreliable-narrator-naming/",
        "ja": "/ja/tools/unreliable-narrator-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Separate self presentation from externally documented identity",
      "task": "Separate self presentation from externally documented identity",
      "searchIntent": {
        "primary": "Complete the task: Separate self presentation from externally documented identity",
        "queryHypothesis": "unreliable narrator naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate self presentation from externally documented identity?",
        "When should unreliable narrator naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate self presentation from externally documented identity",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate self presentation from externally documented identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Separate self presentation from externally documented identity versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unreliable-name-attribution",
          "score": 0.18888888888888888,
          "sharedProfile": false,
          "difference": "Separate self presentation from externally documented identity versus Separate a narrator's claim from corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-names-as-citizenship",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Separate self presentation from externally documented identity versus Separate state assigned recognition from self identity in a fictional regime; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate self presentation from externally documented identity",
        "outline": [
          "Explain the specific decision: Separate self presentation from externally documented identity",
          "Define the applicable contract and limits for Unreliable narrator naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate self presentation from externally documented identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate self presentation from externally documented identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:5",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-unnamed-narrator-decision",
      "slug": "unnamed-narrator-decision",
      "name": "Unnamed narrator decision",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/unnamed-narrator-decision/",
        "ja": "/ja/tools/unnamed-narrator-decision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Compare pronoun only narration against staged name disclosure",
      "task": "Compare pronoun only narration against staged name disclosure",
      "searchIntent": {
        "primary": "Complete the task: Compare pronoun only narration against staged name disclosure",
        "queryHypothesis": "unnamed narrator decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare pronoun only narration against staged name disclosure?",
        "When should unnamed narrator decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare pronoun only narration against staged name disclosure",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare pronoun only narration against staged name disclosure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Compare pronoun only narration against staged name disclosure versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare pronoun only narration against staged name disclosure versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-list-spoiler-test",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare pronoun only narration against staged name disclosure versus Compare cast list entries against mystery disclosure timing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare pronoun only narration against staged name disclosure",
        "outline": [
          "Explain the specific decision: Compare pronoun only narration against staged name disclosure",
          "Define the applicable contract and limits for Unnamed narrator decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare pronoun only narration against staged name disclosure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare pronoun only narration against staged name disclosure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:6",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-surname-construction",
      "slug": "character-surname-construction",
      "name": "Character surname construction",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-surname-construction/",
        "ja": "/ja/tools/character-surname-construction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Build a family identifier with explicit inheritance assumptions",
      "task": "Build a family identifier with explicit inheritance assumptions",
      "searchIntent": {
        "primary": "Complete the task: Build a family identifier with explicit inheritance assumptions",
        "queryHypothesis": "character surname construction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build a family identifier with explicit inheritance assumptions?",
        "When should character surname construction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build a family identifier with explicit inheritance assumptions",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build a family identifier with explicit inheritance assumptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-surname-inheritance",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Build a family identifier with explicit inheritance assumptions versus Model family transmission independently of given name generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-maiden-surname-reveal-fiction",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Build a family identifier with explicit inheritance assumptions versus Track documentary access and relationship knowledge without legal assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Build a family identifier with explicit inheritance assumptions versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build a family identifier with explicit inheritance assumptions",
        "outline": [
          "Explain the specific decision: Build a family identifier with explicit inheritance assumptions",
          "Define the applicable contract and limits for Character surname construction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build a family identifier with explicit inheritance assumptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build a family identifier with explicit inheritance assumptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:7",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-given-name-surname-fit",
      "slug": "given-name-surname-fit",
      "name": "Given name surname fit",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/given-name-surname-fit/",
        "ja": "/ja/tools/given-name-surname-fit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Repair an existing full name without replacing its fixed component",
      "task": "Repair an existing full name without replacing its fixed component",
      "searchIntent": {
        "primary": "Complete the task: Repair an existing full name without replacing its fixed component",
        "queryHypothesis": "given name surname fit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to repair an existing full name without replacing its fixed component?",
        "When should given name surname fit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Repair an existing full name without replacing its fixed component",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Repair an existing full name without replacing its fixed component. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-given-name-boundary",
          "score": 0.19,
          "sharedProfile": false,
          "difference": "Repair an existing full name without replacing its fixed component versus Prevent full name segmentation errors in a cast sheet; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shipboard-rank-reference",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Repair an existing full name without replacing its fixed component versus Handle promotions without replacing personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-downtime-household-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Repair an existing full name without replacing its fixed component versus Extend a household without replacing established members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Repair an existing full name without replacing its fixed component",
        "outline": [
          "Explain the specific decision: Repair an existing full name without replacing its fixed component",
          "Define the applicable contract and limits for Given name surname fit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Repair an existing full name without replacing its fixed component; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Repair an existing full name without replacing its fixed component",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:8",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-middle-name-use",
      "slug": "character-middle-name-use",
      "name": "Character middle name use",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-middle-name-use/",
        "ja": "/ja/tools/character-middle-name-use/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Decide where a middle name matters in dialogue and records",
      "task": "Decide where a middle name matters in dialogue and records",
      "searchIntent": {
        "primary": "Complete the task: Decide where a middle name matters in dialogue and records",
        "queryHypothesis": "character middle name use",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide where a middle name matters in dialogue and records?",
        "When should character middle name use be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide where a middle name matters in dialogue and records",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide where a middle name matters in dialogue and records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide where a middle name matters in dialogue and records versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-divorce-name-continuity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide where a middle name matters in dialogue and records versus Maintain records and dialogue references before and after separation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide where a middle name matters in dialogue and records versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide where a middle name matters in dialogue and records",
        "outline": [
          "Explain the specific decision: Decide where a middle name matters in dialogue and records",
          "Define the applicable contract and limits for Character middle name use",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide where a middle name matters in dialogue and records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide where a middle name matters in dialogue and records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:9",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-mononym-character-design",
      "slug": "mononym-character-design",
      "name": "Mononym character design",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/mononym-character-design/",
        "ja": "/ja/tools/mononym-character-design/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Maintain referential clarity for a character with one public name",
      "task": "Maintain referential clarity for a character with one public name",
      "searchIntent": {
        "primary": "Complete the task: Maintain referential clarity for a character with one public name",
        "queryHypothesis": "mononym character design",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain referential clarity for a character with one public name?",
        "When should mononym character design be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain referential clarity for a character with one public name",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain referential clarity for a character with one public name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-unspoken-name-scene",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Maintain referential clarity for a character with one public name versus Keep a name off the page while preserving referential clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-off-panel-name-reference",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Maintain referential clarity for a character with one public name versus Maintain clarity when a speaker or listener is unseen; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-military-callsign-design",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Maintain referential clarity for a character with one public name versus Derive fictional callsigns from unit practice and character history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain referential clarity for a character with one public name",
        "outline": [
          "Explain the specific decision: Maintain referential clarity for a character with one public name",
          "Define the applicable contract and limits for Mononym character design",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain referential clarity for a character with one public name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain referential clarity for a character with one public name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:10",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-inherited-name-burden",
      "slug": "inherited-name-burden",
      "name": "Inherited name burden",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/inherited-name-burden/",
        "ja": "/ja/tools/inherited-name-burden/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Track a namesake relationship and the character's response to it",
      "task": "Track a namesake relationship and the character's response to it",
      "searchIntent": {
        "primary": "Complete the task: Track a namesake relationship and the character's response to it",
        "queryHypothesis": "inherited name burden",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track a namesake relationship and the character's response to it?",
        "When should inherited name burden be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track a namesake relationship and the character's response to it",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track a namesake relationship and the character's response to it. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-inherited-secret-name",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track a namesake relationship and the character's response to it versus Track knowledge transfer and failures across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track a namesake relationship and the character's response to it versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-pen-name-fiction",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track a namesake relationship and the character's response to it versus Track multiple fictional holders of a famous author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track a namesake relationship and the character's response to it",
        "outline": [
          "Explain the specific decision: Track a namesake relationship and the character's response to it",
          "Define the applicable contract and limits for Inherited name burden",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track a namesake relationship and the character's response to it; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track a namesake relationship and the character's response to it",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:11",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-self-chosen-character-name",
      "slug": "self-chosen-character-name",
      "name": "Self chosen character name",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/self-chosen-character-name/",
        "ja": "/ja/tools/self-chosen-character-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Design a chosen identity with consent and viewpoint boundaries",
      "task": "Design a chosen identity with consent and viewpoint boundaries",
      "searchIntent": {
        "primary": "Complete the task: Design a chosen identity with consent and viewpoint boundaries",
        "queryHypothesis": "self chosen character name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a chosen identity with consent and viewpoint boundaries?",
        "When should self chosen character name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a chosen identity with consent and viewpoint boundaries",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a chosen identity with consent and viewpoint boundaries. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Design a chosen identity with consent and viewpoint boundaries versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Design a chosen identity with consent and viewpoint boundaries versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-amnesiac-placeholder-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Design a chosen identity with consent and viewpoint boundaries versus Transition from assigned label to recovered or chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a chosen identity with consent and viewpoint boundaries",
        "outline": [
          "Explain the specific decision: Design a chosen identity with consent and viewpoint boundaries",
          "Define the applicable contract and limits for Self chosen character name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a chosen identity with consent and viewpoint boundaries; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a chosen identity with consent and viewpoint boundaries",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:12",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-pronunciation-brief",
      "slug": "character-name-pronunciation-brief",
      "name": "Character name pronunciation brief",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-pronunciation-brief/",
        "ja": "/ja/tools/character-name-pronunciation-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Supply author approved pronunciations without invented etymology",
      "task": "Supply author approved pronunciations without invented etymology",
      "searchIntent": {
        "primary": "Complete the task: Supply author approved pronunciations without invented etymology",
        "queryHypothesis": "character name pronunciation brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to supply author approved pronunciations without invented etymology?",
        "When should character name pronunciation brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Supply author approved pronunciations without invented etymology",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Supply author approved pronunciations without invented etymology. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-screen-reader-brief",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Supply author approved pronunciations without invented etymology versus Provide author approved reading without relying on glyph guessing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.17575757575757575,
          "sharedProfile": false,
          "difference": "Supply author approved pronunciations without invented etymology versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-naming-brief",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Supply author approved pronunciations without invented etymology versus Convert a role, setting and narrative distance into a testable name brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Supply author approved pronunciations without invented etymology",
        "outline": [
          "Explain the specific decision: Supply author approved pronunciations without invented etymology",
          "Define the applicable contract and limits for Character name pronunciation brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Supply author approved pronunciations without invented etymology; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Supply author approved pronunciations without invented etymology",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:13",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-dossier-name-system",
      "slug": "character-dossier-name-system",
      "name": "Character dossier name system",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-dossier-name-system/",
        "ja": "/ja/tools/character-dossier-name-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Reconcile names across documents, dialogue and narration",
      "task": "Reconcile names across documents, dialogue and narration",
      "searchIntent": {
        "primary": "Complete the task: Reconcile names across documents, dialogue and narration",
        "queryHypothesis": "character dossier name system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile names across documents, dialogue and narration?",
        "When should character dossier name system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile names across documents, dialogue and narration",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile names across documents, dialogue and narration. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile names across documents, dialogue and narration versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-order-policy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile names across documents, dialogue and narration versus Keep display order consistent across narration and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-cue-name-system",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Reconcile names across documents, dialogue and narration versus Keep production cues distinct from spoken identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile names across documents, dialogue and narration",
        "outline": [
          "Explain the specific decision: Reconcile names across documents, dialogue and narration",
          "Define the applicable contract and limits for Character dossier name system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile names across documents, dialogue and narration; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile names across documents, dialogue and narration",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:15",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-replacement",
      "slug": "character-name-replacement",
      "name": "Character name replacement",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-replacement/",
        "ja": "/ja/tools/character-name-replacement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Replace one established name while preserving story dependencies",
      "task": "Replace one established name while preserving story dependencies",
      "searchIntent": {
        "primary": "Complete the task: Replace one established name while preserving story dependencies",
        "queryHypothesis": "character name replacement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to replace one established name while preserving story dependencies?",
        "When should character name replacement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "identityId",
          "use": "Select a confirmed character rather than every matching word."
        },
        {
          "key": "occurrences",
          "use": "Link names to scenes, props, clues and quotations."
        },
        {
          "key": "newForms",
          "use": "Supply a replacement mapping and locked exceptions."
        }
      ],
      "rules": [
        "Preview occurrence-scoped edits before commitment.",
        "Keep quoted document errors when explicitly intentional.",
        "Invalidate initials, anagrams and other dependent clues.",
        "Maintain prior forms in an edit ledger for undo."
      ],
      "requiredData": [
        {
          "description": "Author-confirmed occurrence map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Clue dependencies and locked quotations",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Preview occurrence-scoped edits before commitment.",
        "Keep quoted document errors when explicitly intentional.",
        "Invalidate initials, anagrams and other dependent clues.",
        "Maintain prior forms in an edit ledger for undo."
      ],
      "outputs": [
        "Proposed edit patch",
        "Dependent creative work list",
        "Reversible before-after mapping"
      ],
      "capabilities": [
        "Show non-text dependencies that a rename breaks.",
        "Undo a rename without overwriting unrelated subsequent decisions."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Replace an established identity with a reversible dependency-aware patch, rather than produce fresh suggestions detached from the manuscript.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "manuscript-global-replace-safety",
          "difference": "A character-level decision plan traces clues and relationships; generic text replacement only edits matching strings."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Replace one established name while preserving story dependencies versus Remove overdetermined motifs while preserving relevant story function; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Replace one established name while preserving story dependencies versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wrong-honorific-clue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Replace one established name while preserving story dependencies versus Ground the clue in an established in story convention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A rename is an editorial migration, not a find-and-replace command.",
        "outline": [
          "Confirm identity before matching text",
          "Audit props and puzzles",
          "Preview a scoped patch",
          "Restore a previous decision safely"
        ],
        "story": "Fictional example: changing a suspect's surname breaks a visible monogram on a suitcase. The editor repairs the clue or chooses a different replacement rather than leave the old evidence unexplained.",
        "storyAnalysis": "Compare a string-only replacement with a dependency-aware patch and enumerate the changed reader deductions.",
        "evidence": "Original occurrence and monogram fixtures; no manuscript parsing accuracy claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/rename.md",
        "localizedBodies": {
          "en": "content/en/rename.md",
          "ja": "content/ja/rename.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A different person with the same string is not replaced.",
        "A dependent initials clue becomes unresolved.",
        "A locked quotation remains unchanged.",
        "Undo restores only the recorded affected fields."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:16",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-01",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "rename",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/editorial-engines.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/editorial.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "identityId",
          "label": [
            "Character ID to rename",
            "改名する人物ID"
          ],
          "type": "text",
          "default": "a",
          "help": null
        },
        {
          "key": "mode",
          "label": [
            "Operation",
            "操作"
          ],
          "type": "select",
          "default": "preview",
          "help": null,
          "options": [
            [
              "preview",
              [
                "Preview rename",
                "改名案を確認"
              ]
            ],
            [
              "undo",
              [
                "Guarded undo preview",
                "条件付きの復元案"
              ]
            ]
          ]
        },
        {
          "key": "occurrences",
          "label": [
            "Confirmed occurrence ledger",
            "確認済みの使用箇所"
          ],
          "type": "textarea",
          "default": "o1 | a | full | Aven Reed | replace | Chapter 2 dialogue\no2 | a | full | Aven Reed | replace | Suitcase monogram artwork\no3 | b | full | Aven Reed | replace | Another person in Chapter 3\no4 | a | full | Aven Reed | lock | Quoted old document",
          "help": [
            "Occurrence ID | person ID | form key | exact current text | replace/lock | scene or asset. This tool does not discover occurrences in a manuscript.",
            "使用箇所ID | 人物ID | 表記キー | 現在の文字列 | replace/lock | 場面または素材。原稿から使用箇所を自動抽出しません。"
          ]
        },
        {
          "key": "newForms",
          "label": [
            "Replacement forms",
            "表記の対応"
          ],
          "type": "textarea",
          "default": "full | Aven Reed | Aven Vale",
          "help": [
            "Form key | exact old form | proposed new form. Each key once.",
            "表記キー | 完全一致する旧表記 | 新表記。キーは一度だけ。"
          ]
        },
        {
          "key": "dependencies",
          "label": [
            "Clues and production dependencies",
            "手掛かりと制作の依存関係"
          ],
          "type": "textarea",
          "default": "clue-1 | o2 | initials | AR | Redesign suitcase monogram before approval",
          "help": [
            "Dependency ID | occurrence ID | initials/anagram/text/manual | recorded requirement | repair note, optional. A note does not approve a repair.",
            "依存ID | 使用箇所ID | initials/anagram/text/manual | 記録した条件 | 修正メモ・任意。メモは修正の承認ではありません。"
          ]
        },
        {
          "key": "patch",
          "label": [
            "Exported patch for undo · JSON",
            "復元するパッチ・JSON"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "For undo, paste the downloaded reversible patch and supply the current occurrence ledger. Changed or locked occurrences are preserved.",
            "復元には書き出したパッチと現在の使用箇所を入力。後で変えた箇所と固定した箇所は保持します。"
          ]
        }
      ]
    },
    {
      "id": "nw-character-name-motif-restraint",
      "slug": "character-name-motif-restraint",
      "name": "Character name motif restraint",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-motif-restraint/",
        "ja": "/ja/tools/character-name-motif-restraint/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Limit symbolic signals so a name does not announce the plot",
      "task": "Limit symbolic signals so a name does not announce the plot",
      "searchIntent": {
        "primary": "Complete the task: Limit symbolic signals so a name does not announce the plot",
        "queryHypothesis": "character name motif restraint",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to limit symbolic signals so a name does not announce the plot?",
        "When should character name motif restraint be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Limit symbolic signals so a name does not announce the plot",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Limit symbolic signals so a name does not announce the plot. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-prophetic-name-restraint",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Limit symbolic signals so a name does not announce the plot versus Design an ambiguous epithet without making prophecy self proving; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-names-without-surnames",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Limit symbolic signals so a name does not announce the plot versus Design a reference system that does not assume family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Limit symbolic signals so a name does not announce the plot versus Remove overdetermined motifs while preserving relevant story function; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Limit symbolic signals so a name does not announce the plot",
        "outline": [
          "Explain the specific decision: Limit symbolic signals so a name does not announce the plot",
          "Define the applicable contract and limits for Character name motif restraint",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Limit symbolic signals so a name does not announce the plot; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Limit symbolic signals so a name does not announce the plot",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:17",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-memorability-test",
      "slug": "character-name-memorability-test",
      "name": "Character name memorability test",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-memorability-test/",
        "ja": "/ja/tools/character-name-memorability-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Build a recall exercise against a supplied cast",
      "task": "Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate.",
      "searchIntent": {
        "primary": "Complete the task: Build a recall exercise against a supplied cast",
        "queryHypothesis": "character name memorability test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build a recall exercise against a supplied cast?",
        "When should character name memorability test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "stimuli",
          "use": "Candidate IDs and exact author-approved spellings, not explanations shown beside them."
        },
        {
          "key": "protocol",
          "use": "Exposure material, stated delay and permitted answer normalization."
        },
        {
          "key": "responses",
          "use": "Participant token, candidate ID, response, completed/omitted/not-tested state."
        },
        {
          "key": "conditions",
          "use": "Versioned condition IDs; conditions cannot silently be pooled."
        }
      ],
      "rules": [
        "Never create participants, responses or measured delays.",
        "Separate not-tested from an observed blank response.",
        "Use a disclosed exact or normalized string comparison only; no inferred recognition.",
        "Report per-item numerators and actual observed denominators, with raw rows available.",
        "Block duplicate participant-item-condition keys.",
        "Do not infer generalizability, causation, cultural quality or population confidence from a convenience sample.",
        "Exposure exports omit answer explanations; analysis export contains answer keys and is labeled separately."
      ],
      "requiredData": [
        {
          "description": "User-entered anonymous observations",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Authored protocol and spelling normalization policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Never create participants, responses or measured delays.",
        "Separate not-tested from an observed blank response.",
        "Use a disclosed exact or normalized string comparison only; no inferred recognition.",
        "Report per-item numerators and actual observed denominators, with raw rows available.",
        "Block duplicate participant-item-condition keys.",
        "Do not infer generalizability, causation, cultural quality or population confidence from a convenience sample.",
        "Exposure exports omit answer explanations; analysis export contains answer keys and is labeled separately."
      ],
      "outputs": [
        "Exposure and response sheets",
        "Per-item exact-match counts with missing-state accounting",
        "Protocol deviations and condition-specific observations"
      ],
      "capabilities": [
        "Recompute actual denominators when a response changes from not-tested to an observed omission.",
        "Keep blind exposure separate from the author analysis key."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The task collects actual response observations and checks a study protocol; generating names or exporting a blind worksheet cannot calculate recall from absent responses.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "pen-name-designer",
          "difference": "Pen design supplies a worksheet; this tool preserves exposure conditions, anonymous participant rows, item-level exact responses, omissions and actual denominators."
        }
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.128125,
          "sharedProfile": false,
          "difference": "Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate. versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-cast-recognition-test",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate. versus Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-possession-naming-test",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate. versus State what a name test can and cannot establish in the fictional rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A recall figure is a summary of recorded answers under stated conditions, not a name-quality score.",
        "outline": [
          "Write the protocol before looking at answers",
          "Separate exposure from the key",
          "Fictional scene: two readers and one forgotten surname",
          "Missing observation is not failure",
          "Explain the result without promising a memorable name"
        ],
        "story": "A writer gives two volunteer readers the same short scene and later asks for names without showing the roster. One reader was interrupted and never completed the exercise. Counting that person as a failed recall changes the denominator and misrepresents what happened.",
        "storyAnalysis": "Changing the name may not change recall if the scene gave one character much more exposure. Compare actual protocol limitations rather than invent a winner.",
        "evidence": "Original protocol fixtures; no real participants or experimental results asserted.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/recall.md",
        "localizedBodies": {
          "en": "content/en/recall.md",
          "ja": "content/ja/recall.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "No responses means no recall percentage, never a manufactured zero.",
        "An observed omission counts in its stated denominator; not-tested does not.",
        "Duplicate observation keys fail.",
        "Changing normalization changes only the declared comparison, with raw spellings retained.",
        "A comparison across protocol conditions remains stratified."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:18",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-02",
      "absorbedModules": [
        {
          "sourceId": "nw-pen-name-spelling-recall",
          "input": "Supplied credit spellings and neutral cues; declared exposure conditions; actual completed/omitted/not-tested observations.",
          "rule": "Keep exposure and later response sheets separate; calculate exact declared spelling matches with observed denominators and preserve missing states and protocol deviations.",
          "output": "Condition/item recall cells, raw-answer analysis and a target-free blank response sheet. No quality score, real participants or cover appearance is invented.",
          "acceptance": "With no observations rate remains unknown; an omission and not-tested produce different denominators; normalization preserves raw answers; response export omits target strings.",
          "evidence": [
            "RECALL-01",
            "RECALL-02",
            "RECALL-03",
            "RECALL-04",
            "RECALL-06",
            "reports/recall-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-pen-name-byline-recall-test",
          "input": "Supplied credit spellings and neutral cues; declared exposure conditions; actual completed/omitted/not-tested observations.",
          "rule": "Keep exposure and later response sheets separate; calculate exact declared spelling matches with observed denominators and preserve missing states and protocol deviations.",
          "output": "Condition/item recall cells, raw-answer analysis and a target-free blank response sheet. No quality score, real participants or cover appearance is invented.",
          "acceptance": "With no observations rate remains unknown; an omission and not-tested produce different denominators; normalization preserves raw answers; response export omits target strings.",
          "evidence": [
            "RECALL-01",
            "RECALL-02",
            "RECALL-03",
            "RECALL-04",
            "RECALL-06",
            "reports/recall-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "recall",
        "engineFiles": [
          "web/recall-ledger.mjs",
          "web/recall-ui.js",
          "scripts/render-recall-capture.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/recall.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "stimuli",
          "label": [
            "Names and neutral recall cues",
            "名前と回答用の中立的な手掛かり"
          ],
          "type": "textarea",
          "default": "courier | Sela Morrow | Courier at the ferry desk\nclerk | Aven Reed | Registry clerk by the window\nwitness | Orin Vale | Witness holding a blue folder",
          "help": [
            "Item ID | target spelling | cue. 1–40 items. Cues will appear on the blank response sheet; check that they do not reveal the answer.",
            "項目ID | 目標の表記 | 手掛かり。1〜40項目。手掛かりは回答用シートに出るため、答えを明かさないか確認してください。"
          ]
        },
        {
          "key": "conditions",
          "label": [
            "Separate test conditions",
            "分けて扱うテスト条件"
          ],
          "type": "textarea",
          "default": "c1 | Five-second exposure, one-minute delay | 5 | 60\nc2 | Ten-second exposure, one-minute delay | 10 | 60",
          "help": [
            "Condition ID | authored description | planned exposure seconds | planned delay seconds. Blank time stays unknown. 1–8 conditions; no pooled winner.",
            "条件ID | 作者の説明 | 計画した提示秒数 | 計画した遅延秒数。時間の空欄は不明。1〜8条件。まとめた勝者は出しません。"
          ]
        },
        {
          "key": "matchPolicy",
          "label": [
            "Spelling comparison policy",
            "表記の比較方法"
          ],
          "type": "select",
          "default": "exact",
          "help": null,
          "options": [
            [
              "exact",
              [
                "Exact raw string",
                "元の文字列の完全一致"
              ]
            ],
            [
              "nfc-trim",
              [
                "NFC + trim surrounding whitespace",
                "NFCと前後空白除去"
              ]
            ],
            [
              "nfc-trim-lower",
              [
                "NFC + trim + lowercase",
                "NFC・前後空白除去・小文字化"
              ]
            ]
          ]
        },
        {
          "key": "inclusionPolicy",
          "label": [
            "Observation inclusion policy",
            "観察を分母に含める方針"
          ],
          "type": "select",
          "default": "all-observed",
          "help": null,
          "options": [
            [
              "all-observed",
              [
                "All observed responses, deviations flagged",
                "観察した全回答・条件ずれを表示"
              ]
            ],
            [
              "protocol-matched",
              [
                "Only matching reported exposure and delay",
                "報告した提示・遅延時間が一致した回答のみ"
              ]
            ]
          ]
        },
        {
          "key": "observations",
          "label": [
            "Actual anonymous observations · JSON",
            "実際の匿名の観察・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "JSON array, max 500. Fields: participant, condition, item, state (completed/omitted/not-tested), response, optional numeric exposureSeconds/delaySeconds and note. Preserve raw answers. Empty means no observations; no sample participants are invented.",
            "最大500件のJSON配列。participant、condition、item、state（completed/omitted/not-tested）、response、任意の数値exposureSeconds/delaySecondsとnote。元回答を保持。空配列は観察なしで、架空の参加者は作りません。"
          ],
          "maxLength": 180000
        }
      ]
    },
    {
      "id": "nw-character-name-ambiguity-budget",
      "slug": "character-name-ambiguity-budget",
      "name": "Character name ambiguity budget",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-ambiguity-budget/",
        "ja": "/ja/tools/character-name-ambiguity-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Decide which confusions are intentional and which need repair",
      "task": "Decide which confusions are intentional and which need repair",
      "searchIntent": {
        "primary": "Complete the task: Decide which confusions are intentional and which need repair",
        "queryHypothesis": "character name ambiguity budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide which confusions are intentional and which need repair?",
        "When should character name ambiguity budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide which confusions are intentional and which need repair",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide which confusions are intentional and which need repair. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-ambiguity-budget",
          "score": 0.2924242424242424,
          "sharedProfile": false,
          "difference": "Decide which confusions are intentional and which need repair versus Track newly introduced collisions and intentional ambiguity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-crowd-reference-plan",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Decide which confusions are intentional and which need repair versus Decide which background figures need a name at all; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide which confusions are intentional and which need repair versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide which confusions are intentional and which need repair",
        "outline": [
          "Explain the specific decision: Decide which confusions are intentional and which need repair",
          "Define the applicable contract and limits for Character name ambiguity budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide which confusions are intentional and which need repair; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide which confusions are intentional and which need repair",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:19",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-age-cohort-naming",
      "slug": "character-age-cohort-naming",
      "name": "Character age cohort naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-age-cohort-naming/",
        "ja": "/ja/tools/character-age-cohort-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Match fictional birth timing to sourced cohort data",
      "task": "Match fictional birth timing to sourced cohort data",
      "searchIntent": {
        "primary": "Complete the task: Match fictional birth timing to sourced cohort data",
        "queryHypothesis": "character age cohort naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match fictional birth timing to sourced cohort data?",
        "When should character age cohort naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "birthWindow",
          "use": "Compute a fictional birth interval from story date and age uncertainty."
        },
        {
          "key": "locality",
          "use": "Limit evidence scope rather than infer nationality."
        },
        {
          "key": "dataset",
          "use": "Require dated counts, population coverage and permitted use."
        }
      ],
      "rules": [
        "Do not substitute present-day frequency for birth-cohort evidence.",
        "Report not covered for out-of-range dates or missing populations.",
        "Frequency is not proof of suitability for one individual.",
        "Keep age uncertainty as a range instead of rounding to one year."
      ],
      "requiredData": [
        {
          "description": "Pinned SSA annual aggregate records; manifest, raw SHA-256 and source qualifications retained.",
          "intakeStatus": "imported",
          "licenseReview": "CC0 metadata recorded"
        }
      ],
      "generationFlow": [
        "Do not substitute present-day frequency for birth-cohort evidence.",
        "Report not covered for out-of-range dates or missing populations.",
        "Frequency is not proof of suitability for one individual.",
        "Keep age uncertainty as a range instead of rounding to one year."
      ],
      "outputs": [
        "Eligible evidence window",
        "Candidate counts with denominator where available",
        "Coverage gaps and interpretation limits"
      ],
      "capabilities": [
        "Compare the same candidate across two supported birth windows.",
        "Expose how a broader age range changes evidence coverage."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Evaluate candidates against dated, geographically bounded evidence and disclose source coverage; a style toggle cannot substantiate a cohort claim.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "evaluation",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "historical-birth-cohort-shortlist",
          "difference": "Potential overlap remains open: merge unless period research genuinely needs a different evidence workflow."
        }
      },
      "nearestTools": [
        {
          "id": "nw-academy-cohort-naming",
          "score": 0.17083333333333334,
          "sharedProfile": false,
          "difference": "Match fictional birth timing to sourced cohort data versus Decide whether cohort labels belong in public personal references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-coming-of-age-chosen-name",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Match fictional birth timing to sourced cohort data versus Connect a name decision to a specific act of agency; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dragon-age-name-layers",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Match fictional birth timing to sourced cohort data versus Add earned components at authored milestones without arbitrary syllable growth; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Period plausibility depends on evidence coverage, not a vintage-sounding name.",
        "outline": [
          "Infer the birth window carefully",
          "Read the denominator and the missing populations",
          "A grandparent younger than the archive assumes",
          "Keep evidence separate from creative choice"
        ],
        "story": "Fictional example: a serial changes its calendar while retaining a character's age. A cohort check reveals that the author's selected evidence no longer covers the implied birth years.",
        "storyAnalysis": "The fix may change the timeline or research source rather than the character's name.",
        "evidence": "No frequency corpus imported; only supplied tables may support a claim. Independent-page overlap remains unresolved.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/cohort.md",
        "localizedBodies": {
          "en": "content/en/cohort.md",
          "ja": "content/ja/cohort.md"
        }
      },
      "dataSources": [
        "ssa-source",
        "ssa-license"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Unsupported year produces not covered, not zero popularity.",
        "No dataset produces no frequency claim.",
        "Negative ages are rejected.",
        "Dataset population mismatch is displayed before ranking."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:20",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-01",
      "absorbedModules": [
        {
          "sourceId": "nw-historical-birth-cohort-shortlist",
          "input": "dated source rows; candidate shortlist",
          "rule": "Keep missing or suppressed rows unknown and preserve source coverage.",
          "output": "Versioned cohort evidence brief with observed/missing years.",
          "acceptance": "Unobserved supplied spelling remains unknown, never zero.",
          "evidence": [
            "COHORT-01",
            "COHORT-02"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "cohort",
        "engineFiles": [
          "web/corpus.mjs",
          "web/next-tools.mjs",
          "web/corpus-ui.js"
        ],
        "tests": [
          "test/corpus.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "storyYear",
          "label": [
            "Story year",
            "物語の西暦"
          ],
          "type": "number",
          "default": 2020,
          "help": null
        },
        {
          "key": "minAge",
          "label": [
            "Youngest possible age",
            "考えられる最小年齢"
          ],
          "type": "number",
          "default": 40,
          "help": null
        },
        {
          "key": "maxAge",
          "label": [
            "Oldest possible age",
            "考えられる最大年齢"
          ],
          "type": "number",
          "default": 42,
          "help": null
        },
        {
          "key": "shortlist",
          "label": [
            "Existing candidates · optional",
            "すでにある候補・任意"
          ],
          "type": "textarea",
          "default": "Maya\nMira\nMary",
          "help": [
            "One name per line. Unobserved names remain visible with unknown counts. Leave empty to rank the published rows in this birth interval.",
            "1行に一つの名前。観測できない候補も件数不明のまま残します。空欄なら出生年の範囲内の公開行から候補を並べます。"
          ]
        },
        {
          "key": "prefix",
          "label": [
            "Optional spelling prefix",
            "任意の先頭文字"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "exclude",
          "label": [
            "Exclude spelling fragments",
            "除外する表記の一部"
          ],
          "type": "textarea",
          "default": "",
          "help": null
        },
        {
          "key": "count",
          "label": [
            "Maximum candidates · 1–30",
            "候補数の上限・1〜30"
          ],
          "type": "number",
          "default": 12,
          "help": null
        },
        {
          "key": "dataVersion",
          "label": [
            "Pinned SSA archive SHA-256",
            "固定したSSA資料のSHA-256"
          ],
          "type": "text",
          "default": "cd78e975ed7bb358e018dd62fbe14ced89295e9581c49172ca4eedcb011b3724",
          "help": [
            "A different version stops reproduction. Update only after reviewing the archived evidence.",
            "資料版が異なる場合は再現を止めます。保存した根拠を確認したうえで更新してください。"
          ],
          "requiredInProject": true
        }
      ],
      "availableSourceManifest": "data/corpora/manifest.json"
    },
    {
      "id": "nw-character-social-register-naming",
      "slug": "character-social-register-naming",
      "name": "Character social register naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-social-register-naming/",
        "ja": "/ja/tools/character-social-register-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Compare public formality with private address without stereotyping",
      "task": "Compare public formality with private address without stereotyping",
      "searchIntent": {
        "primary": "Complete the task: Compare public formality with private address without stereotyping",
        "queryHypothesis": "character social register naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare public formality with private address without stereotyping?",
        "When should character social register naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare public formality with private address without stereotyping",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare public formality with private address without stereotyping. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare public formality with private address without stereotyping versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-commoner-register",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Compare public formality with private address without stereotyping versus Define structural differences without equating status and virtue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare public formality with private address without stereotyping versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare public formality with private address without stereotyping",
        "outline": [
          "Explain the specific decision: Compare public formality with private address without stereotyping",
          "Define the applicable contract and limits for Character social register naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare public formality with private address without stereotyping; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare public formality with private address without stereotyping",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:21",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-migration-naming",
      "slug": "character-migration-naming",
      "name": "Character migration naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-migration-naming/",
        "ja": "/ja/tools/character-migration-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Track retained, adapted and imposed forms across a journey",
      "task": "Track retained, adapted and imposed forms across a journey",
      "searchIntent": {
        "primary": "Complete the task: Track retained, adapted and imposed forms across a journey",
        "queryHypothesis": "character migration naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track retained, adapted and imposed forms across a journey?",
        "When should character migration naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track retained, adapted and imposed forms across a journey",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track retained, adapted and imposed forms across a journey. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-localization-drift",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track retained, adapted and imposed forms across a journey versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-migration-between-towns",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Track retained, adapted and imposed forms across a journey versus Preserve individual names while updating local forms of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-abdicated-ruler-reference",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track retained, adapted and imposed forms across a journey versus Distinguish retained courtesy forms from current authority; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track retained, adapted and imposed forms across a journey",
        "outline": [
          "Explain the specific decision: Track retained, adapted and imposed forms across a journey",
          "Define the applicable contract and limits for Character migration naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track retained, adapted and imposed forms across a journey; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track retained, adapted and imposed forms across a journey",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:22",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-literacy-naming",
      "slug": "character-literacy-naming",
      "name": "Character literacy naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-literacy-naming/",
        "ja": "/ja/tools/character-literacy-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Distinguish how a character writes a name from how others record it",
      "task": "Distinguish how a character writes a name from how others record it",
      "searchIntent": {
        "primary": "Complete the task: Distinguish how a character writes a name from how others record it",
        "queryHypothesis": "character literacy naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish how a character writes a name from how others record it?",
        "When should character literacy naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish how a character writes a name from how others record it",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish how a character writes a name from how others record it. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish how a character writes a name from how others record it versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish how a character writes a name from how others record it versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish how a character writes a name from how others record it versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish how a character writes a name from how others record it",
        "outline": [
          "Explain the specific decision: Distinguish how a character writes a name from how others record it",
          "Define the applicable contract and limits for Character literacy naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish how a character writes a name from how others record it; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish how a character writes a name from how others record it",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:23",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-aversion",
      "slug": "character-name-aversion",
      "name": "Character name aversion",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-aversion/",
        "ja": "/ja/tools/character-name-aversion/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Map who avoids a name and what substitute each speaker uses",
      "task": "Map who avoids a name and what substitute each speaker uses",
      "searchIntent": {
        "primary": "Complete the task: Map who avoids a name and what substitute each speaker uses",
        "queryHypothesis": "character name aversion",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map who avoids a name and what substitute each speaker uses?",
        "When should character name aversion be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map who avoids a name and what substitute each speaker uses",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map who avoids a name and what substitute each speaker uses. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shared-campaign-naming-authority",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Map who avoids a name and what substitute each speaker uses versus Record who may introduce or revise each naming rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-betrayal",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Map who avoids a name and what substitute each speaker uses versus Map who retains or rejects earlier intimate forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-grandparent-nickname-dialogue",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Map who avoids a name and what substitute each speaker uses versus Map each child's term to a stable character identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map who avoids a name and what substitute each speaker uses",
        "outline": [
          "Explain the specific decision: Map who avoids a name and what substitute each speaker uses",
          "Define the applicable contract and limits for Character name aversion",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map who avoids a name and what substitute each speaker uses; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map who avoids a name and what substitute each speaker uses",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:24",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-mishearing",
      "slug": "character-name-mishearing",
      "name": "Character name mishearing",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-mishearing/",
        "ja": "/ja/tools/character-name-mishearing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Design recoverable mishearings that do not depend on false phonetics",
      "task": "Design recoverable mishearings that do not depend on false phonetics",
      "searchIntent": {
        "primary": "Complete the task: Design recoverable mishearings that do not depend on false phonetics",
        "queryHypothesis": "character name mishearing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design recoverable mishearings that do not depend on false phonetics?",
        "When should character name mishearing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design recoverable mishearings that do not depend on false phonetics",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design recoverable mishearings that do not depend on false phonetics. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-names-without-surnames",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Design recoverable mishearings that do not depend on false phonetics versus Design a reference system that does not assume family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-reveal-regression-test",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Design recoverable mishearings that do not depend on false phonetics versus Verify that revised names do not expose hidden identities early; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-mistaken-identity-encounter",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Design recoverable mishearings that do not depend on false phonetics versus Design fair recoverable name confusion for a live session; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design recoverable mishearings that do not depend on false phonetics",
        "outline": [
          "Explain the specific decision: Design recoverable mishearings that do not depend on false phonetics",
          "Define the applicable contract and limits for Character name mishearing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design recoverable mishearings that do not depend on false phonetics; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design recoverable mishearings that do not depend on false phonetics",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:25",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-in-letters",
      "slug": "character-name-in-letters",
      "name": "Character name in letters",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-in-letters/",
        "ja": "/ja/tools/character-name-in-letters/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Create signoffs and salutations tied to relationship distance",
      "task": "Create signoffs and salutations tied to relationship distance",
      "searchIntent": {
        "primary": "Complete the task: Create signoffs and salutations tied to relationship distance",
        "queryHypothesis": "character name in letters",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to create signoffs and salutations tied to relationship distance?",
        "When should character name in letters be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Create signoffs and salutations tied to relationship distance",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Create signoffs and salutations tied to relationship distance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-letters-versus-speech-address",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Create signoffs and salutations tied to relationship distance versus Compare written and spoken relationship registers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-title-reward",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Create signoffs and salutations tied to relationship distance versus Create earned titles tied to actual in game actions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-formal-informal-contrast",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Create signoffs and salutations tied to relationship distance versus Rebuild relationship distance through approved language choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Create signoffs and salutations tied to relationship distance",
        "outline": [
          "Explain the specific decision: Create signoffs and salutations tied to relationship distance",
          "Define the applicable contract and limits for Character name in letters",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Create signoffs and salutations tied to relationship distance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Create signoffs and salutations tied to relationship distance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:26",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-in-records",
      "slug": "character-name-in-records",
      "name": "Character name in records",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-in-records/",
        "ja": "/ja/tools/character-name-in-records/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Keep official record forms separate from narrative display",
      "task": "Keep official record forms separate from narrative display",
      "searchIntent": {
        "primary": "Complete the task: Keep official record forms separate from narrative display",
        "queryHypothesis": "character name in records",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep official record forms separate from narrative display?",
        "When should character name in records be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep official record forms separate from narrative display",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep official record forms separate from narrative display. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Keep official record forms separate from narrative display versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-border-town-name-register",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep official record forms separate from narrative display versus Map local and official forms across a fictional frontier; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-disputed-heir-name-evidence",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep official record forms separate from narrative display versus Separate claimed descent, documentary forms and narrative inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep official record forms separate from narrative display",
        "outline": [
          "Explain the specific decision: Keep official record forms separate from narrative display",
          "Define the applicable contract and limits for Character name in records",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep official record forms separate from narrative display; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep official record forms separate from narrative display",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:27",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-naming-deadline",
      "slug": "character-naming-deadline",
      "name": "Character naming deadline",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-naming-deadline/",
        "ja": "/ja/tools/character-naming-deadline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Choose among supplied candidates using explicit rejection criteria",
      "task": "Choose among supplied candidates using explicit rejection criteria",
      "searchIntent": {
        "primary": "Complete the task: Choose among supplied candidates using explicit rejection criteria",
        "queryHypothesis": "character naming deadline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to choose among supplied candidates using explicit rejection criteria?",
        "When should character naming deadline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Choose among supplied candidates using explicit rejection criteria",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Choose among supplied candidates using explicit rejection criteria. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-candidate-decision",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Choose among supplied candidates using explicit rejection criteria versus Compare a fixed shortlist using published heuristic criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-batch-review",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Choose among supplied candidates using explicit rejection criteria versus Separate generated candidates from accepted character identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-recruit-list-clarity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Choose among supplied candidates using explicit rejection criteria versus Separate candidates in compact selection menus; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Choose among supplied candidates using explicit rejection criteria",
        "outline": [
          "Explain the specific decision: Choose among supplied candidates using explicit rejection criteria",
          "Define the applicable contract and limits for Character naming deadline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Choose among supplied candidates using explicit rejection criteria; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Choose among supplied candidates using explicit rejection criteria",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:28",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-beta-reader-test",
      "slug": "character-name-beta-reader-test",
      "name": "Character name beta reader test",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-beta-reader-test/",
        "ja": "/ja/tools/character-name-beta-reader-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Generate blind comparison prompts and record reader confusion",
      "task": "Generate blind comparison prompts and record reader confusion",
      "searchIntent": {
        "primary": "Complete the task: Generate blind comparison prompts and record reader confusion",
        "queryHypothesis": "character name beta reader test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate blind comparison prompts and record reader confusion?",
        "When should character name beta reader test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate blind comparison prompts and record reader confusion",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate blind comparison prompts and record reader confusion. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-onboarding-reader-test",
          "score": 0.1990909090909091,
          "sharedProfile": false,
          "difference": "Generate blind comparison prompts and record reader confusion versus Generate recall tasks after staged introductions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.19416666666666665,
          "sharedProfile": false,
          "difference": "Generate blind comparison prompts and record reader confusion versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Generate blind comparison prompts and record reader confusion versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate blind comparison prompts and record reader confusion",
        "outline": [
          "Explain the specific decision: Generate blind comparison prompts and record reader confusion",
          "Define the applicable contract and limits for Character name beta reader test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate blind comparison prompts and record reader confusion; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate blind comparison prompts and record reader confusion",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:29",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-revision-history",
      "slug": "character-name-revision-history",
      "name": "Character name revision history",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-revision-history/",
        "ja": "/ja/tools/character-name-revision-history/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Track why a name changed and dependent scenes to revisit",
      "task": "Track why a name changed and dependent scenes to revisit",
      "searchIntent": {
        "primary": "Complete the task: Track why a name changed and dependent scenes to revisit",
        "queryHypothesis": "character name revision history",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track why a name changed and dependent scenes to revisit?",
        "When should character name revision history be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track why a name changed and dependent scenes to revisit",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track why a name changed and dependent scenes to revisit. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-rename-impact-map",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track why a name changed and dependent scenes to revisit versus List scenes, props and clues dependent on a proposed rename; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track why a name changed and dependent scenes to revisit versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-existing-pen-name-revision",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track why a name changed and dependent scenes to revisit versus Plan continuity notes and old to new credit mappings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track why a name changed and dependent scenes to revisit",
        "outline": [
          "Explain the specific decision: Track why a name changed and dependent scenes to revisit",
          "Define the applicable contract and limits for Character name revision history",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track why a name changed and dependent scenes to revisit; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track why a name changed and dependent scenes to revisit",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:30",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-evidence-ledger",
      "slug": "character-name-evidence-ledger",
      "name": "Character name evidence ledger",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-evidence-ledger/",
        "ja": "/ja/tools/character-name-evidence-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Separate verified cultural claims from author associations",
      "task": "Separate verified cultural claims from author associations",
      "searchIntent": {
        "primary": "Complete the task: Separate verified cultural claims from author associations",
        "queryHypothesis": "character name evidence ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate verified cultural claims from author associations?",
        "When should character name evidence ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate verified cultural claims from author associations",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate verified cultural claims from author associations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-claim-evidence-mapping",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Separate verified cultural claims from author associations versus Attach sources to individual readings, meanings and cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mispronunciation-character-arc",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate verified cultural claims from author associations versus Record author verified pronunciation and speaker learning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-serial-reader-correction-log",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate verified cultural claims from author associations versus Track reports as claims pending author confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate verified cultural claims from author associations",
        "outline": [
          "Explain the specific decision: Separate verified cultural claims from author associations",
          "Define the applicable contract and limits for Character name evidence ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate verified cultural claims from author associations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate verified cultural claims from author associations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:31",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-consent-map",
      "slug": "character-name-consent-map",
      "name": "Character name consent map",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-consent-map/",
        "ja": "/ja/tools/character-name-consent-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Record who may use a chosen, former or intimate name",
      "task": "Record who may use a chosen, former or intimate name",
      "searchIntent": {
        "primary": "Complete the task: Record who may use a chosen, former or intimate name",
        "queryHypothesis": "character name consent map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record who may use a chosen, former or intimate name?",
        "When should character name consent map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record who may use a chosen, former or intimate name",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record who may use a chosen, former or intimate name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Record who may use a chosen, former or intimate name versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reclaimed-insult-name",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Record who may use a chosen, former or intimate name versus Trace who may use a reclaimed label and when; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Record who may use a chosen, former or intimate name versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record who may use a chosen, former or intimate name",
        "outline": [
          "Explain the specific decision: Record who may use a chosen, former or intimate name",
          "Define the applicable contract and limits for Character name consent map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record who may use a chosen, former or intimate name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record who may use a chosen, former or intimate name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:32",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-first-impression",
      "slug": "character-name-first-impression",
      "name": "Character name first impression",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-first-impression/",
        "ja": "/ja/tools/character-name-first-impression/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Compare intended characterization against reader supplied impressions",
      "task": "Compare intended characterization against reader supplied impressions",
      "searchIntent": {
        "primary": "Complete the task: Compare intended characterization against reader supplied impressions",
        "queryHypothesis": "character name first impression",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare intended characterization against reader supplied impressions?",
        "When should character name first impression be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare intended characterization against reader supplied impressions",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare intended characterization against reader supplied impressions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-spelling-dictation-test",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare intended characterization against reader supplied impressions versus Compare intended spelling against listener transcriptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare intended characterization against reader supplied impressions versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-role-association-test",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare intended characterization against reader supplied impressions versus Compare reader associations with intended role without claiming objectivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare intended characterization against reader supplied impressions",
        "outline": [
          "Explain the specific decision: Compare intended characterization against reader supplied impressions",
          "Define the applicable contract and limits for Character name first impression",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare intended characterization against reader supplied impressions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare intended characterization against reader supplied impressions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:33",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-semantic-overload",
      "slug": "character-name-semantic-overload",
      "name": "Character name semantic overload",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-semantic-overload/",
        "ja": "/ja/tools/character-name-semantic-overload/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Detect conflicts between name motifs and other story symbols",
      "task": "Detect conflicts between name motifs and other story symbols",
      "searchIntent": {
        "primary": "Complete the task: Detect conflicts between name motifs and other story symbols",
        "queryHypothesis": "character name semantic overload",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect conflicts between name motifs and other story symbols?",
        "When should character name semantic overload be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect conflicts between name motifs and other story symbols",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect conflicts between name motifs and other story symbols. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rebel-cell-identity-separation",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Detect conflicts between name motifs and other story symbols versus Avoid accidental leakage between cells in story dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Detect conflicts between name motifs and other story symbols versus Remove overdetermined motifs while preserving relevant story function; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-nickname-inheritance",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Detect conflicts between name motifs and other story symbols versus Track a nickname transferred between relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect conflicts between name motifs and other story symbols",
        "outline": [
          "Explain the specific decision: Detect conflicts between name motifs and other story symbols",
          "Define the applicable contract and limits for Character name semantic overload",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect conflicts between name motifs and other story symbols; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect conflicts between name motifs and other story symbols",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:34",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-name-chapter-heading",
      "slug": "character-name-chapter-heading",
      "name": "Character name chapter heading",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-name-chapter-heading/",
        "ja": "/ja/tools/character-name-chapter-heading/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Test headings against viewpoint identity and spoiler exposure",
      "task": "Test headings against viewpoint identity and spoiler exposure",
      "searchIntent": {
        "primary": "Complete the task: Test headings against viewpoint identity and spoiler exposure",
        "queryHypothesis": "character name chapter heading",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test headings against viewpoint identity and spoiler exposure?",
        "When should character name chapter heading be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test headings against viewpoint identity and spoiler exposure",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test headings against viewpoint identity and spoiler exposure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-audiobook-chapter-name-headings",
          "score": 0.2825,
          "sharedProfile": false,
          "difference": "Test headings against viewpoint identity and spoiler exposure versus Test spoken headings for identity spoilers and clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-chapter-title-name-spoiler",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Test headings against viewpoint identity and spoiler exposure versus Evaluate a title against the reader's current identity knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Test headings against viewpoint identity and spoiler exposure versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test headings against viewpoint identity and spoiler exposure",
        "outline": [
          "Explain the specific decision: Test headings against viewpoint identity and spoiler exposure",
          "Define the applicable contract and limits for Character name chapter heading",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test headings against viewpoint identity and spoiler exposure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test headings against viewpoint identity and spoiler exposure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:35",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-character-naming-uncertainty-map",
      "slug": "character-naming-uncertainty-map",
      "name": "Character naming uncertainty map",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-naming-uncertainty-map/",
        "ja": "/ja/tools/character-naming-uncertainty-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Identify missing research before committing a culturally situated name",
      "task": "Identify missing research before committing a culturally situated name",
      "searchIntent": {
        "primary": "Complete the task: Identify missing research before committing a culturally situated name",
        "queryHypothesis": "character naming uncertainty map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify missing research before committing a culturally situated name?",
        "When should character naming uncertainty map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "role brief: constrain narrative prominence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "setting and dates: bound evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "fixed name parts: preserve accepted identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary"
      ],
      "requiredData": [
        {
          "description": "author approved candidate corpus",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "claim level source ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify missing research before committing a culturally situated name",
        "separate name form from author's interpretation",
        "evaluate candidates against supplied story vocabulary",
        "Proposed category workflow: shortlist → scene test → evidence review → accepted identity",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "candidate identity forms",
        "fit rationale tied to the brief",
        "tradeoffs and revision alternatives"
      ],
      "capabilities": [
        "lock a supplied component and explain constrained alternatives",
        "trace a proposed choice to affected narrative references"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify missing research before committing a culturally situated name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-setting-name-rule-exception-map",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Identify missing research before committing a culturally situated name versus Identify which characters violate local rules and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-localization-name-map",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Identify missing research before committing a culturally situated name versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-consent-map",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Identify missing research before committing a culturally situated name versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify missing research before committing a culturally situated name",
        "outline": [
          "Explain the specific decision: Identify missing research before committing a culturally situated name",
          "Define the applicable contract and limits for Character naming uncertainty map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify missing research before committing a culturally situated name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify missing research before committing a culturally situated name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:36",
      "profileSource": "data/profiles.json#character-foundations"
    },
    {
      "id": "nw-family-name-planner",
      "slug": "family-name-planner",
      "name": "Family name planner",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-name-planner/",
        "ja": "/ja/tools/family-name-planner/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Assign shared surnames across a relationship graph",
      "task": "Assign shared surnames across a relationship graph",
      "searchIntent": {
        "primary": "Complete the task: Assign shared surnames across a relationship graph",
        "queryHypothesis": "family name planner",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to assign shared surnames across a relationship graph?",
        "When should family name planner be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "people",
          "use": "Stable ID, parent links, household and fixed given or family fields; unknown parents stay unknown."
        },
        {
          "key": "inheritance",
          "use": "Choose authored maternal, paternal, dual-component or explicit per-child inheritance, not a presumed cultural universal."
        },
        {
          "key": "generationMarkers",
          "use": "Optional author supplied marker table indexed by generation; do not infer generation from age."
        },
        {
          "key": "sceneGroups",
          "use": "Identify relatives likely to be introduced together for confusion checks."
        }
      ],
      "rules": [
        "Validate IDs, missing references and parent cycles before generating.",
        "Topologically traverse the relationship graph; derive only fields enabled by the selected inheritance policy.",
        "Locks override generation but never silently override inherited constraints; return a named conflict.",
        "A household change alone never changes a surname.",
        "Compare confirmed readings and visible short forms within each scene group.",
        "Follow the selected maternal parent ID only",
        "Follow the selected paternal parent ID only",
        "Preserve ordered maternal and paternal components",
        "Shared marker does not exempt a pair from collision review",
        "Evaluate all three pairs in a three-person introduction"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Validate IDs, missing references and parent cycles before generating.",
        "Topologically traverse the relationship graph; derive only fields enabled by the selected inheritance policy.",
        "Locks override generation but never silently override inherited constraints; return a named conflict.",
        "A household change alone never changes a surname.",
        "Compare confirmed readings and visible short forms within each scene group.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "personId and approved name components",
        "inheritedFrom path",
        "generation marker and exception reason",
        "within-family confusion pairs",
        "minimal unlocked alternatives",
        "Derivation source ID",
        "Derivation source ID",
        "Ordered surname parts",
        "Pair link and separate short forms",
        "Three pairwise findings"
      ],
      "capabilities": [
        "Preview a changed ancestor surname through the affected descendant subtree.",
        "Compare graph state before and after adoption while retaining approved earlier identities."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "A family graph must be solved jointly; one-person generation cannot propagate inherited components or expose inconsistent relatives.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hyphenated-family-name-limits",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Assign shared surnames across a relationship graph versus Resolve accumulated surnames across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Assign shared surnames across a relationship graph versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Assign shared surnames across a relationship graph versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Inheritance is a relationship rule, not a visual surname theme.",
        "outline": [
          "Draw the family before choosing a name pool",
          "When a shared surname is useful and when it is misleading",
          "One adoption event, three explicit naming decisions",
          "Distinguish cousins readers meet in the same scene",
          "Repair a locked-name conflict without rewriting the entire family"
        ],
        "story": "Fictional example: a household census labels an adopted mapmaker as a visitor because her retained surname differs. Her cousin corrects the household record without asking her to erase her earlier identity.",
        "storyAnalysis": "Compare retained identity plus an explicit household field with forced surname conformity. The misunderstanding depends on a record policy, not on a supposed universal adoption custom.",
        "evidence": "Original graph fixtures plus W3C personal-name model guidance; any actual jurisdiction claim requires separate sources.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/family.md",
        "localizedBodies": {
          "en": "content/en/family.md",
          "ja": "content/ja/family.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Changing a fictional inherited surname updates eligible unlocked descendants and no unrelated household.",
        "A parent cycle returns the exact cycle; no partial family is committed.",
        "A locked child surname incompatible with the chosen policy returns a conflict with two explicit resolution options.",
        "Unknown parentage does not invent relatives.",
        "Maternal surname changes only eligible unlocked children",
        "Paternal surname change does not alter maternal-policy children",
        "Swapping order reverses parts without changing person IDs",
        "Two same-reading twins remain flagged despite an intentional link",
        "Three names produce exactly three comparisons"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:39",
      "profileSource": "data/profiles.json#kinship",
      "absorbedModules": [
        {
          "sourceId": "nw-matrilineal-fictional-inheritance",
          "input": "inheritance= maternal",
          "rule": "Follow the selected maternal parent ID only",
          "output": "Derivation source ID",
          "acceptance": "Maternal surname changes only eligible unlocked children",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-patrilineal-fictional-inheritance",
          "input": "inheritance= paternal",
          "rule": "Follow the selected paternal parent ID only",
          "output": "Derivation source ID",
          "acceptance": "Paternal surname change does not alter maternal-policy children",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-dual-surname-family-system",
          "input": "inheritance=dual; componentOrder",
          "rule": "Preserve ordered maternal and paternal components",
          "output": "Ordered surname parts",
          "acceptance": "Swapping order reverses parts without changing person IDs",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-sibling-name-differentiation",
          "input": "sceneGroups; sceneMarkers; references; generations",
          "rule": "Evaluate every pair; shared markers never waive reading and short-form collision checks.",
          "output": "All-pair introduction matrix and shared-marker compliance without changing authored relationships.",
          "acceptance": "Three siblings produce three pair checks; removing a required marker changes compliance without changing parent IDs.",
          "evidence": [
            "FAM-04"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-twin-character-names",
          "input": "intentionalPairLinks",
          "rule": "Shared marker does not exempt a pair from collision review",
          "output": "Pair link and separate short forms",
          "acceptance": "Two same-reading twins remain flagged despite an intentional link",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-triplet-introduction-names",
          "input": "introductionGroups",
          "rule": "Evaluate all three pairs in a three-person introduction",
          "output": "Three pairwise findings",
          "acceptance": "Three names produce exactly three comparisons",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "family",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "Family members",
            "家族の一覧"
          ],
          "type": "textarea",
          "default": "p1 | Aven | Reed | | !\np2 | Sela | | p1 |\np3 | Oren | | p1 |",
          "help": [
            "One row: ID | given name | surname | inheritance parent ID | ! to lock surname. Parent is an authored link, not a gender assumption.",
            "1行ごとに ID | 名 | 姓 | 継承元のID | 姓を固定する場合 !。継承元は作者の設定です。"
          ]
        },
        {
          "key": "policy",
          "label": [
            "Surname rule",
            "姓のルール"
          ],
          "type": "select",
          "default": "parent",
          "help": null,
          "options": [
            [
              "parent",
              [
                "Inherit from declared parent",
                "指定した親から継承"
              ]
            ],
            [
              "shared",
              [
                "Shared household surname",
                "指定した共通の姓"
              ]
            ],
            [
              "keep",
              [
                "Keep supplied surnames",
                "入力された姓を維持"
              ]
            ],
            [
              "maternal",
              [
                "Maternal source",
                "母系の継承元"
              ]
            ],
            [
              "paternal",
              [
                "Paternal source",
                "父系の継承元"
              ]
            ],
            [
              "dual",
              [
                "Dual components",
                "二つの姓を継承"
              ]
            ]
          ]
        },
        {
          "key": "sharedSurname",
          "label": [
            "Shared surname",
            "共通の姓"
          ],
          "type": "text",
          "default": "Reed",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "parents",
          "label": [
            "Maternal and paternal links",
            "母系と父系のリンク"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "child ID | maternal parent ID | paternal parent ID",
            "子のID | 母系の親ID | 父系の親ID"
          ]
        },
        {
          "key": "componentOrder",
          "label": [
            "Dual-component order",
            "二つの姓の順序"
          ],
          "type": "select",
          "default": "maternal-first",
          "help": null,
          "options": [
            [
              "maternal-first",
              [
                "Maternal first",
                "母系を先に"
              ]
            ],
            [
              "paternal-first",
              [
                "Paternal first",
                "父系を先に"
              ]
            ]
          ]
        },
        {
          "key": "exceptions",
          "label": [
            "Explicit surname exceptions",
            "姓の明示的な例外"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | surname | reason",
            "ID | 姓 | 理由"
          ]
        },
        {
          "key": "events",
          "label": [
            "Dated family events",
            "章ごとの家族イベント"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "chapter | ID | parent/mother/father/household/surname | value | retain/inherit | reason",
            "章 | ID | parent/mother/father/household/surname | 値 | retain/inherit | 理由"
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Evaluate at chapter",
            "検証する章"
          ],
          "type": "number",
          "default": 5,
          "help": null
        },
        {
          "key": "compareChapter",
          "label": [
            "Compare with chapter",
            "比較元の章"
          ],
          "type": "number",
          "default": 0,
          "help": null
        },
        {
          "key": "generations",
          "label": [
            "Declared generations",
            "作者指定の世代"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | generation key. Not inferred from age.",
            "ID | 世代キー。年齢から推測しません。"
          ]
        },
        {
          "key": "markers",
          "label": [
            "Fictional generation markers",
            "架空の世代マーカー"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "generation key | marker",
            "世代キー | マーカー"
          ]
        },
        {
          "key": "references",
          "label": [
            "Scene reference forms",
            "場面で使う呼称"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | short form | approved reading",
            "ID | 短い呼称 | 確認済みの読み"
          ]
        },
        {
          "key": "sceneGroups",
          "label": [
            "Scene groups",
            "同じ場面の人物"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "scene ID | comma-separated person IDs",
            "場面ID | 人物IDをカンマ区切り"
          ]
        },
        {
          "key": "sceneMarkers",
          "label": [
            "Required shared markers in an introduction group",
            "導入グループで必要な共有マーカー"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "scene ID | exact authored marker. Optional, not a real cultural rule.",
            "場面ID | 作者指定の正確なマーカー。任意の架空規則です。"
          ]
        }
      ]
    },
    {
      "id": "nw-half-sibling-surname-logic",
      "slug": "half-sibling-surname-logic",
      "name": "Half sibling surname logic",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/half-sibling-surname-logic/",
        "ja": "/ja/tools/half-sibling-surname-logic/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Model different households and documented surname paths",
      "task": "Model different households and documented surname paths",
      "searchIntent": {
        "primary": "Complete the task: Model different households and documented surname paths",
        "queryHypothesis": "half sibling surname logic",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model different households and documented surname paths?",
        "When should half sibling surname logic be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model different households and documented surname paths",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model different households and documented surname paths. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-lost-sibling-reunion-names",
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Model different households and documented surname paths versus Reconcile names learned in separate households; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Model different households and documented surname paths versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-workplace-ensemble-name-map",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model different households and documented surname paths versus Model surname, title and first name use by colleague relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model different households and documented surname paths",
        "outline": [
          "Explain the specific decision: Model different households and documented surname paths",
          "Define the applicable contract and limits for Half sibling surname logic",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model different households and documented surname paths; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model different households and documented surname paths",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:43",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-stepfamily-address-map",
      "slug": "stepfamily-address-map",
      "name": "Stepfamily address map",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/stepfamily-address-map/",
        "ja": "/ja/tools/stepfamily-address-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Distinguish household membership from inherited naming",
      "task": "Distinguish household membership from inherited naming",
      "searchIntent": {
        "primary": "Complete the task: Distinguish household membership from inherited naming",
        "queryHypothesis": "stepfamily address map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish household membership from inherited naming?",
        "When should stepfamily address map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish household membership from inherited naming",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish household membership from inherited naming. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-court-retainer-identity",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish household membership from inherited naming versus Track service affiliation and inherited household names independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-house-identity-system",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish household membership from inherited naming versus Define house membership and inherited personal components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-capital-court-name-hierarchy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Distinguish household membership from inherited naming versus Keep citizen identity, court titles and household membership distinct; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish household membership from inherited naming",
        "outline": [
          "Explain the specific decision: Distinguish household membership from inherited naming",
          "Define the applicable contract and limits for Stepfamily address map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish household membership from inherited naming; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish household membership from inherited naming",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:44",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-adopted-character-name-timeline",
      "slug": "adopted-character-name-timeline",
      "name": "Adopted character name timeline",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/adopted-character-name-timeline/",
        "ja": "/ja/tools/adopted-character-name-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Track birth, placement and chosen names by story event",
      "task": "Track birth, placement and chosen names by story event",
      "searchIntent": {
        "primary": "Complete the task: Track birth, placement and chosen names by story event",
        "queryHypothesis": "adopted character name timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track birth, placement and chosen names by story event?",
        "When should adopted character name timeline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track birth, placement and chosen names by story event",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track birth, placement and chosen names by story event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rewrites-own-myth",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track birth, placement and chosen names by story event versus Coordinate chosen name, public story and skeptical observers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-alibi-timeline",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Track birth, placement and chosen names by story event versus Check which form a witness could have heard at a dated event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-live-roleplay-alias-reveal",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track birth, placement and chosen names by story event versus Schedule badge or roster changes at an agreed story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track birth, placement and chosen names by story event",
        "outline": [
          "Explain the specific decision: Track birth, placement and chosen names by story event",
          "Define the applicable contract and limits for Adopted character name timeline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track birth, placement and chosen names by story event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track birth, placement and chosen names by story event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:45",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-foster-household-naming",
      "slug": "foster-household-naming",
      "name": "Foster household naming",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/foster-household-naming/",
        "ja": "/ja/tools/foster-household-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Preserve separate legal and informal family relationships",
      "task": "Preserve separate legal and informal family relationships",
      "searchIntent": {
        "primary": "Complete the task: Preserve separate legal and informal family relationships",
        "queryHypothesis": "foster household naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve separate legal and informal family relationships?",
        "When should foster household naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve separate legal and informal family relationships",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve separate legal and informal family relationships. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Preserve separate legal and informal family relationships versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-multilingual-household",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Preserve separate legal and informal family relationships versus Combine two rule systems through declared family choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Preserve separate legal and informal family relationships versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve separate legal and informal family relationships",
        "outline": [
          "Explain the specific decision: Preserve separate legal and informal family relationships",
          "Define the applicable contract and limits for Foster household naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve separate legal and informal family relationships; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve separate legal and informal family relationships",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:46",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-found-family-address-system",
      "slug": "found-family-address-system",
      "name": "Found family address system",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/found-family-address-system/",
        "ja": "/ja/tools/found-family-address-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Design elective kinship terms without implying blood relationship",
      "task": "Design elective kinship terms without implying blood relationship",
      "searchIntent": {
        "primary": "Complete the task: Design elective kinship terms without implying blood relationship",
        "queryHypothesis": "found family address system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design elective kinship terms without implying blood relationship?",
        "When should found family address system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design elective kinship terms without implying blood relationship",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design elective kinship terms without implying blood relationship. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-secret-address-slip",
          "score": 0.16309523809523807,
          "sharedProfile": true,
          "difference": "Design elective kinship terms without implying blood relationship versus Design a revealing form of address with a scene knowledge ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Design elective kinship terms without implying blood relationship versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-kinship-address-policy",
          "score": 0.15,
          "sharedProfile": false,
          "difference": "Design elective kinship terms without implying blood relationship versus Preserve relationship information when terms do not align; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design elective kinship terms without implying blood relationship",
        "outline": [
          "Explain the specific decision: Design elective kinship terms without implying blood relationship",
          "Define the applicable contract and limits for Found family address system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design elective kinship terms without implying blood relationship; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design elective kinship terms without implying blood relationship",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:47",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-multigenerational-family-names",
      "slug": "multigenerational-family-names",
      "name": "Multigenerational family names",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/multigenerational-family-names/",
        "ja": "/ja/tools/multigenerational-family-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Allocate names over a dated family tree without accidental recycling",
      "task": "Allocate names over a dated family tree without accidental recycling",
      "searchIntent": {
        "primary": "Complete the task: Allocate names over a dated family tree without accidental recycling",
        "queryHypothesis": "multigenerational family names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to allocate names over a dated family tree without accidental recycling?",
        "When should multigenerational family names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Allocate names over a dated family tree without accidental recycling",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Allocate names over a dated family tree without accidental recycling. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-family-repeated-kanji",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Allocate names over a dated family tree without accidental recycling versus Track shared characters without assuming universal family practice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Allocate names over a dated family tree without accidental recycling versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-records-mismatch",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Allocate names over a dated family tree without accidental recycling versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Allocate names over a dated family tree without accidental recycling",
        "outline": [
          "Explain the specific decision: Allocate names over a dated family tree without accidental recycling",
          "Define the applicable contract and limits for Multigenerational family names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Allocate names over a dated family tree without accidental recycling; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Allocate names over a dated family tree without accidental recycling",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:48",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-namesake-ancestor-chain",
      "slug": "namesake-ancestor-chain",
      "name": "Namesake ancestor chain",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/namesake-ancestor-chain/",
        "ja": "/ja/tools/namesake-ancestor-chain/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Show repeated names with unambiguous narrative references",
      "task": "Show repeated names with unambiguous narrative references",
      "searchIntent": {
        "primary": "Complete the task: Show repeated names with unambiguous narrative references",
        "queryHypothesis": "namesake ancestor chain",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show repeated names with unambiguous narrative references?",
        "When should namesake ancestor chain be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show repeated names with unambiguous narrative references",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show repeated names with unambiguous narrative references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-breaks-namesake-cycle",
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Show repeated names with unambiguous narrative references versus Show the deliberate rejection of a repeated family pattern; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-generational-confusion-audit",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Show repeated names with unambiguous narrative references versus Detect repeated name references in dated scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Show repeated names with unambiguous narrative references versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show repeated names with unambiguous narrative references",
        "outline": [
          "Explain the specific decision: Show repeated names with unambiguous narrative references",
          "Define the applicable contract and limits for Namesake ancestor chain",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show repeated names with unambiguous narrative references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show repeated names with unambiguous narrative references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:49",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-generation-marker",
      "slug": "family-generation-marker",
      "name": "Family generation marker",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-generation-marker/",
        "ja": "/ja/tools/family-generation-marker/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Apply an author defined generation scheme to eligible relatives",
      "task": "Apply an author defined generation scheme to eligible relatives",
      "searchIntent": {
        "primary": "Complete the task: Apply an author defined generation scheme to eligible relatives",
        "queryHypothesis": "family generation marker",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply an author defined generation scheme to eligible relatives?",
        "When should family generation marker be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply an author defined generation scheme to eligible relatives",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply an author defined generation scheme to eligible relatives. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-generation-ship-family-names",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Apply an author defined generation scheme to eligible relatives versus Model repeated names across a closed fictional population; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-family-generation",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Apply an author defined generation scheme to eligible relatives versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-nickname-inheritance",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Apply an author defined generation scheme to eligible relatives versus Track a nickname transferred between relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply an author defined generation scheme to eligible relatives",
        "outline": [
          "Explain the specific decision: Apply an author defined generation scheme to eligible relatives",
          "Define the applicable contract and limits for Family generation marker",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply an author defined generation scheme to eligible relatives; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply an author defined generation scheme to eligible relatives",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:50",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-hyphenated-family-name-limits",
      "slug": "hyphenated-family-name-limits",
      "name": "Hyphenated family name limits",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/hyphenated-family-name-limits/",
        "ja": "/ja/tools/hyphenated-family-name-limits/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Resolve accumulated surnames across generations",
      "task": "Resolve accumulated surnames across generations",
      "searchIntent": {
        "primary": "Complete the task: Resolve accumulated surnames across generations",
        "queryHypothesis": "hyphenated family name limits",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve accumulated surnames across generations?",
        "When should hyphenated family name limits be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve accumulated surnames across generations",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve accumulated surnames across generations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.2557142857142857,
          "sharedProfile": false,
          "difference": "Resolve accumulated surnames across generations versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-name-planner",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Resolve accumulated surnames across generations versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-secret-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Resolve accumulated surnames across generations versus Track knowledge transfer and failures across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve accumulated surnames across generations",
        "outline": [
          "Explain the specific decision: Resolve accumulated surnames across generations",
          "Define the applicable contract and limits for Hyphenated family name limits",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve accumulated surnames across generations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve accumulated surnames across generations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:54",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-marriage-name-decision",
      "slug": "marriage-name-decision",
      "name": "Marriage name decision",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/marriage-name-decision/",
        "ja": "/ja/tools/marriage-name-decision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Compare retained, combined and changed names in a fictional household",
      "task": "Compare retained, combined and changed names in a fictional household",
      "searchIntent": {
        "primary": "Complete the task: Compare retained, combined and changed names in a fictional household",
        "queryHypothesis": "marriage name decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare retained, combined and changed names in a fictional household?",
        "When should marriage name decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare retained, combined and changed names in a fictional household",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare retained, combined and changed names in a fictional household. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-decision-record",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Compare retained, combined and changed names in a fictional household versus Save chosen names with reasons and rejected alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Compare retained, combined and changed names in a fictional household versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-space-colony-name-registry",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Compare retained, combined and changed names in a fictional household versus Separate habitat citizenship from personal and household identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare retained, combined and changed names in a fictional household",
        "outline": [
          "Explain the specific decision: Compare retained, combined and changed names in a fictional household",
          "Define the applicable contract and limits for Marriage name decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare retained, combined and changed names in a fictional household; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare retained, combined and changed names in a fictional household",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:55",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-divorce-name-continuity",
      "slug": "divorce-name-continuity",
      "name": "Divorce name continuity",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/divorce-name-continuity/",
        "ja": "/ja/tools/divorce-name-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Maintain records and dialogue references before and after separation",
      "task": "Maintain records and dialogue references before and after separation",
      "searchIntent": {
        "primary": "Complete the task: Maintain records and dialogue references before and after separation",
        "queryHypothesis": "divorce name continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain records and dialogue references before and after separation?",
        "When should divorce name continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain records and dialogue references before and after separation",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain records and dialogue references before and after separation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-erasure-story-continuity",
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Maintain records and dialogue references before and after separation versus Define how records and memories change after erasure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Maintain records and dialogue references before and after separation versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Maintain records and dialogue references before and after separation versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain records and dialogue references before and after separation",
        "outline": [
          "Explain the specific decision: Maintain records and dialogue references before and after separation",
          "Define the applicable contract and limits for Divorce name continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain records and dialogue references before and after separation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain records and dialogue references before and after separation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:56",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-widowed-character-name-use",
      "slug": "widowed-character-name-use",
      "name": "Widowed character name use",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/widowed-character-name-use/",
        "ja": "/ja/tools/widowed-character-name-use/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Model deliberate name retention and speaker expectations",
      "task": "Model deliberate name retention and speaker expectations",
      "searchIntent": {
        "primary": "Complete the task: Model deliberate name retention and speaker expectations",
        "queryHypothesis": "widowed character name use",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model deliberate name retention and speaker expectations?",
        "When should widowed character name use be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model deliberate name retention and speaker expectations",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model deliberate name retention and speaker expectations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-middle-name-use",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Model deliberate name retention and speaker expectations versus Decide where a middle name matters in dialogue and records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Model deliberate name retention and speaker expectations versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Model deliberate name retention and speaker expectations versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model deliberate name retention and speaker expectations",
        "outline": [
          "Explain the specific decision: Model deliberate name retention and speaker expectations",
          "Define the applicable contract and limits for Widowed character name use",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model deliberate name retention and speaker expectations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model deliberate name retention and speaker expectations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:57",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-estranged-sibling-name-clues",
      "slug": "estranged-sibling-name-clues",
      "name": "Estranged sibling name clues",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/estranged-sibling-name-clues/",
        "ja": "/ja/tools/estranged-sibling-name-clues/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Control how much shared structure reveals relatedness",
      "task": "Control how much shared structure reveals relatedness",
      "searchIntent": {
        "primary": "Complete the task: Control how much shared structure reveals relatedness",
        "queryHypothesis": "estranged sibling name clues",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to control how much shared structure reveals relatedness?",
        "When should estranged sibling name clues be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Control how much shared structure reveals relatedness",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Control how much shared structure reveals relatedness. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-sibling-alias-clues",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Control how much shared structure reveals relatedness versus Limit overlaps that would expose a relationship prematurely; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-relation-inference-test",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Control how much shared structure reveals relatedness versus Check what a shared structure leads readers to infer; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Control how much shared structure reveals relatedness versus Show how a remembered form reveals relationship history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Control how much shared structure reveals relatedness",
        "outline": [
          "Explain the specific decision: Control how much shared structure reveals relatedness",
          "Define the applicable contract and limits for Estranged sibling name clues",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Control how much shared structure reveals relatedness; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Control how much shared structure reveals relatedness",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:58",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-secret-parentage-name-clues",
      "slug": "secret-parentage-name-clues",
      "name": "Secret parentage name clues",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/secret-parentage-name-clues/",
        "ja": "/ja/tools/secret-parentage-name-clues/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Place bounded clues without proving lineage through a name alone",
      "task": "Place bounded clues without proving lineage through a name alone",
      "searchIntent": {
        "primary": "Complete the task: Place bounded clues without proving lineage through a name alone",
        "queryHypothesis": "secret parentage name clues",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to place bounded clues without proving lineage through a name alone?",
        "When should secret parentage name clues be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Place bounded clues without proving lineage through a name alone",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Place bounded clues without proving lineage through a name alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-sibling-alias-clues",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Place bounded clues without proving lineage through a name alone versus Limit overlaps that would expose a relationship prematurely; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.11333333333333333,
          "sharedProfile": false,
          "difference": "Place bounded clues without proving lineage through a name alone versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Place bounded clues without proving lineage through a name alone versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Place bounded clues without proving lineage through a name alone",
        "outline": [
          "Explain the specific decision: Place bounded clues without proving lineage through a name alone",
          "Define the applicable contract and limits for Secret parentage name clues",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Place bounded clues without proving lineage through a name alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Place bounded clues without proving lineage through a name alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:59",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-disputed-heir-name-evidence",
      "slug": "disputed-heir-name-evidence",
      "name": "Disputed heir name evidence",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/disputed-heir-name-evidence/",
        "ja": "/ja/tools/disputed-heir-name-evidence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Separate claimed descent, documentary forms and narrative inference",
      "task": "Separate claimed descent, documentary forms and narrative inference",
      "searchIntent": {
        "primary": "Complete the task: Separate claimed descent, documentary forms and narrative inference",
        "queryHypothesis": "disputed heir name evidence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate claimed descent, documentary forms and narrative inference?",
        "When should disputed heir name evidence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate claimed descent, documentary forms and narrative inference",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate claimed descent, documentary forms and narrative inference. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-in-records",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate claimed descent, documentary forms and narrative inference versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-title-evidence-file",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Separate claimed descent, documentary forms and narrative inference versus Separate attested office forms from fictional inventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate claimed descent, documentary forms and narrative inference versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate claimed descent, documentary forms and narrative inference",
        "outline": [
          "Explain the specific decision: Separate claimed descent, documentary forms and narrative inference",
          "Define the applicable contract and limits for Disputed heir name evidence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate claimed descent, documentary forms and narrative inference; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate claimed descent, documentary forms and narrative inference",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:60",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-branch-differentiation",
      "slug": "family-branch-differentiation",
      "name": "Family branch differentiation",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-branch-differentiation/",
        "ja": "/ja/tools/family-branch-differentiation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Mark branches without treating all cousins as interchangeable",
      "task": "Mark branches without treating all cousins as interchangeable",
      "searchIntent": {
        "primary": "Complete the task: Mark branches without treating all cousins as interchangeable",
        "queryHypothesis": "family branch differentiation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to mark branches without treating all cousins as interchangeable?",
        "When should family branch differentiation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Mark branches without treating all cousins as interchangeable",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Mark branches without treating all cousins as interchangeable. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-multigenerational-family-names",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Mark branches without treating all cousins as interchangeable versus Allocate names over a dated family tree without accidental recycling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-records-mismatch",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Mark branches without treating all cousins as interchangeable versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Mark branches without treating all cousins as interchangeable versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Mark branches without treating all cousins as interchangeable",
        "outline": [
          "Explain the specific decision: Mark branches without treating all cousins as interchangeable",
          "Define the applicable contract and limits for Family branch differentiation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Mark branches without treating all cousins as interchangeable; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Mark branches without treating all cousins as interchangeable",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:61",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-clan-adoption-naming",
      "slug": "clan-adoption-naming",
      "name": "Clan adoption naming",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/clan-adoption-naming/",
        "ja": "/ja/tools/clan-adoption-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Integrate an outsider into an invented clan's explicit rules",
      "task": "Integrate an outsider into an invented clan's explicit rules",
      "searchIntent": {
        "primary": "Complete the task: Integrate an outsider into an invented clan's explicit rules",
        "queryHypothesis": "clan adoption naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to integrate an outsider into an invented clan's explicit rules?",
        "When should clan adoption naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Integrate an outsider into an invented clan's explicit rules",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Integrate an outsider into an invented clan's explicit rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Integrate an outsider into an invented clan's explicit rules versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-nickname-adoption",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Integrate an outsider into an invented clan's explicit rules versus Track table invented nicknames separately from in world forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-clan-name-affixes",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Integrate an outsider into an invented clan's explicit rules versus Enforce a declared clan marker across eligible members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Integrate an outsider into an invented clan's explicit rules",
        "outline": [
          "Explain the specific decision: Integrate an outsider into an invented clan's explicit rules",
          "Define the applicable contract and limits for Clan adoption naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Integrate an outsider into an invented clan's explicit rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Integrate an outsider into an invented clan's explicit rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:62",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-household-servant-address",
      "slug": "household-servant-address",
      "name": "Household servant address",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/household-servant-address/",
        "ja": "/ja/tools/household-servant-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Map speaker status and address without making a universal cultural claim",
      "task": "Map speaker status and address without making a universal cultural claim",
      "searchIntent": {
        "primary": "Complete the task: Map speaker status and address without making a universal cultural claim",
        "queryHypothesis": "household servant address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map speaker status and address without making a universal cultural claim?",
        "When should household servant address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map speaker status and address without making a universal cultural claim",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map speaker status and address without making a universal cultural claim. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.1976190476190476,
          "sharedProfile": false,
          "difference": "Map speaker status and address without making a universal cultural claim versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-rationing-society",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Map speaker status and address without making a universal cultural claim versus Explain allocation rules and social conflicts without a universal cultural claim; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-relationship-graph",
          "score": 0.15666666666666668,
          "sharedProfile": false,
          "difference": "Map speaker status and address without making a universal cultural claim versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map speaker status and address without making a universal cultural claim",
        "outline": [
          "Explain the specific decision: Map speaker status and address without making a universal cultural claim",
          "Define the applicable contract and limits for Household servant address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map speaker status and address without making a universal cultural claim; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map speaker status and address without making a universal cultural claim",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:63",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-nickname-inheritance",
      "slug": "family-nickname-inheritance",
      "name": "Family nickname inheritance",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-nickname-inheritance/",
        "ja": "/ja/tools/family-nickname-inheritance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Track a nickname transferred between relatives",
      "task": "Track a nickname transferred between relatives",
      "searchIntent": {
        "primary": "Complete the task: Track a nickname transferred between relatives",
        "queryHypothesis": "family nickname inheritance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track a nickname transferred between relatives?",
        "When should family nickname inheritance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track a nickname transferred between relatives",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track a nickname transferred between relatives. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-inheritance-exception",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Track a nickname transferred between relatives versus Document the story event that overrides the default surname rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-generation-marker",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Track a nickname transferred between relatives versus Apply an author defined generation scheme to eligible relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Track a nickname transferred between relatives versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track a nickname transferred between relatives",
        "outline": [
          "Explain the specific decision: Track a nickname transferred between relatives",
          "Define the applicable contract and limits for Family nickname inheritance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track a nickname transferred between relatives; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track a nickname transferred between relatives",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:64",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-grandparent-address-network",
      "slug": "grandparent-address-network",
      "name": "Grandparent address network",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/grandparent-address-network/",
        "ja": "/ja/tools/grandparent-address-network/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Keep different speakers' kin terms attached to the same person",
      "task": "Keep different speakers' kin terms attached to the same person",
      "searchIntent": {
        "primary": "Complete the task: Keep different speakers' kin terms attached to the same person",
        "queryHypothesis": "grandparent address network",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep different speakers' kin terms attached to the same person?",
        "When should grandparent address network be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep different speakers' kin terms attached to the same person",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep different speakers' kin terms attached to the same person. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-sibling-birth-order-address",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Keep different speakers' kin terms attached to the same person versus Use a supplied cultural policy rather than infer kin terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cross-household-child-address",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Keep different speakers' kin terms attached to the same person versus Preserve different names used by guardians in separate homes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-respectful-address-disagreement",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Keep different speakers' kin terms attached to the same person versus Model speakers who differ about a preferred form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep different speakers' kin terms attached to the same person",
        "outline": [
          "Explain the specific decision: Keep different speakers' kin terms attached to the same person",
          "Define the applicable contract and limits for Grandparent address network",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep different speakers' kin terms attached to the same person; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep different speakers' kin terms attached to the same person",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:65",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-cousin-reunion-cast-names",
      "slug": "cousin-reunion-cast-names",
      "name": "Cousin reunion cast names",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/cousin-reunion-cast-names/",
        "ja": "/ja/tools/cousin-reunion-cast-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Avoid collisions during a large family gathering scene",
      "task": "Avoid collisions during a large family gathering scene",
      "searchIntent": {
        "primary": "Complete the task: Avoid collisions during a large family gathering scene",
        "queryHypothesis": "cousin reunion cast names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid collisions during a large family gathering scene?",
        "When should cousin reunion cast names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid collisions during a large family gathering scene",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid collisions during a large family gathering scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-confusion-severity-triage",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Avoid collisions during a large family gathering scene versus Prioritize reader reported collisions by actual scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-cast-registry",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Avoid collisions during a large family gathering scene versus Prevent collisions across sessions and locations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-name-relationship-heatmap",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Avoid collisions during a large family gathering scene versus Combine scene proximity with similarity for targeted review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid collisions during a large family gathering scene",
        "outline": [
          "Explain the specific decision: Avoid collisions during a large family gathering scene",
          "Define the applicable contract and limits for Cousin reunion cast names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid collisions during a large family gathering scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid collisions during a large family gathering scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:66",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-tree-label-layout",
      "slug": "family-tree-label-layout",
      "name": "Family tree label layout",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-tree-label-layout/",
        "ja": "/ja/tools/family-tree-label-layout/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fiction, comic and game authors preparing readable name-bearing relationship diagrams from known identities.",
      "scenario": "A child draws two ancestors after seeing one person repeated on two branches; the author needs readable repetition with visible identity references rather than an accidental merge or deletion.",
      "task": "Lay out an authored occurrence DAG with source-bound label dimensions, inspect remaining geometric problems and export a private ID-labelled SVG.",
      "searchIntent": {
        "primary": "Prepare readable family-diagram name labels with repeated identities and exported layout.",
        "queryHypothesis": "family tree repeated person label layout",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Do two boxes mean two people?",
        "Does a lower layer establish a younger generation?",
        "Why does a name change invalidate measured dimensions?"
      ],
      "inputs": [
        {
          "key": "people",
          "type": "textarea",
          "purpose": "1–80 {id,name,short}. IDs unique ≤40, labels ≤120; empty short falls back to full. Authored links assert no biological or legal relationship."
        },
        {
          "key": "occurrences",
          "type": "textarea",
          "purpose": "1–100 {id,person}. Reuse a person ID for repeated appearances, but every box has its own occurrence ID."
        },
        {
          "key": "links",
          "type": "textarea",
          "purpose": "0–160 {from,to} occurrence links, no duplicates, self-links or directed cycles. Arrows mean only what your caption declares."
        },
        {
          "key": "labelMode",
          "type": "select",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "orientation",
          "type": "select",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "fontSize",
          "type": "number",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "gap",
          "type": "number",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "levelGap",
          "type": "number",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "frameWidth",
          "type": "number",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "frameHeight",
          "type": "number",
          "purpose": "Task-specific drawing geometry control."
        },
        {
          "key": "measurements",
          "type": "textarea",
          "purpose": "Use the capture button after generating. {} uses explicitly labelled estimates. Supplied measurements must match the current labels/font; changing them requires recapture. A saved measurement record is not independently authenticated."
        },
        {
          "key": "context",
          "type": "textarea",
          "purpose": "≤1000 units; included in private audit and SVG metadata."
        }
      ],
      "rules": [
        "1–80 unique people with full/short labels, 1–100 occurrence boxes referencing existing person IDs, 0–160 exact directed occurrence links. Repeated people across boxes are allowed, self-links, duplicate edges and directed cycles are rejected. No inferred blood, household or legal relations.",
        "Layer by longest directed path; top-to-bottom or left-to-right geometry uses literal full/short labels, reported full fallbacks and separately controlled layer/within-layer gaps. Unplaced people remain explicit.",
        "Initial text dimensions are disclosed estimates including visible ID lines. Browser capture waits document fonts and measures literal Georgia/serif label and ID width; source key ties supplied dimensions to labels and font. Changes reject stale bounds. Supplied records are not independently authenticated.",
        "Eight alternating barycentric sweeps retain only strict improvements in proper straight-segment crossing count. No global optimality claim. Inspect unrelated-box line intersections, rectangle overlaps, same labels across different people and target-frame overflow separately.",
        "Target frame does not shrink text to force success. SVG preserves actual geometry, visible occurrence/person IDs, dimension mode and private source/context metadata; escaping retains literal markup-like names. Download refuses a changed worksheet until recomputed.",
        "Copy/favorites/compare/project/audit preserve person-versus-occurrence distinction. A diagram is a production artifact, not an authenticated genealogy."
      ],
      "requiredData": [
        {
          "description": "Original fictional Ena/Sol/Min/Tavi chart with one person repeated on two branches.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-authored people, occurrences, directed links and optional browser dimension record.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "1–80 unique people with full/short labels, 1–100 occurrence boxes referencing existing person IDs, 0–160 exact directed occurrence links. Repeated people across boxes are allowed, self-links, duplicate edges and directed cycles are rejected. No inferred blood, household or legal relations.",
        "Layer by longest directed path; top-to-bottom or left-to-right geometry uses literal full/short labels, reported full fallbacks and separately controlled layer/within-layer gaps. Unplaced people remain explicit.",
        "Initial text dimensions are disclosed estimates including visible ID lines. Browser capture waits document fonts and measures literal Georgia/serif label and ID width; source key ties supplied dimensions to labels and font. Changes reject stale bounds. Supplied records are not independently authenticated.",
        "Eight alternating barycentric sweeps retain only strict improvements in proper straight-segment crossing count. No global optimality claim. Inspect unrelated-box line intersections, rectangle overlaps, same labels across different people and target-frame overflow separately.",
        "Target frame does not shrink text to force success. SVG preserves actual geometry, visible occurrence/person IDs, dimension mode and private source/context metadata; escaping retains literal markup-like names. Download refuses a changed worksheet until recomputed.",
        "Copy/favorites/compare/project/audit preserve person-versus-occurrence distinction. A diagram is a production artifact, not an authenticated genealogy."
      ],
      "outputs": [
        "Accessible literal-name SVG with occurrence/person IDs and source metadata.",
        "Initial/retained crossings, line-through-box witnesses, overlaps, outside-frame occurrences and distinct-person same-label pairs.",
        "Per-person occurrence map, unplaced people and exact coordinates.",
        "Private audit and source-guarded SVG download."
      ],
      "capabilities": [
        "Separate identity records from chart occurrences, preserving repeated identity across different branches and unplaced supplied people.",
        "Actual browser label/ID width capture, stale-dimension detection and explicitly estimated fallback.",
        "Finite layered layout with retained crossing improvements, independent obstruction/frame findings and exact escaped SVG."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Family naming creates names and resolves declared shared structures. Identity review evaluates same/separate declarations. This page assumes those decisions and prepares a physical diagram: repeated occurrences, measured boxes, layered positions, straight-link geometry and source-guarded SVG. Switching a surname option cannot perform that production task.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "family-name-planner",
          "difference": "Generative family rules resolve the names belonging to records; an occurrence DAG lays out already known identities, allows one person in several boxes and tests actual text dimensions, frame bounds and line obstructions."
        }
      },
      "nearestTools": [
        {
          "id": "nw-campaign-family-tree",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Lay out an authored occurrence DAG with source-bound label dimensions, inspect remaining geometric problems and export a private ID-labelled SVG. versus Build relationship linked names from player approved lore; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-bible",
          "score": 0.09826086956521739,
          "sharedProfile": true,
          "difference": "Lay out an authored occurrence DAG with source-bound label dimensions, inspect remaining geometric problems and export a private ID-labelled SVG. versus Export people, naming rules and exception decisions as one reference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-merchant-family-trade-names",
          "score": 0.08928571428571427,
          "sharedProfile": false,
          "difference": "Lay out an authored occurrence DAG with source-bound label dimensions, inspect remaining geometric problems and export a private ID-labelled SVG. versus Separate a business label from each household member; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "The physical representation of a name can manufacture a second person; identity references and readable geometry must be edited together.",
        "outline": [
          "A diagram can multiply a person",
          "Original two portraits for one ancestor",
          "People versus appearances",
          "Arrows need a declared meaning",
          "Estimated versus browser dimensions",
          "Bounded crossing improvements",
          "Frame as production constraint",
          "Accountable private picture",
          "Revise explanation as well as geometry"
        ],
        "story": "Tavi draws two versions of Ena after seeing two branches. The maker keeps repeated occurrence boxes with a common person ID and explains the navigation choice, letting both portraits become views of one fictional person.",
        "storyAnalysis": "If the two E nas were truly different namesakes, one person ID would erase an identity. Separate IDs and a same-label finding support a different caption; the software must not merge them for visual neatness.",
        "evidence": "Original complete EN/JA diagram guides, finite geometry fixtures and actual browser capture/download observations; no historical kinship convention.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/familyChart.md",
        "localizedBodies": {
          "en": "content/en/familyChart.md",
          "ja": "content/ja/familyChart.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default has five boxes but four people; two Ena occurrences resolve to person ena.",
        "A directed cycle, duplicate reversed-property-order edge, unknown person or stale dimensions clears diagram.",
        "Simple crossed pair improves one crossing to zero; no retained result increases crossings.",
        "Browser capture changes actual geometry; label/font changes require recapture, orientation/gap changes retain valid dimensions.",
        "Small frame exposes overflow without scaling text; short fallback and same-label different people remain explicit.",
        "Actual SVG download contains visible IDs, escaped names and private metadata; changed source cannot export stale layout.",
        "Both full localized guides and all four viewport submissions must pass."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:67",
      "profileSource": "data/profiles.json#kinship",
      "specBatch": "batch-16",
      "implementationDifficulty": {
        "level": "high",
        "reason": "DAG validation, source-bound browser dimensions, finite layered geometry refinement and independent crossing/intersection/frame checks with escaped export."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "familyChart",
        "engineFiles": [
          "web/family-chart.mjs",
          "web/family-chart-tool.mjs",
          "web/family-chart-view.mjs",
          "web/family-chart-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/family-chart.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "People · JSON",
            "人物・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"ena\",\n    \"name\": \"Ena Vale\",\n    \"short\": \"Ena\"\n  },\n  {\n    \"id\": \"sol\",\n    \"name\": \"Sol Vale\",\n    \"short\": \"Sol\"\n  },\n  {\n    \"id\": \"min\",\n    \"name\": \"Min Vale\",\n    \"short\": \"Min\"\n  },\n  {\n    \"id\": \"tavi\",\n    \"name\": \"Tavi Reed\",\n    \"short\": \"Tavi\"\n  }\n]",
          "help": [
            "1–80 {id,name,short}. IDs unique ≤40, labels ≤120; empty short falls back to full. Authored links assert no biological or legal relationship.",
            "{id,name,short}を1〜80件。固有ID40以内、表示120以内。shortが空なら名前全体を使用。連線は生物学・法律上の関係を認定しません。"
          ],
          "maxLength": 28000
        },
        {
          "key": "occurrences",
          "label": [
            "Chart occurrences · JSON",
            "図上の出現位置・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"ena-left\",\n    \"person\": \"ena\"\n  },\n  {\n    \"id\": \"ena-right\",\n    \"person\": \"ena\"\n  },\n  {\n    \"id\": \"sol-box\",\n    \"person\": \"sol\"\n  },\n  {\n    \"id\": \"min-box\",\n    \"person\": \"min\"\n  },\n  {\n    \"id\": \"tavi-box\",\n    \"person\": \"tavi\"\n  }\n]",
          "help": [
            "1–100 {id,person}. Reuse a person ID for repeated appearances, but every box has its own occurrence ID.",
            "{id,person}を1〜100件。同一人物を再掲する時はpersonを共通にし、箱のidは固有にします。"
          ],
          "maxLength": 16000
        },
        {
          "key": "links",
          "label": [
            "Directed chart links · JSON",
            "図の有向連線・JSON"
          ],
          "type": "textarea",
          "default": "[{\"from\":\"ena-left\",\"to\":\"sol-box\"},{\"from\":\"ena-right\",\"to\":\"min-box\"},{\"from\":\"sol-box\",\"to\":\"tavi-box\"},{\"from\":\"min-box\",\"to\":\"tavi-box\"}]",
          "help": [
            "0–160 {from,to} occurrence links, no duplicates, self-links or directed cycles. Arrows mean only what your caption declares.",
            "出現位置間の{from,to}を0〜160件。重複、自己参照、有向循環不可。矢印の意味は作者が別途定義します。"
          ],
          "maxLength": 16000
        },
        {
          "key": "labelMode",
          "label": [
            "Label form",
            "表示形"
          ],
          "type": "select",
          "default": "full",
          "help": null,
          "options": [
            [
              "full",
              [
                "Full supplied name",
                "入力した名前全体"
              ]
            ],
            [
              "short",
              [
                "Supplied short label, with full fallback",
                "短い表示・空なら全体"
              ]
            ]
          ]
        },
        {
          "key": "orientation",
          "label": [
            "Arrow direction",
            "矢印の方向"
          ],
          "type": "select",
          "default": "down",
          "help": null,
          "options": [
            [
              "down",
              [
                "Top to bottom",
                "上から下"
              ]
            ],
            [
              "right",
              [
                "Left to right",
                "左から右"
              ]
            ]
          ]
        },
        {
          "key": "fontSize",
          "label": [
            "Georgia / serif label size · 10–40 px",
            "Georgia／serif文字サイズ・10〜40px"
          ],
          "type": "number",
          "default": 18,
          "help": null
        },
        {
          "key": "gap",
          "label": [
            "Space within a layer · 10–160 px",
            "同じ層の間隔・10〜160px"
          ],
          "type": "number",
          "default": 24,
          "help": null
        },
        {
          "key": "levelGap",
          "label": [
            "Space between layers · 20–200 px",
            "層の間隔・20〜200px"
          ],
          "type": "number",
          "default": 60,
          "help": null
        },
        {
          "key": "frameWidth",
          "label": [
            "Target frame width · 200–4000 px",
            "対象枠の幅・200〜4000px"
          ],
          "type": "number",
          "default": 720,
          "help": null
        },
        {
          "key": "frameHeight",
          "label": [
            "Target frame height · 200–4000 px",
            "対象枠の高さ・200〜4000px"
          ],
          "type": "number",
          "default": 520,
          "help": null
        },
        {
          "key": "measurements",
          "label": [
            "Source-bound label dimensions · JSON",
            "入力に結び付く文字寸法・JSON"
          ],
          "type": "textarea",
          "default": "{}",
          "help": [
            "Use the capture button after generating. {} uses explicitly labelled estimates. Supplied measurements must match the current labels/font; changing them requires recapture. A saved measurement record is not independently authenticated.",
            "配置後の測定ボタンを使用。{}なら推定と明記します。寸法は現在の表示とフォントに一致する必要があり、変更後は再測定します。保存した測定記録の真正性を別途認定しません。"
          ],
          "maxLength": 18000
        },
        {
          "key": "context",
          "label": [
            "Private chart caption and story purpose",
            "非公開の図の注釈・物語上の目的"
          ],
          "type": "textarea",
          "default": "Ena is repeated on two authored branches. The caption must make clear that two boxes do not mean two ancestors; arrows are fictional relation links, not inferred blood or inheritance.",
          "help": [
            "≤1000 units; included in private audit and SVG metadata.",
            "1000単位以内。非公開検証とSVGメタデータに含みます。"
          ],
          "maxLength": 1000
        }
      ]
    },
    {
      "id": "nw-lost-sibling-reunion-names",
      "slug": "lost-sibling-reunion-names",
      "name": "Lost sibling reunion names",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/lost-sibling-reunion-names/",
        "ja": "/ja/tools/lost-sibling-reunion-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Reconcile names learned in separate households",
      "task": "Reconcile names learned in separate households",
      "searchIntent": {
        "primary": "Complete the task: Reconcile names learned in separate households",
        "queryHypothesis": "lost sibling reunion names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile names learned in separate households?",
        "When should lost sibling reunion names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile names learned in separate households",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile names learned in separate households. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-half-sibling-surname-logic",
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Reconcile names learned in separate households versus Model different households and documented surname paths; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-obituary-clue",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Reconcile names learned in separate households versus Reconcile dates, names and witnesses in fictional records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-lore-naming-conflict",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Reconcile names learned in separate households versus Reconcile two contributor supplied naming conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile names learned in separate households",
        "outline": [
          "Explain the specific decision: Reconcile names learned in separate households",
          "Define the applicable contract and limits for Lost sibling reunion names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile names learned in separate households; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile names learned in separate households",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:68",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-records-mismatch",
      "slug": "family-records-mismatch",
      "name": "Family records mismatch",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-records-mismatch/",
        "ja": "/ja/tools/family-records-mismatch/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Explain alternate spellings without silently merging characters",
      "task": "Explain alternate spellings without silently merging characters",
      "searchIntent": {
        "primary": "Complete the task: Explain alternate spellings without silently merging characters",
        "queryHypothesis": "family records mismatch",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain alternate spellings without silently merging characters?",
        "When should family records mismatch be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain alternate spellings without silently merging characters",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain alternate spellings without silently merging characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-multigenerational-family-names",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Explain alternate spellings without silently merging characters versus Allocate names over a dated family tree without accidental recycling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-import-validation",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Explain alternate spellings without silently merging characters versus Reject malformed datasets without silently dropping characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-source-contradiction",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Explain alternate spellings without silently merging characters versus Compare conflicting references without silently selecting one; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain alternate spellings without silently merging characters",
        "outline": [
          "Explain the specific decision: Explain alternate spellings without silently merging characters",
          "Define the applicable contract and limits for Family records mismatch",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain alternate spellings without silently merging characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain alternate spellings without silently merging characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:69",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-intermarried-fictional-houses",
      "slug": "intermarried-fictional-houses",
      "name": "Intermarried fictional houses",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/intermarried-fictional-houses/",
        "ja": "/ja/tools/intermarried-fictional-houses/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Reconcile two invented inheritance policies",
      "task": "Reconcile two invented inheritance policies",
      "searchIntent": {
        "primary": "Complete the task: Reconcile two invented inheritance policies",
        "queryHypothesis": "intermarried fictional houses",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile two invented inheritance policies?",
        "When should intermarried fictional houses be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile two invented inheritance policies",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile two invented inheritance policies. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-lore-naming-conflict",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Reconcile two invented inheritance policies versus Reconcile two contributor supplied naming conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-culture-naming-contrast",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile two invented inheritance policies versus Compare two invented cultures using explicit structural rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-merged-identity-systems",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile two invented inheritance policies versus Reconcile naming rules after two fictional organizations combine; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile two invented inheritance policies",
        "outline": [
          "Explain the specific decision: Reconcile two invented inheritance policies",
          "Define the applicable contract and limits for Intermarried fictional houses",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile two invented inheritance policies; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile two invented inheritance policies",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:70",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-taboo-name-rule",
      "slug": "family-taboo-name-rule",
      "name": "Family taboo name rule",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-taboo-name-rule/",
        "ja": "/ja/tools/family-taboo-name-rule/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Apply an invented ban while showing exceptions and their costs",
      "task": "Apply an invented ban while showing exceptions and their costs",
      "searchIntent": {
        "primary": "Complete the task: Apply an invented ban while showing exceptions and their costs",
        "queryHypothesis": "family taboo name rule",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply an invented ban while showing exceptions and their costs?",
        "When should family taboo name rule be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply an invented ban while showing exceptions and their costs",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply an invented ban while showing exceptions and their costs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-generation-marker",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Apply an invented ban while showing exceptions and their costs versus Apply an author defined generation scheme to eligible relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Apply an invented ban while showing exceptions and their costs versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Apply an invented ban while showing exceptions and their costs versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply an invented ban while showing exceptions and their costs",
        "outline": [
          "Explain the specific decision: Apply an invented ban while showing exceptions and their costs",
          "Define the applicable contract and limits for Family taboo name rule",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply an invented ban while showing exceptions and their costs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply an invented ban while showing exceptions and their costs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:71",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-memorial-naming",
      "slug": "family-memorial-naming",
      "name": "Family memorial naming",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-memorial-naming/",
        "ja": "/ja/tools/family-memorial-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Track whom a child is named for and who knows the connection",
      "task": "Track whom a child is named for and who knows the connection",
      "searchIntent": {
        "primary": "Complete the task: Track whom a child is named for and who knows the connection",
        "queryHypothesis": "family memorial naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track whom a child is named for and who knows the connection?",
        "When should family memorial naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track whom a child is named for and who knows the connection",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track whom a child is named for and who knows the connection. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track whom a child is named for and who knows the connection versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track whom a child is named for and who knows the connection versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-name-planner",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Track whom a child is named for and who knows the connection versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track whom a child is named for and who knows the connection",
        "outline": [
          "Explain the specific decision: Track whom a child is named for and who knows the connection",
          "Define the applicable contract and limits for Family memorial naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track whom a child is named for and who knows the connection; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track whom a child is named for and who knows the connection",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:72",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-surname-extinction",
      "slug": "family-surname-extinction",
      "name": "Family surname extinction",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-surname-extinction/",
        "ja": "/ja/tools/family-surname-extinction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Model succession choices when a fictional line has no designated heir",
      "task": "Model succession choices when a fictional line has no designated heir",
      "searchIntent": {
        "primary": "Complete the task: Model succession choices when a fictional line has no designated heir",
        "queryHypothesis": "family surname extinction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model succession choices when a fictional line has no designated heir?",
        "When should family surname extinction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model succession choices when a fictional line has no designated heir",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model succession choices when a fictional line has no designated heir. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-generation-ship-family-names",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Model succession choices when a fictional line has no designated heir versus Model repeated names across a closed fictional population; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-surname-inheritance",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Model succession choices when a fictional line has no designated heir versus Model family transmission independently of given name generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.110625,
          "sharedProfile": false,
          "difference": "Model succession choices when a fictional line has no designated heir versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model succession choices when a fictional line has no designated heir",
        "outline": [
          "Explain the specific decision: Model succession choices when a fictional line has no designated heir",
          "Define the applicable contract and limits for Family surname extinction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model succession choices when a fictional line has no designated heir; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model succession choices when a fictional line has no designated heir",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:73",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-illegitimacy-label-critique",
      "slug": "illegitimacy-label-critique",
      "name": "Illegitimacy label critique",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/illegitimacy-label-critique/",
        "ja": "/ja/tools/illegitimacy-label-critique/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Audit narrator and character labels without endorsing discriminatory categories",
      "task": "Audit narrator and character labels without endorsing discriminatory categories",
      "searchIntent": {
        "primary": "Complete the task: Audit narrator and character labels without endorsing discriminatory categories",
        "queryHypothesis": "illegitimacy label critique",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to audit narrator and character labels without endorsing discriminatory categories?",
        "When should illegitimacy label critique be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Audit narrator and character labels without endorsing discriminatory categories",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Audit narrator and character labels without endorsing discriminatory categories. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-role-label-transition",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Audit narrator and character labels without endorsing discriminatory categories versus Replace temporary draft labels without losing scene references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Audit narrator and character labels without endorsing discriminatory categories versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-colony-imposed-labels",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Audit narrator and character labels without endorsing discriminatory categories versus Track institutional naming and resistance without endorsing dehumanization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Audit narrator and character labels without endorsing discriminatory categories",
        "outline": [
          "Explain the specific decision: Audit narrator and character labels without endorsing discriminatory categories",
          "Define the applicable contract and limits for Illegitimacy label critique",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Audit narrator and character labels without endorsing discriminatory categories; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Audit narrator and character labels without endorsing discriminatory categories",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:74",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-secret-address-slip",
      "slug": "family-secret-address-slip",
      "name": "Family secret address slip",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-secret-address-slip/",
        "ja": "/ja/tools/family-secret-address-slip/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Design a revealing form of address with a scene knowledge ledger",
      "task": "Design a revealing form of address with a scene knowledge ledger",
      "searchIntent": {
        "primary": "Complete the task: Design a revealing form of address with a scene knowledge ledger",
        "queryHypothesis": "family secret address slip",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a revealing form of address with a scene knowledge ledger?",
        "When should family secret address slip be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a revealing form of address with a scene knowledge ledger",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a revealing form of address with a scene knowledge ledger. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-found-family-address-system",
          "score": 0.16309523809523807,
          "sharedProfile": true,
          "difference": "Design a revealing form of address with a scene knowledge ledger versus Design elective kinship terms without implying blood relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Design a revealing form of address with a scene knowledge ledger versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reconciliation-name-return",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Design a revealing form of address with a scene knowledge ledger versus Make the return of a form of address legible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a revealing form of address with a scene knowledge ledger",
        "outline": [
          "Explain the specific decision: Design a revealing form of address with a scene knowledge ledger",
          "Define the applicable contract and limits for Family secret address slip",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a revealing form of address with a scene knowledge ledger; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a revealing form of address with a scene knowledge ledger",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:75",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-adoption-reveal-audit",
      "slug": "family-adoption-reveal-audit",
      "name": "Family adoption reveal audit",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-adoption-reveal-audit/",
        "ja": "/ja/tools/family-adoption-reveal-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Check earlier name references against the planned reveal",
      "task": "Check earlier name references against the planned reveal",
      "searchIntent": {
        "primary": "Complete the task: Check earlier name references against the planned reveal",
        "queryHypothesis": "family adoption reveal audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check earlier name references against the planned reveal?",
        "When should family adoption reveal audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check earlier name references against the planned reveal",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check earlier name references against the planned reveal. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Check earlier name references against the planned reveal versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-generational-confusion-audit",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Check earlier name references against the planned reveal versus Detect repeated name references in dated scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-time-traveler-cover-names",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Check earlier name references against the planned reveal versus Check alias references against story dates and social context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check earlier name references against the planned reveal",
        "outline": [
          "Explain the specific decision: Check earlier name references against the planned reveal",
          "Define the applicable contract and limits for Family adoption reveal audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check earlier name references against the planned reveal; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check earlier name references against the planned reveal",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:76",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-naming-bible",
      "slug": "family-naming-bible",
      "name": "Family naming bible",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-naming-bible/",
        "ja": "/ja/tools/family-naming-bible/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Export people, naming rules and exception decisions as one reference",
      "task": "Export people, naming rules and exception decisions as one reference",
      "searchIntent": {
        "primary": "Complete the task: Export people, naming rules and exception decisions as one reference",
        "queryHypothesis": "family naming bible",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export people, naming rules and exception decisions as one reference?",
        "When should family naming bible be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export people, naming rules and exception decisions as one reference",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export people, naming rules and exception decisions as one reference. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-setting-naming-bible",
          "score": 0.16309523809523807,
          "sharedProfile": false,
          "difference": "Export people, naming rules and exception decisions as one reference versus Link places, institutions and people without merging their naming grammars; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Export people, naming rules and exception decisions as one reference versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-family-generation",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Export people, naming rules and exception decisions as one reference versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export people, naming rules and exception decisions as one reference",
        "outline": [
          "Explain the specific decision: Export people, naming rules and exception decisions as one reference",
          "Define the applicable contract and limits for Family naming bible",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export people, naming rules and exception decisions as one reference; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export people, naming rules and exception decisions as one reference",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:77",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-generational-confusion-audit",
      "slug": "family-generational-confusion-audit",
      "name": "Family generational confusion audit",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-generational-confusion-audit/",
        "ja": "/ja/tools/family-generational-confusion-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Detect repeated name references in dated scenes",
      "task": "Detect repeated name references in dated scenes",
      "searchIntent": {
        "primary": "Complete the task: Detect repeated name references in dated scenes",
        "queryHypothesis": "family generational confusion audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect repeated name references in dated scenes?",
        "When should family generational confusion audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect repeated name references in dated scenes",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect repeated name references in dated scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Detect repeated name references in dated scenes versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reverse-outline",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Detect repeated name references in dated scenes versus Extract a timeline of identity references from authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-namesake-ancestor-chain",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Detect repeated name references in dated scenes versus Show repeated names with unambiguous narrative references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect repeated name references in dated scenes",
        "outline": [
          "Explain the specific decision: Detect repeated name references in dated scenes",
          "Define the applicable contract and limits for Family generational confusion audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect repeated name references in dated scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect repeated name references in dated scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:78",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-chosen-household-surname",
      "slug": "chosen-household-surname",
      "name": "Chosen household surname",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/chosen-household-surname/",
        "ja": "/ja/tools/chosen-household-surname/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Negotiate a shared fictional surname across unrelated members",
      "task": "Negotiate a shared fictional surname across unrelated members",
      "searchIntent": {
        "primary": "Complete the task: Negotiate a shared fictional surname across unrelated members",
        "queryHypothesis": "chosen household surname",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to negotiate a shared fictional surname across unrelated members?",
        "When should chosen household surname be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Negotiate a shared fictional surname across unrelated members",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Negotiate a shared fictional surname across unrelated members. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Negotiate a shared fictional surname across unrelated members versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-name-planner",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Negotiate a shared fictional surname across unrelated members versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-collective-identity-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Negotiate a shared fictional surname across unrelated members versus Name members whose society treats identity as shared; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Negotiate a shared fictional surname across unrelated members",
        "outline": [
          "Explain the specific decision: Negotiate a shared fictional surname across unrelated members",
          "Define the applicable contract and limits for Chosen household surname",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Negotiate a shared fictional surname across unrelated members; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Negotiate a shared fictional surname across unrelated members",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:79",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-cross-household-child-address",
      "slug": "cross-household-child-address",
      "name": "Cross household child address",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/cross-household-child-address/",
        "ja": "/ja/tools/cross-household-child-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Preserve different names used by guardians in separate homes",
      "task": "Preserve different names used by guardians in separate homes",
      "searchIntent": {
        "primary": "Complete the task: Preserve different names used by guardians in separate homes",
        "queryHypothesis": "cross household child address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve different names used by guardians in separate homes?",
        "When should cross household child address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve different names used by guardians in separate homes",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve different names used by guardians in separate homes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-household-servant-address",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Preserve different names used by guardians in separate homes versus Map speaker status and address without making a universal cultural claim; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-grandparent-address-network",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Preserve different names used by guardians in separate homes versus Keep different speakers' kin terms attached to the same person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-child-adult-address-shift",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Preserve different names used by guardians in separate homes versus Update a fictional relationship across a time skip; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve different names used by guardians in separate homes",
        "outline": [
          "Explain the specific decision: Preserve different names used by guardians in separate homes",
          "Define the applicable contract and limits for Cross household child address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve different names used by guardians in separate homes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve different names used by guardians in separate homes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:80",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-family-inheritance-exception",
      "slug": "family-inheritance-exception",
      "name": "Family inheritance exception",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/family-inheritance-exception/",
        "ja": "/ja/tools/family-inheritance-exception/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Document the story event that overrides the default surname rule",
      "task": "Document the story event that overrides the default surname rule",
      "searchIntent": {
        "primary": "Complete the task: Document the story event that overrides the default surname rule",
        "queryHypothesis": "family inheritance exception",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to document the story event that overrides the default surname rule?",
        "When should family inheritance exception be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Document the story event that overrides the default surname rule",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Document the story event that overrides the default surname rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-nickname-inheritance",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Document the story event that overrides the default surname rule versus Track a nickname transferred between relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inheritance-event-names",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Document the story event that overrides the default surname rule versus Apply surname and title rules after a succession event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-duplicate-exception",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Document the story event that overrides the default surname rule versus Permit an intentional duplicate with a stated story reason; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Document the story event that overrides the default surname rule",
        "outline": [
          "Explain the specific decision: Document the story event that overrides the default surname rule",
          "Define the applicable contract and limits for Family inheritance exception",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Document the story event that overrides the default surname rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Document the story event that overrides the default surname rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:81",
      "profileSource": "data/profiles.json#kinship"
    },
    {
      "id": "nw-ensemble-name-separation",
      "slug": "ensemble-name-separation",
      "name": "Ensemble name separation",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/ensemble-name-separation/",
        "ja": "/ja/tools/ensemble-name-separation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Optimize a supplied cast for distinct written and spoken forms",
      "task": "Optimize a supplied cast for distinct written and spoken forms",
      "searchIntent": {
        "primary": "Complete the task: Optimize a supplied cast for distinct written and spoken forms",
        "queryHypothesis": "ensemble name separation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to optimize a supplied cast for distinct written and spoken forms?",
        "When should ensemble name separation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "cast",
          "use": "Stable IDs, full forms, dialogue short forms and explicitly confirmed readings."
        },
        {
          "key": "sceneEdges",
          "use": "Weight pairs who appear together, rather than equally penalizing a distant cameo."
        },
        {
          "key": "lockedIds",
          "use": "Protect already published identities during repairs."
        },
        {
          "key": "weights",
          "use": "Expose visual, spelling and confirmed-sound heuristic weights."
        }
      ],
      "rules": [
        "Normalize comparison strings separately from original display.",
        "Compute spelling edit-distance ratio on grapheme clusters; do not call it perceptual certainty.",
        "Use pronunciation comparison only when both readings are confirmed; otherwise mark unavailable.",
        "Multiply pair risk by supplied cooccurrence and prominence weights.",
        "Offer repairs only for unlocked identities; retain intentional collisions with a reason.",
        "Compare initials separately from full names",
        "Compare dialogue short forms independently",
        "Never fabricate a reading for missing pronunciation",
        "Keep measured visual evidence separate from edit distance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Normalize comparison strings separately from original display.",
        "Compute spelling edit-distance ratio on grapheme clusters; do not call it perceptual certainty.",
        "Use pronunciation comparison only when both readings are confirmed; otherwise mark unavailable.",
        "Multiply pair risk by supplied cooccurrence and prominence weights.",
        "Offer repairs only for unlocked identities; retain intentional collisions with a reason.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "pair IDs and compared forms",
        "component risk values and weight formula",
        "scene-specific risk order",
        "smallest proposed changes",
        "unmeasured sound and typography warnings",
        "Initial collision reasons",
        "Short-form pair risk",
        "Reading collision or unavailable",
        "Visual review item"
      ],
      "capabilities": [
        "Rank conflicts by actual shared scenes.",
        "Simulate a single rename against every connected cast member before accepting it."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The task optimizes relationships between many established names rather than independently drawing plausible names.",
        "proposedDifferenceAxes": [
          "inputs",
          "evaluation",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-letters-versus-speech-address",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Optimize a supplied cast for distinct written and spoken forms versus Compare written and spoken relationship registers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-cue-name-system",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Optimize a supplied cast for distinct written and spoken forms versus Keep production cues distinct from spoken identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Optimize a supplied cast for distinct written and spoken forms versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A name becomes confusing through its neighbors and scene use.",
        "outline": [
          "Why a good individual name can fail in a cast",
          "Build the comparison from the names readers actually see",
          "A five-person harbor inquiry before and after one repair",
          "Read the heuristic formula and its blind spots",
          "Keep deliberate lookalikes without confusing everyone else"
        ],
        "story": "Fictional example: a harbor clerk hears two similar short names during a roll call and sends a repair order to the wrong boat. A revised scene uses a distinctive established surname for one worker while retaining both legal names.",
        "storyAnalysis": "The repair changes dialogue reference, not every identity. Compare with a full rename and explain why scene weighting makes the local repair sufficient.",
        "evidence": "Original five-person cooccurrence fixture and a disclosed deterministic heuristic; reader validation still pending.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/ensemble.md",
        "localizedBodies": {
          "en": "content/en/ensemble.md",
          "ja": "content/ja/ensemble.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Increasing one scene edge weight raises that pair's risk with all strings held constant.",
        "A locked cast member is never renamed.",
        "Two different full names sharing a short form produce a short-form warning.",
        "Missing pronunciation never produces a fabricated phonetic score.",
        "Different names with identical initials are flagged",
        "Different full names with one shared nickname are flagged",
        "An absent reading yields unavailable, not zero risk",
        "Unmeasured font similarity remains unmeasured"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:84",
      "profileSource": "data/profiles.json#ensemble",
      "absorbedModules": [
        {
          "sourceId": "nw-cast-initial-collision-repair",
          "input": "comparisonForms=initials",
          "rule": "Compare initials separately from full names",
          "output": "Initial collision reasons",
          "acceptance": "Different names with identical initials are flagged",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-cast-nickname-collision-repair",
          "input": "shortForms",
          "rule": "Compare dialogue short forms independently",
          "output": "Short-form pair risk",
          "acceptance": "Different full names with one shared nickname are flagged",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-cast-sound-collision-repair",
          "input": "confirmedReadings",
          "rule": "Never fabricate a reading for missing pronunciation",
          "output": "Reading collision or unavailable",
          "acceptance": "An absent reading yields unavailable, not zero risk",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-cast-visual-collision-repair",
          "input": "fontProofs",
          "rule": "Keep measured visual evidence separate from edit distance",
          "output": "Visual review item",
          "acceptance": "Unmeasured font similarity remains unmeasured",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "ensemble",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "cast",
          "label": [
            "Cast and approved forms",
            "人物と使用する表記"
          ],
          "type": "textarea",
          "default": "a | Aven Reed | Ave | ay-ven\nb | Arden Reed | Ave | ar-den\nc | Sela Morrow | Sela | seh-la",
          "help": [
            "ID | full name | dialogue short form | approved reading. Leave unknown readings blank.",
            "ID | 姓名 | 会話での呼び名 | 作者が確認した読み。不明な読みは空欄にします。"
          ]
        },
        {
          "key": "scenes",
          "label": [
            "Scene pair weights",
            "同じ場面に出る組み合わせ"
          ],
          "type": "textarea",
          "default": "a | b | 3\na | c | 1",
          "help": [
            "ID | ID | weight. Unspecified pairs use 1. These are editable editorial priorities.",
            "ID | ID | 重み。未指定は1。重みは作者が決める比較上の優先度です。"
          ]
        },
        {
          "key": "lockedIds",
          "label": [
            "Locked identity IDs",
            "固定する人物ID"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "fullWeight",
          "label": [
            "Full-form weight",
            "姓名の重み"
          ],
          "type": "number",
          "default": 0.5,
          "help": null
        },
        {
          "key": "shortWeight",
          "label": [
            "Short-form weight",
            "短称の重み"
          ],
          "type": "number",
          "default": 0.3,
          "help": null
        },
        {
          "key": "readingWeight",
          "label": [
            "Reading weight",
            "読みの重み"
          ],
          "type": "number",
          "default": 0.2,
          "help": null
        },
        {
          "key": "repairs",
          "label": [
            "Candidate rename simulations",
            "改名案のシミュレーション"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | proposed full form | proposed short form | approved reading",
            "ID | 改名案 | 短称案 | 確認済みの読み"
          ]
        },
        {
          "key": "intentionalPairs",
          "label": [
            "Intentional resemblance exceptions",
            "意図して残す類似"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | ID | reason; scores remain visible.",
            "ID | ID | 理由。数値を隠すことはありません。"
          ]
        },
        {
          "key": "proofFont",
          "label": [
            "Visual comparison font",
            "字形比較の書体"
          ],
          "type": "text",
          "default": "Georgia",
          "help": null
        },
        {
          "key": "visualWeight",
          "label": [
            "Supplied visual-observation weight",
            "入力した字形観察の重み"
          ],
          "type": "number",
          "default": 0,
          "help": null
        },
        {
          "key": "visualRatings",
          "label": [
            "Your visual observation · not objective scoring",
            "字形についての観察・客観的採点ではありません"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | ID | rating 0–1 | observation and conditions",
            "ID | ID | 評価0〜1 | 観察と条件"
          ]
        }
      ]
    },
    {
      "id": "nw-point-of-view-roster",
      "slug": "point-of-view-roster",
      "name": "Point of view roster",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/point-of-view-roster/",
        "ja": "/ja/tools/point-of-view-roster/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Keep viewpoint names distinct in chapter transitions",
      "task": "Keep viewpoint names distinct in chapter transitions",
      "searchIntent": {
        "primary": "Complete the task: Keep viewpoint names distinct in chapter transitions",
        "queryHypothesis": "point of view roster",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep viewpoint names distinct in chapter transitions?",
        "When should point of view roster be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep viewpoint names distinct in chapter transitions",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep viewpoint names distinct in chapter transitions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-military-unit-callsign-roster",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Keep viewpoint names distinct in chapter transitions versus Keep unit identifiers distinct from individual callsigns; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-suspect-name-roster",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Keep viewpoint names distinct in chapter transitions versus Distinguish suspects while preserving intentionally misleading associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-cue-name-system",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Keep viewpoint names distinct in chapter transitions versus Keep production cues distinct from spoken identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep viewpoint names distinct in chapter transitions",
        "outline": [
          "Explain the specific decision: Keep viewpoint names distinct in chapter transitions",
          "Define the applicable contract and limits for Point of view roster",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep viewpoint names distinct in chapter transitions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep viewpoint names distinct in chapter transitions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:85",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-scene-cooccurrence-name-audit",
      "slug": "scene-cooccurrence-name-audit",
      "name": "Scene cooccurrence name audit",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/scene-cooccurrence-name-audit/",
        "ja": "/ja/tools/scene-cooccurrence-name-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Prioritize collisions between characters who share scenes",
      "task": "Prioritize collisions between characters who share scenes",
      "searchIntent": {
        "primary": "Complete the task: Prioritize collisions between characters who share scenes",
        "queryHypothesis": "scene cooccurrence name audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prioritize collisions between characters who share scenes?",
        "When should scene cooccurrence name audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prioritize collisions between characters who share scenes",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prioritize collisions between characters who share scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-in-confession-scene",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Prioritize collisions between characters who share scenes versus Control who is identified by an emotionally loaded address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Prioritize collisions between characters who share scenes versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-confusion-severity-triage",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Prioritize collisions between characters who share scenes versus Prioritize reader reported collisions by actual scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prioritize collisions between characters who share scenes",
        "outline": [
          "Explain the specific decision: Prioritize collisions between characters who share scenes",
          "Define the applicable contract and limits for Scene cooccurrence name audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prioritize collisions between characters who share scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prioritize collisions between characters who share scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:86",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-dialogue-only-cast-test",
      "slug": "dialogue-only-cast-test",
      "name": "Dialogue only cast test",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/dialogue-only-cast-test/",
        "ja": "/ja/tools/dialogue-only-cast-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Identify speakers using names without descriptive tags",
      "task": "Identify speakers using names without descriptive tags",
      "searchIntent": {
        "primary": "Complete the task: Identify speakers using names without descriptive tags",
        "queryHypothesis": "dialogue only cast test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify speakers using names without descriptive tags?",
        "When should dialogue only cast test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify speakers using names without descriptive tags",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify speakers using names without descriptive tags. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-audio-cast-recognition-test",
          "score": 0.1476190476190476,
          "sharedProfile": false,
          "difference": "Identify speakers using names without descriptive tags versus Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-delayed-recall-test",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Identify speakers using names without descriptive tags versus Test recall after a defined reading passage and delay; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Identify speakers using names without descriptive tags versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify speakers using names without descriptive tags",
        "outline": [
          "Explain the specific decision: Identify speakers using names without descriptive tags",
          "Define the applicable contract and limits for Dialogue only cast test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify speakers using names without descriptive tags; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify speakers using names without descriptive tags",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:87",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-large-cast-introduction-pacing",
      "slug": "large-cast-introduction-pacing",
      "name": "Large cast introduction pacing",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/large-cast-introduction-pacing/",
        "ja": "/ja/tools/large-cast-introduction-pacing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Novel, serial-comic and game writers staging a large cast over multiple scenes.",
      "scenario": "Several unfamiliar labels arrive in one scene even though some belong to people the audience already knows; a writer needs a feasible introduction plan without moving protected story events.",
      "task": "Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets.",
      "searchIntent": {
        "primary": "Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets.",
        "queryHypothesis": "large cast introduction pacing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "How many new identities, rather than labels, arrive in this scene?",
        "Can an introduction move without violating a protected plot beat?"
      ],
      "inputs": [
        {
          "key": "scenes",
          "use": "Stable ordered scenes, explicit new-identity/new-label budgets and allowed event types."
        },
        {
          "key": "identities",
          "use": "Stable cast IDs and already-established identities at the start of the reviewed excerpt."
        },
        {
          "key": "introductions",
          "use": "Stable introduction events, identity/label form, earliest/latest scene, proposed scene and lock."
        },
        {
          "key": "dependencies",
          "use": "Explicit prior events or identity-link prerequisites; no inferred reader knowledge."
        },
        {
          "key": "operation",
          "use": "Audit the supplied placement or request a bounded alternative schedule."
        }
      ],
      "rules": [
        "Count newly established identities separately from newly introduced forms of known identities.",
        "Treat budgets as author-selected editorial limits, not measured reader-memory capacity.",
        "Never move locked events or move an event outside its authored window.",
        "A missing identity/link prerequisite is a concrete unsatisfied dependency, not proof of reader confusion.",
        "Detect cycles and unknown references before search.",
        "Use bounded search; an exhausted bound is not proof that no valid schedule exists.",
        "Preserve original placement beside any proposed schedule for an explicit decision."
      ],
      "requiredData": [
        {
          "description": "Original excerpt-level cast/scene fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Author-declared scene order and exposure dependencies, without participant data",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Count newly established identities separately from newly introduced forms of known identities.",
        "Treat budgets as author-selected editorial limits, not measured reader-memory capacity.",
        "Never move locked events or move an event outside its authored window.",
        "A missing identity/link prerequisite is a concrete unsatisfied dependency, not proof of reader confusion.",
        "Detect cycles and unknown references before search.",
        "Use bounded search; an exhausted bound is not proof that no valid schedule exists.",
        "Preserve original placement beside any proposed schedule for an explicit decision."
      ],
      "outputs": [
        "Per-scene new-identity/new-label inventory",
        "Dependency and over-budget diagnostics",
        "A proposed placement diff and locked-event proof",
        "Private scheduling handoff, without automatically rewriting a manuscript"
      ],
      "capabilities": [
        "Separate five new labels from five newly encountered people.",
        "Find a valid alternative introduction order while preserving locked story beats, or show the specific unfilled constraints."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The main task is constrained placement of introduction events over narrative order. Similarity checking compares names already supplied, while an alias knowledge view checks what is known at one point; neither schedules a set of introductions under scene capacity and prerequisites.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "ensemble-name-separation",
          "difference": "This workbench schedules first identity/label exposure and required links across scenes, reports unavailable placements and budgets, and keeps author-protected events fixed. It does not infer human memory, rewrite prose or rank names by similarity."
        }
      },
      "nearestTools": [
        {
          "id": "nw-cast-introduction-comprehension",
          "score": 0.1670833333333333,
          "sharedProfile": false,
          "difference": "Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets. versus Measure who readers think was introduced after a scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-vertical-comic-name-pacing",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets. versus Schedule first name displays across scrolling episode beats; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.10263157894736842,
          "sharedProfile": true,
          "difference": "Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets. versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "An introduction plan should track what the audience is asked to learn, while leaving story-event authority with the writer.",
        "outline": [
          "The rehearsal with more labels than new people",
          "Define the excerpt’s starting knowledge",
          "Put an introduction inside a real scene window",
          "Compare an alternative without rewriting a protected reveal",
          "Read an editorial budget as a choice"
        ],
        "story": "A company prepares a public demonstration: several returning people use task labels, while a newcomer must be linked to a first action. The sequence is revised around a protected demonstration beat, not by renaming every participant.",
        "storyAnalysis": "Changing all labels does not move their exposure. A better schedule can reduce an authored burst while preserving a necessary reveal; actual reader comprehension still needs a separate observation.",
        "evidence": "Original scene-order examples and constraint-search fixtures; no measured reading study.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/introductions.md",
        "localizedBodies": {
          "en": "content/en/introductions.md",
          "ja": "content/ja/introductions.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Changing a scene budget changes feasibility or the reported violations.",
        "A locked event never moves in the proposed schedule.",
        "A linked alias counts as a new label without inventing a new person.",
        "Cycles and missing prerequisite IDs fail explicitly.",
        "Search-limit and proven-infeasible states are distinct.",
        "No output claims a measured memory load or reader comprehension outcome."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:88",
      "profileSource": "data/profiles.json#ensemble",
      "specBatch": "batch-04",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Explicit task states, scoped rules, traceable alternatives and bilingual original content; no time/cost estimate invented."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-localized-ensemble-introduction-order",
          "input": "One edition: author-ordered scenes with separate new-person/new-association budgets, explicit established forms, introduction/reminder events, protected placements and prerequisite gaps.",
          "rule": "Treat exact person/form associations separately from people; do not infer reader knowledge, transliteration equivalence or prose links. Search bounded finite placements without silently changing inputs.",
          "output": "Original and complete proposed exposure tables, placement diff, finite-search state and private schedule handoff.",
          "acceptance": "The default scene has one new person and four associations; applying a feasible proposal moves only two event placements. Locked placements, stale inputs and exhausted search bounds retain their distinct behavior. No cross-edition or clue certification.",
          "evidence": [
            "PACE-01",
            "PACE-02",
            "PACE-03",
            "PACE-10",
            "PACE-11",
            "PACE-14",
            "PACE-HTML",
            "reports/introduction-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "introductions",
        "engineFiles": [
          "web/introduction-schedule.mjs",
          "web/introduction-view.mjs",
          "web/introduction-plan-ui.mjs",
          "web/introduction-worker.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/introduction.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "scenes",
          "label": [
            "Scenes in narrative order · JSON",
            "物語順の場面・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"s1\",\n    \"label\": \"Opening briefing\",\n    \"identityBudget\": 1,\n    \"labelBudget\": 1,\n    \"allowedKinds\": [\n      \"identity\",\n      \"label\",\n      \"reminder\"\n    ]\n  },\n  {\n    \"id\": \"s2\",\n    \"label\": \"Public demonstration\",\n    \"identityBudget\": 1,\n    \"labelBudget\": 2,\n    \"allowedKinds\": [\n      \"identity\",\n      \"label\",\n      \"reminder\"\n    ]\n  },\n  {\n    \"id\": \"s3\",\n    \"label\": \"After the test\",\n    \"identityBudget\": 0,\n    \"labelBudget\": 2,\n    \"allowedKinds\": [\n      \"label\",\n      \"reminder\"\n    ]\n  },\n  {\n    \"id\": \"s4\",\n    \"label\": \"Quiet return\",\n    \"identityBudget\": 0,\n    \"labelBudget\": 0,\n    \"allowedKinds\": [\n      \"reminder\"\n    ]\n  }\n]",
          "help": [
            "Array order is narrative order. Budgets 0–40 count new people and exact person/form associations, not memory capacity. allowedKinds can be empty.",
            "配列順が物語順です。0〜40の予算は新しい人物と正確な人物・表記の対応を数え、記憶力を測りません。allowedKindsは空にもできます。"
          ],
          "maxLength": 150000
        },
        {
          "key": "identities",
          "label": [
            "Starting audience knowledge · JSON",
            "開始時に読者へ示した人物・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"dena\",\n    \"name\": \"Dena Quill\",\n    \"knownAtStart\": true,\n    \"knownForms\": [\n      \"Dena Quill\",\n      \"Dena\"\n    ]\n  },\n  {\n    \"id\": \"olek\",\n    \"name\": \"Olek Fen\",\n    \"knownAtStart\": true,\n    \"knownForms\": [\n      \"Olek Fen\"\n    ]\n  },\n  {\n    \"id\": \"pella\",\n    \"name\": \"Pella Moss\",\n    \"knownAtStart\": false,\n    \"knownForms\": []\n  }\n]",
          "help": [
            "id/name/knownAtStart/knownForms. These are authored declarations, not observed reader knowledge. An unknown person has no established forms.",
            "id/name/knownAtStart/knownForms。作者の宣言で、読者の知識の観測ではありません。未紹介の人物のknownFormsは空です。"
          ],
          "maxLength": 150000
        },
        {
          "key": "introductions",
          "label": [
            "Introduction and reminder events · JSON",
            "紹介と再提示の項目・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"dena-role\",\n    \"person\": \"dena\",\n    \"form\": \"Inspector Quill\",\n    \"kind\": \"label\",\n    \"earliest\": \"s1\",\n    \"latest\": \"s3\",\n    \"proposed\": \"s2\",\n    \"locked\": false\n  },\n  {\n    \"id\": \"olek-short\",\n    \"person\": \"olek\",\n    \"form\": \"Olek\",\n    \"kind\": \"label\",\n    \"earliest\": \"s1\",\n    \"latest\": \"s3\",\n    \"proposed\": \"s2\",\n    \"locked\": false\n  },\n  {\n    \"id\": \"pella-first\",\n    \"person\": \"pella\",\n    \"form\": \"Pella Moss\",\n    \"kind\": \"identity\",\n    \"earliest\": \"s1\",\n    \"latest\": \"s3\",\n    \"proposed\": \"s2\",\n    \"locked\": true\n  },\n  {\n    \"id\": \"pel-short\",\n    \"person\": \"pella\",\n    \"form\": \"Pel\",\n    \"kind\": \"label\",\n    \"earliest\": \"s1\",\n    \"latest\": \"s3\",\n    \"proposed\": \"s2\",\n    \"locked\": false\n  },\n  {\n    \"id\": \"dena-return\",\n    \"person\": \"dena\",\n    \"form\": \"Dena\",\n    \"kind\": \"reminder\",\n    \"earliest\": \"s3\",\n    \"latest\": \"s4\",\n    \"proposed\": \"s4\",\n    \"locked\": false\n  }\n]",
          "help": [
            "Each event has a stable id, person, exact form, kind, earliest/latest scene, proposed scene or null, and locked. Row order is not prose order: prerequisite order is shown separately. label assumes the person is already linked in the story; unlinked aliases are outside this model.",
            "各項目はid、person、正確なform、kind、earliest/latest、proposedかnull、lockedを持ちます。配列順は本文順ではなく、前提の順を別に示します。labelは人物との関連を本文で示す前提です。未接続の別名は対象外です。"
          ],
          "maxLength": 150000
        },
        {
          "key": "dependencies",
          "label": [
            "Authored prerequisites · JSON",
            "作者が指定する前後条件・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"before\": \"pella-first\",\n    \"after\": \"pel-short\",\n    \"minScenes\": 1\n  }\n]",
          "help": [
            "before/after/minScenes. Zero allows one scene but still requires the displayed event order. Unknown people and reminders also get explicit automatic prerequisites; nothing is inferred from prose.",
            "before/after/minScenes。0なら同じ場面ですが表示する項目順に従います。未紹介の人物と再提示にも明示した自動前提が付き、本文から意味を推測しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "operation",
          "label": [
            "Operation",
            "操作"
          ],
          "type": "select",
          "default": "plan",
          "help": null,
          "options": [
            [
              "plan",
              [
                "Find a feasible proposal",
                "実行できる配置案を探す"
              ]
            ],
            [
              "audit",
              [
                "Audit current placement only",
                "現在の配置だけを調べる"
              ]
            ]
          ]
        },
        {
          "key": "nodeLimit",
          "label": [
            "Search bound · candidate attempts, 1–20000",
            "探索上限・候補試行数1〜20000"
          ],
          "type": "number",
          "default": 5000,
          "help": [
            "The first feasible result prefers current placements; it is not a minimum-move guarantee. Reaching this bound is not proof of no solution.",
            "現在の配置を優先して最初の実行可能な案を返し、最小移動は保証しません。上限到達は解なしの証明ではありません。"
          ]
        }
      ]
    },
    {
      "id": "nw-rival-character-name-pairing",
      "slug": "rival-character-name-pairing",
      "name": "Rival character name pairing",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/rival-character-name-pairing/",
        "ja": "/ja/tools/rival-character-name-pairing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Express opposition without making names indistinguishable",
      "task": "Express opposition without making names indistinguishable",
      "searchIntent": {
        "primary": "Complete the task: Express opposition without making names indistinguishable",
        "queryHypothesis": "rival character name pairing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to express opposition without making names indistinguishable?",
        "When should rival character name pairing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Express opposition without making names indistinguishable",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Express opposition without making names indistinguishable. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rival-respect-address-arc",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Express opposition without making names indistinguishable versus Encode changes in mutual regard without changing legal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prophetic-name-restraint",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Express opposition without making names indistinguishable versus Design an ambiguous epithet without making prophecy self proving; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-household-servant-address",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Express opposition without making names indistinguishable versus Map speaker status and address without making a universal cultural claim; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Express opposition without making names indistinguishable",
        "outline": [
          "Explain the specific decision: Express opposition without making names indistinguishable",
          "Define the applicable contract and limits for Rival character name pairing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Express opposition without making names indistinguishable; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Express opposition without making names indistinguishable",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:89",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-romantic-lead-name-pairing",
      "slug": "romantic-lead-name-pairing",
      "name": "Romantic lead name pairing",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/romantic-lead-name-pairing/",
        "ja": "/ja/tools/romantic-lead-name-pairing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Test paired references, initials and accidental rhyme",
      "task": "Test paired references, initials and accidental rhyme",
      "searchIntent": {
        "primary": "Complete the task: Test paired references, initials and accidental rhyme",
        "queryHypothesis": "romantic lead name pairing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test paired references, initials and accidental rhyme?",
        "When should romantic lead name pairing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test paired references, initials and accidental rhyme",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test paired references, initials and accidental rhyme. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-former-name-reference-policy",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test paired references, initials and accidental rhyme versus Mark necessary historical references and avoid accidental exposure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Test paired references, initials and accidental rhyme versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rival-character-name-pairing",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Test paired references, initials and accidental rhyme versus Express opposition without making names indistinguishable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test paired references, initials and accidental rhyme",
        "outline": [
          "Explain the specific decision: Test paired references, initials and accidental rhyme",
          "Define the applicable contract and limits for Romantic lead name pairing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test paired references, initials and accidental rhyme; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test paired references, initials and accidental rhyme",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:90",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-love-triangle-name-clarity",
      "slug": "love-triangle-name-clarity",
      "name": "Love triangle name clarity",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/love-triangle-name-clarity/",
        "ja": "/ja/tools/love-triangle-name-clarity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Distinguish three leads in rapidly alternating dialogue",
      "task": "Distinguish three leads in rapidly alternating dialogue",
      "searchIntent": {
        "primary": "Complete the task: Distinguish three leads in rapidly alternating dialogue",
        "queryHypothesis": "love triangle name clarity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish three leads in rapidly alternating dialogue?",
        "When should love triangle name clarity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish three leads in rapidly alternating dialogue",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish three leads in rapidly alternating dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rpg-companion-name-roster",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Distinguish three leads in rapidly alternating dialogue versus Distinguish companions in dialogue and party UI; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Distinguish three leads in rapidly alternating dialogue versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Distinguish three leads in rapidly alternating dialogue versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish three leads in rapidly alternating dialogue",
        "outline": [
          "Explain the specific decision: Distinguish three leads in rapidly alternating dialogue",
          "Define the applicable contract and limits for Love triangle name clarity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish three leads in rapidly alternating dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish three leads in rapidly alternating dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:91",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-mentor-apprentice-name-echo",
      "slug": "mentor-apprentice-name-echo",
      "name": "Mentor apprentice name echo",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/mentor-apprentice-name-echo/",
        "ja": "/ja/tools/mentor-apprentice-name-echo/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Control a deliberate echo without suggesting blood relation",
      "task": "Control a deliberate echo without suggesting blood relation",
      "searchIntent": {
        "primary": "Complete the task: Control a deliberate echo without suggesting blood relation",
        "queryHypothesis": "mentor apprentice name echo",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to control a deliberate echo without suggesting blood relation?",
        "When should mentor apprentice name echo be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Control a deliberate echo without suggesting blood relation",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Control a deliberate echo without suggesting blood relation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-stutter-name-policy",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Control a deliberate echo without suggesting blood relation versus Record deliberate performance choices without treating disability as a naming trope; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-found-family-address-system",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Control a deliberate echo without suggesting blood relation versus Design elective kinship terms without implying blood relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-guild-apprentice-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Control a deliberate echo without suggesting blood relation versus Track entry, mastery and departure forms under authored guild rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Control a deliberate echo without suggesting blood relation",
        "outline": [
          "Explain the specific decision: Control a deliberate echo without suggesting blood relation",
          "Define the applicable contract and limits for Mentor apprentice name echo",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Control a deliberate echo without suggesting blood relation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Control a deliberate echo without suggesting blood relation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:92",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-foil-character-name-balance",
      "slug": "foil-character-name-balance",
      "name": "Foil character name balance",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/foil-character-name-balance/",
        "ja": "/ja/tools/foil-character-name-balance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Compare controlled parallels against conflicting traits",
      "task": "Compare controlled parallels against conflicting traits",
      "searchIntent": {
        "primary": "Complete the task: Compare controlled parallels against conflicting traits",
        "queryHypothesis": "foil character name balance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare controlled parallels against conflicting traits?",
        "When should foil character name balance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare controlled parallels against conflicting traits",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare controlled parallels against conflicting traits. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-font-glyph-audit",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare controlled parallels against conflicting traits versus Verify approved name characters against actual font coverage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-first-impression",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Compare controlled parallels against conflicting traits versus Compare intended characterization against reader supplied impressions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Compare controlled parallels against conflicting traits versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare controlled parallels against conflicting traits",
        "outline": [
          "Explain the specific decision: Compare controlled parallels against conflicting traits",
          "Define the applicable contract and limits for Foil character name balance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare controlled parallels against conflicting traits; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare controlled parallels against conflicting traits",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:93",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-doppelganger-cast-labeling",
      "slug": "doppelganger-cast-labeling",
      "name": "Doppelganger cast labeling",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/doppelganger-cast-labeling/",
        "ja": "/ja/tools/doppelganger-cast-labeling/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Maintain intended likeness while preserving reader orientation",
      "task": "Maintain intended likeness while preserving reader orientation",
      "searchIntent": {
        "primary": "Complete the task: Maintain intended likeness while preserving reader orientation",
        "queryHypothesis": "doppelganger cast labeling",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain intended likeness while preserving reader orientation?",
        "When should doppelganger cast labeling be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain intended likeness while preserving reader orientation",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain intended likeness while preserving reader orientation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-refuses-name-disclosure",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Maintain intended likeness while preserving reader orientation versus Preserve agency while maintaining reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-forgotten-by-everyone",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Maintain intended likeness while preserving reader orientation versus Preserve reader orientation while characters lose references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Maintain intended likeness while preserving reader orientation versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain intended likeness while preserving reader orientation",
        "outline": [
          "Explain the specific decision: Maintain intended likeness while preserving reader orientation",
          "Define the applicable contract and limits for Doppelganger cast labeling",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain intended likeness while preserving reader orientation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain intended likeness while preserving reader orientation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:94",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-identical-twin-scene-labels",
      "slug": "identical-twin-scene-labels",
      "name": "Identical twin scene labels",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/identical-twin-scene-labels/",
        "ja": "/ja/tools/identical-twin-scene-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Track knowledge of identity across a mistaken identity scene",
      "task": "Track knowledge of identity across a mistaken identity scene",
      "searchIntent": {
        "primary": "Complete the task: Track knowledge of identity across a mistaken identity scene",
        "queryHypothesis": "identical twin scene labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track knowledge of identity across a mistaken identity scene?",
        "When should identical twin scene labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track knowledge of identity across a mistaken identity scene",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track knowledge of identity across a mistaken identity scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-inherited-secret-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track knowledge of identity across a mistaken identity scene versus Track knowledge transfer and failures across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track knowledge of identity across a mistaken identity scene versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track knowledge of identity across a mistaken identity scene versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track knowledge of identity across a mistaken identity scene",
        "outline": [
          "Explain the specific decision: Track knowledge of identity across a mistaken identity scene",
          "Define the applicable contract and limits for Identical twin scene labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track knowledge of identity across a mistaken identity scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track knowledge of identity across a mistaken identity scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:95",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-character-team-naming-hierarchy",
      "slug": "character-team-naming-hierarchy",
      "name": "Character team naming hierarchy",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/character-team-naming-hierarchy/",
        "ja": "/ja/tools/character-team-naming-hierarchy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Separate individual names, role labels and collective references",
      "task": "Separate individual names, role labels and collective references",
      "searchIntent": {
        "primary": "Complete the task: Separate individual names, role labels and collective references",
        "queryHypothesis": "character team naming hierarchy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate individual names, role labels and collective references?",
        "When should character team naming hierarchy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate individual names, role labels and collective references",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate individual names, role labels and collective references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate individual names, role labels and collective references versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hive-member-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate individual names, role labels and collective references versus Distinguish collective reference from individual agents; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-occupation-name-separation",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate individual names, role labels and collective references versus Keep role titles from replacing individual identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate individual names, role labels and collective references",
        "outline": [
          "Explain the specific decision: Separate individual names, role labels and collective references",
          "Define the applicable contract and limits for Character team naming hierarchy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate individual names, role labels and collective references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate individual names, role labels and collective references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:96",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-school-class-roster-design",
      "slug": "school-class-roster-design",
      "name": "School class roster design",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/school-class-roster-design/",
        "ja": "/ja/tools/school-class-roster-design/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Assign background and recurring names with classroom reference tests",
      "task": "Assign background and recurring names with classroom reference tests",
      "searchIntent": {
        "primary": "Complete the task: Assign background and recurring names with classroom reference tests",
        "queryHypothesis": "school class roster design",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to assign background and recurring names with classroom reference tests?",
        "When should school class roster design be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Assign background and recurring names with classroom reference tests",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Assign background and recurring names with classroom reference tests. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-school-desk-labels",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Assign background and recurring names with classroom reference tests versus Coordinate seat maps, names and classroom scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-faction-address-rules",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Assign background and recurring names with classroom reference tests versus Assign titles and personal names according to fictional memberships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-guest-character-names",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Assign background and recurring names with classroom reference tests versus Prevent conflict with archived recurring characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Assign background and recurring names with classroom reference tests",
        "outline": [
          "Explain the specific decision: Assign background and recurring names with classroom reference tests",
          "Define the applicable contract and limits for School class roster design",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Assign background and recurring names with classroom reference tests; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Assign background and recurring names with classroom reference tests",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:97",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-workplace-ensemble-name-map",
      "slug": "workplace-ensemble-name-map",
      "name": "Workplace ensemble name map",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/workplace-ensemble-name-map/",
        "ja": "/ja/tools/workplace-ensemble-name-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Model surname, title and first name use by colleague relationship",
      "task": "Model surname, title and first name use by colleague relationship",
      "searchIntent": {
        "primary": "Complete the task: Model surname, title and first name use by colleague relationship",
        "queryHypothesis": "workplace ensemble name map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model surname, title and first name use by colleague relationship?",
        "When should workplace ensemble name map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model surname, title and first name use by colleague relationship",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model surname, title and first name use by colleague relationship. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Model surname, title and first name use by colleague relationship versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-consent-map",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Model surname, title and first name use by colleague relationship versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-court-ensemble-address-map",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Model surname, title and first name use by colleague relationship versus Disambiguate personal names, offices and ranked titles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model surname, title and first name use by colleague relationship",
        "outline": [
          "Explain the specific decision: Model surname, title and first name use by colleague relationship",
          "Define the applicable contract and limits for Workplace ensemble name map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model surname, title and first name use by colleague relationship; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model surname, title and first name use by colleague relationship",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:98",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-expedition-party-names",
      "slug": "expedition-party-names",
      "name": "Expedition party names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/expedition-party-names/",
        "ja": "/ja/tools/expedition-party-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Differentiate voice calls under noisy travel scenes",
      "task": "Differentiate voice calls under noisy travel scenes",
      "searchIntent": {
        "primary": "Complete the task: Differentiate voice calls under noisy travel scenes",
        "queryHypothesis": "expedition party names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to differentiate voice calls under noisy travel scenes?",
        "When should expedition party names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Differentiate voice calls under noisy travel scenes",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Differentiate voice calls under noisy travel scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-radio-call-name-differentiation",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Differentiate voice calls under noisy travel scenes versus Check names under author supplied noisy audio examples; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-party-list-name-disambiguation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Differentiate voice calls under noisy travel scenes versus Distinguish shortened names in a compact party display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Differentiate voice calls under noisy travel scenes versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Differentiate voice calls under noisy travel scenes",
        "outline": [
          "Explain the specific decision: Differentiate voice calls under noisy travel scenes",
          "Define the applicable contract and limits for Expedition party names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Differentiate voice calls under noisy travel scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Differentiate voice calls under noisy travel scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:99",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-heist-crew-identity-matrix",
      "slug": "heist-crew-identity-matrix",
      "name": "Heist crew identity matrix",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/heist-crew-identity-matrix/",
        "ja": "/ja/tools/heist-crew-identity-matrix/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Align crew handles with public and private identities",
      "task": "Align crew handles with public and private identities",
      "searchIntent": {
        "primary": "Complete the task: Align crew handles with public and private identities",
        "queryHypothesis": "heist crew identity matrix",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to align crew handles with public and private identities?",
        "When should heist crew identity matrix be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Align crew handles with public and private identities",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Align crew handles with public and private identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Align crew handles with public and private identities versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Align crew handles with public and private identities versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Align crew handles with public and private identities versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Align crew handles with public and private identities",
        "outline": [
          "Explain the specific decision: Align crew handles with public and private identities",
          "Define the applicable contract and limits for Heist crew identity matrix",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Align crew handles with public and private identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Align crew handles with public and private identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:100",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-court-ensemble-address-map",
      "slug": "court-ensemble-address-map",
      "name": "Court ensemble address map",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/court-ensemble-address-map/",
        "ja": "/ja/tools/court-ensemble-address-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Disambiguate personal names, offices and ranked titles",
      "task": "Disambiguate personal names, offices and ranked titles",
      "searchIntent": {
        "primary": "Complete the task: Disambiguate personal names, offices and ranked titles",
        "queryHypothesis": "court ensemble address map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to disambiguate personal names, offices and ranked titles?",
        "When should court ensemble address map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Disambiguate personal names, offices and ranked titles",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Disambiguate personal names, offices and ranked titles. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-faction-address-rules",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Disambiguate personal names, offices and ranked titles versus Assign titles and personal names according to fictional memberships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Disambiguate personal names, offices and ranked titles versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stepfamily-address-map",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Disambiguate personal names, offices and ranked titles versus Distinguish household membership from inherited naming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Disambiguate personal names, offices and ranked titles",
        "outline": [
          "Explain the specific decision: Disambiguate personal names, offices and ranked titles",
          "Define the applicable contract and limits for Court ensemble address map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Disambiguate personal names, offices and ranked titles; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Disambiguate personal names, offices and ranked titles",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:101",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-rebel-cell-identity-separation",
      "slug": "rebel-cell-identity-separation",
      "name": "Rebel cell identity separation",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/rebel-cell-identity-separation/",
        "ja": "/ja/tools/rebel-cell-identity-separation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Avoid accidental leakage between cells in story dialogue",
      "task": "Avoid accidental leakage between cells in story dialogue",
      "searchIntent": {
        "primary": "Complete the task: Avoid accidental leakage between cells in story dialogue",
        "queryHypothesis": "rebel cell identity separation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid accidental leakage between cells in story dialogue?",
        "When should rebel cell identity separation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid accidental leakage between cells in story dialogue",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid accidental leakage between cells in story dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rebel-cell-codenames",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Avoid accidental leakage between cells in story dialogue versus Design a fiction specific namespace and permitted knowledge graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-podcast-fiction-guest-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid accidental leakage between cells in story dialogue versus Avoid confusion between returning and one episode characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-program-character-namespace",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid accidental leakage between cells in story dialogue versus Avoid collisions between display names and technical keys; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid accidental leakage between cells in story dialogue",
        "outline": [
          "Explain the specific decision: Avoid accidental leakage between cells in story dialogue",
          "Define the applicable contract and limits for Rebel cell identity separation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid accidental leakage between cells in story dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid accidental leakage between cells in story dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:102",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-village-ensemble-name-ecology",
      "slug": "village-ensemble-name-ecology",
      "name": "Village ensemble name ecology",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/village-ensemble-name-ecology/",
        "ja": "/ja/tools/village-ensemble-name-ecology/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Balance local patterns with individual distinction",
      "task": "Balance local patterns with individual distinction",
      "searchIntent": {
        "primary": "Complete the task: Balance local patterns with individual distinction",
        "queryHypothesis": "village ensemble name ecology",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to balance local patterns with individual distinction?",
        "When should village ensemble name ecology be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Balance local patterns with individual distinction",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Balance local patterns with individual distinction. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-village-surname-ecology",
          "score": 0.2472222222222222,
          "sharedProfile": false,
          "difference": "Balance local patterns with individual distinction versus Design personal surnames from a bounded fictional local history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-migration-between-towns",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Balance local patterns with individual distinction versus Preserve individual names while updating local forms of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Balance local patterns with individual distinction versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Balance local patterns with individual distinction",
        "outline": [
          "Explain the specific decision: Balance local patterns with individual distinction",
          "Define the applicable contract and limits for Village ensemble name ecology",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Balance local patterns with individual distinction; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Balance local patterns with individual distinction",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:103",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-apartment-cast-door-labels",
      "slug": "apartment-cast-door-labels",
      "name": "Apartment cast door labels",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/apartment-cast-door-labels/",
        "ja": "/ja/tools/apartment-cast-door-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Match visible labels to residents and concealed occupants",
      "task": "Match visible labels to residents and concealed occupants",
      "searchIntent": {
        "primary": "Complete the task: Match visible labels to residents and concealed occupants",
        "queryHypothesis": "apartment cast door labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match visible labels to residents and concealed occupants?",
        "When should apartment cast door labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Match visible labels to residents and concealed occupants",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Match visible labels to residents and concealed occupants. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Match visible labels to residents and concealed occupants versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-subtitle-romanization-continuity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Match visible labels to residents and concealed occupants versus Match visible Latin spellings to the pronunciation bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Match visible labels to residents and concealed occupants versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Match visible labels to residents and concealed occupants",
        "outline": [
          "Explain the specific decision: Match visible labels to residents and concealed occupants",
          "Define the applicable contract and limits for Apartment cast door labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Match visible labels to residents and concealed occupants; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Match visible labels to residents and concealed occupants",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:104",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-tournament-bracket-name-clarity",
      "slug": "tournament-bracket-name-clarity",
      "name": "Tournament bracket name clarity",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/tournament-bracket-name-clarity/",
        "ja": "/ja/tools/tournament-bracket-name-clarity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Prevent abbreviated names from colliding in bracket layouts",
      "task": "Prevent abbreviated names from colliding in bracket layouts",
      "searchIntent": {
        "primary": "Complete the task: Prevent abbreviated names from colliding in bracket layouts",
        "queryHypothesis": "tournament bracket name clarity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent abbreviated names from colliding in bracket layouts?",
        "When should tournament bracket name clarity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent abbreviated names from colliding in bracket layouts",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent abbreviated names from colliding in bracket layouts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-guest-character-names",
          "score": 0.08125,
          "sharedProfile": true,
          "difference": "Prevent abbreviated names from colliding in bracket layouts versus Prevent conflict with archived recurring characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-actor-character-credit-mapping",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Prevent abbreviated names from colliding in bracket layouts versus Prevent performer names from being confused with character aliases; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-cast-registry",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Prevent abbreviated names from colliding in bracket layouts versus Prevent collisions across sessions and locations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent abbreviated names from colliding in bracket layouts",
        "outline": [
          "Explain the specific decision: Prevent abbreviated names from colliding in bracket layouts",
          "Define the applicable contract and limits for Tournament bracket name clarity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent abbreviated names from colliding in bracket layouts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent abbreviated names from colliding in bracket layouts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:105",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-prison-ensemble-naming",
      "slug": "prison-ensemble-naming",
      "name": "Prison ensemble naming",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/prison-ensemble-naming/",
        "ja": "/ja/tools/prison-ensemble-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Separate institutional labels from self and peer chosen names",
      "task": "Separate institutional labels from self and peer chosen names",
      "searchIntent": {
        "primary": "Complete the task: Separate institutional labels from self and peer chosen names",
        "queryHypothesis": "prison ensemble naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate institutional labels from self and peer chosen names?",
        "When should prison ensemble naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate institutional labels from self and peer chosen names",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate institutional labels from self and peer chosen names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate institutional labels from self and peer chosen names versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-assigned-number-resistance",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate institutional labels from self and peer chosen names versus Track adoption and rejection of institutional numeric labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate institutional labels from self and peer chosen names versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate institutional labels from self and peer chosen names",
        "outline": [
          "Explain the specific decision: Separate institutional labels from self and peer chosen names",
          "Define the applicable contract and limits for Prison ensemble naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate institutional labels from self and peer chosen names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate institutional labels from self and peer chosen names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:106",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-hospital-drama-staff-references",
      "slug": "hospital-drama-staff-references",
      "name": "Hospital drama staff references",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/hospital-drama-staff-references/",
        "ja": "/ja/tools/hospital-drama-staff-references/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Distinguish staff roles, surnames and patient address",
      "task": "Distinguish staff roles, surnames and patient address",
      "searchIntent": {
        "primary": "Complete the task: Distinguish staff roles, surnames and patient address",
        "queryHypothesis": "hospital drama staff references",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish staff roles, surnames and patient address?",
        "When should hospital drama staff references be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish staff roles, surnames and patient address",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish staff roles, surnames and patient address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-traveling-caravan-member-references",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Distinguish staff roles, surnames and patient address versus Resolve personal names, duties and group roles in dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-team-callsign-dialogue",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish staff roles, surnames and patient address versus Keep operational and personal address contexts separate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Distinguish staff roles, surnames and patient address versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish staff roles, surnames and patient address",
        "outline": [
          "Explain the specific decision: Distinguish staff roles, surnames and patient address",
          "Define the applicable contract and limits for Hospital drama staff references",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish staff roles, surnames and patient address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish staff roles, surnames and patient address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:107",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-ship-crew-watch-names",
      "slug": "ship-crew-watch-names",
      "name": "Ship crew watch names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/ship-crew-watch-names/",
        "ja": "/ja/tools/ship-crew-watch-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Test names under watch rotations and role changes",
      "task": "Test names under watch rotations and role changes",
      "searchIntent": {
        "primary": "Complete the task: Test names under watch rotations and role changes",
        "queryHypothesis": "ship crew watch names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test names under watch rotations and role changes?",
        "When should ship crew watch names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test names under watch rotations and role changes",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test names under watch rotations and role changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-arc-emotional-continuity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test names under watch rotations and role changes versus Test whether naming changes match the surrounding character behavior; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-ship-character-name",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Test names under watch rotations and role changes versus Separate vessel registry from the onboard intelligence's chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manga-balloon-name-recognition",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Test names under watch rotations and role changes versus Test names in an actual panel layout; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test names under watch rotations and role changes",
        "outline": [
          "Explain the specific decision: Test names under watch rotations and role changes",
          "Define the applicable contract and limits for Ship crew watch names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test names under watch rotations and role changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test names under watch rotations and role changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:108",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-sibling-rival-ensemble",
      "slug": "sibling-rival-ensemble",
      "name": "Sibling rival ensemble",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/sibling-rival-ensemble/",
        "ja": "/ja/tools/sibling-rival-ensemble/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Coordinate kinship cues and rival identities across scenes",
      "task": "Coordinate kinship cues and rival identities across scenes",
      "searchIntent": {
        "primary": "Complete the task: Coordinate kinship cues and rival identities across scenes",
        "queryHypothesis": "sibling rival ensemble",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate kinship cues and rival identities across scenes?",
        "When should sibling rival ensemble be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate kinship cues and rival identities across scenes",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate kinship cues and rival identities across scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Coordinate kinship cues and rival identities across scenes versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-cue-name-system",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Coordinate kinship cues and rival identities across scenes versus Keep production cues distinct from spoken identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-school-desk-labels",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Coordinate kinship cues and rival identities across scenes versus Coordinate seat maps, names and classroom scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate kinship cues and rival identities across scenes",
        "outline": [
          "Explain the specific decision: Coordinate kinship cues and rival identities across scenes",
          "Define the applicable contract and limits for Sibling rival ensemble",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate kinship cues and rival identities across scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate kinship cues and rival identities across scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:109",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-multi-timeline-cast-names",
      "slug": "multi-timeline-cast-names",
      "name": "Multi timeline cast names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/multi-timeline-cast-names/",
        "ja": "/ja/tools/multi-timeline-cast-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Distinguish contemporaries, ancestors and repeated identities",
      "task": "Distinguish contemporaries, ancestors and repeated identities",
      "searchIntent": {
        "primary": "Complete the task: Distinguish contemporaries, ancestors and repeated identities",
        "queryHypothesis": "multi timeline cast names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish contemporaries, ancestors and repeated identities?",
        "When should multi timeline cast names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish contemporaries, ancestors and repeated identities",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish contemporaries, ancestors and repeated identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-priesthood-succession-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish contemporaries, ancestors and repeated identities versus Track repeated religious names and distinguish holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-multi-calendar-name-timeline",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Distinguish contemporaries, ancestors and repeated identities versus Align explicit naming events across author-defined periodic calendars and audit exact name use against ordered adoptions.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-facing-cast-handout",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Distinguish contemporaries, ancestors and repeated identities versus Export only identities known to the party; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish contemporaries, ancestors and repeated identities",
        "outline": [
          "Explain the specific decision: Distinguish contemporaries, ancestors and repeated identities",
          "Define the applicable contract and limits for Multi timeline cast names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish contemporaries, ancestors and repeated identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish contemporaries, ancestors and repeated identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:110",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-parallel-world-cast-correspondence",
      "slug": "parallel-world-cast-correspondence",
      "name": "Parallel world cast correspondence",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/parallel-world-cast-correspondence/",
        "ja": "/ja/tools/parallel-world-cast-correspondence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Link counterparts while preserving world specific forms",
      "task": "Link counterparts while preserving world specific forms",
      "searchIntent": {
        "primary": "Complete the task: Link counterparts while preserving world specific forms",
        "queryHypothesis": "parallel world cast correspondence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link counterparts while preserving world specific forms?",
        "When should parallel world cast correspondence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link counterparts while preserving world specific forms",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link counterparts while preserving world specific forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-parallel-universe-true-name",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Link counterparts while preserving world specific forms versus Separate corresponding identities and world specific reference rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-doppelganger-cast-labeling",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Link counterparts while preserving world specific forms versus Maintain intended likeness while preserving reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-migration-between-towns",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Link counterparts while preserving world specific forms versus Preserve individual names while updating local forms of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link counterparts while preserving world specific forms",
        "outline": [
          "Explain the specific decision: Link counterparts while preserving world specific forms",
          "Define the applicable contract and limits for Parallel world cast correspondence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link counterparts while preserving world specific forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link counterparts while preserving world specific forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:111",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-reincarnation-cast-mapping",
      "slug": "reincarnation-cast-mapping",
      "name": "Reincarnation cast mapping",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/reincarnation-cast-mapping/",
        "ja": "/ja/tools/reincarnation-cast-mapping/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Track identity continuity without revealing it in public references",
      "task": "Track identity continuity without revealing it in public references",
      "searchIntent": {
        "primary": "Complete the task: Track identity continuity without revealing it in public references",
        "queryHypothesis": "reincarnation cast mapping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track identity continuity without revealing it in public references?",
        "When should reincarnation cast mapping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track identity continuity without revealing it in public references",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track identity continuity without revealing it in public references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-immortal-order-alias-archive",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Track identity continuity without revealing it in public references versus Track dated public names without flattening a long identity history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mystery-reveal-name-recap",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Track identity continuity without revealing it in public references versus Explain the identity solution without contradicting earlier references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track identity continuity without revealing it in public references versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track identity continuity without revealing it in public references",
        "outline": [
          "Explain the specific decision: Track identity continuity without revealing it in public references",
          "Define the applicable contract and limits for Reincarnation cast mapping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track identity continuity without revealing it in public references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track identity continuity without revealing it in public references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:112",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-anthology-recurring-cast-names",
      "slug": "anthology-recurring-cast-names",
      "name": "Anthology recurring cast names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/anthology-recurring-cast-names/",
        "ja": "/ja/tools/anthology-recurring-cast-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Detect accidental reuse across otherwise independent stories",
      "task": "Detect accidental reuse across otherwise independent stories",
      "searchIntent": {
        "primary": "Complete the task: Detect accidental reuse across otherwise independent stories",
        "queryHypothesis": "anthology recurring cast names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect accidental reuse across otherwise independent stories?",
        "When should anthology recurring cast names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect accidental reuse across otherwise independent stories",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect accidental reuse across otherwise independent stories. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-cast-registry",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Detect accidental reuse across otherwise independent stories versus Prevent collisions across sessions and locations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Detect accidental reuse across otherwise independent stories versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-recurring-villain-title-chain",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Detect accidental reuse across otherwise independent stories versus Track changing epithets across encounters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect accidental reuse across otherwise independent stories",
        "outline": [
          "Explain the specific decision: Detect accidental reuse across otherwise independent stories",
          "Define the applicable contract and limits for Anthology recurring cast names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect accidental reuse across otherwise independent stories; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect accidental reuse across otherwise independent stories",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:113",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-series-guest-character-names",
      "slug": "series-guest-character-names",
      "name": "Series guest character names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/series-guest-character-names/",
        "ja": "/ja/tools/series-guest-character-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Prevent conflict with archived recurring characters",
      "task": "Prevent conflict with archived recurring characters",
      "searchIntent": {
        "primary": "Complete the task: Prevent conflict with archived recurring characters",
        "queryHypothesis": "series guest character names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent conflict with archived recurring characters?",
        "When should series guest character names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent conflict with archived recurring characters",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent conflict with archived recurring characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-retired-name-blacklist",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Prevent conflict with archived recurring characters versus Prevent accidental reuse with a reason and permitted exceptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Prevent conflict with archived recurring characters versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-podcast-fiction-guest-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Prevent conflict with archived recurring characters versus Avoid confusion between returning and one episode characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent conflict with archived recurring characters",
        "outline": [
          "Explain the specific decision: Prevent conflict with archived recurring characters",
          "Define the applicable contract and limits for Series guest character names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent conflict with archived recurring characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent conflict with archived recurring characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:114",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-role-label-transition",
      "slug": "cast-role-label-transition",
      "name": "Cast role label transition",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-role-label-transition/",
        "ja": "/ja/tools/cast-role-label-transition/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Replace temporary draft labels without losing scene references",
      "task": "Replace temporary draft labels without losing scene references",
      "searchIntent": {
        "primary": "Complete the task: Replace temporary draft labels without losing scene references",
        "queryHypothesis": "cast role label transition",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to replace temporary draft labels without losing scene references?",
        "When should cast role label transition be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Replace temporary draft labels without losing scene references",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Replace temporary draft labels without losing scene references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-illegitimacy-label-critique",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Replace temporary draft labels without losing scene references versus Audit narrator and character labels without endorsing discriminatory categories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-draft-label-cleanup",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Replace temporary draft labels without losing scene references versus Find temporary labels using a project supplied list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.15833333333333333,
          "sharedProfile": true,
          "difference": "Replace temporary draft labels without losing scene references versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Replace temporary draft labels without losing scene references",
        "outline": [
          "Explain the specific decision: Replace temporary draft labels without losing scene references",
          "Define the applicable contract and limits for Cast role label transition",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Replace temporary draft labels without losing scene references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Replace temporary draft labels without losing scene references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:119",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-anonymous-crowd-reference-plan",
      "slug": "anonymous-crowd-reference-plan",
      "name": "Anonymous crowd reference plan",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/anonymous-crowd-reference-plan/",
        "ja": "/ja/tools/anonymous-crowd-reference-plan/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Decide which background figures need a name at all",
      "task": "Decide which background figures need a name at all",
      "searchIntent": {
        "primary": "Complete the task: Decide which background figures need a name at all",
        "queryHypothesis": "anonymous crowd reference plan",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide which background figures need a name at all?",
        "When should anonymous crowd reference plan be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide which background figures need a name at all",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide which background figures need a name at all. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Decide which background figures need a name at all versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-background-name-density",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide which background figures need a name at all versus Decide which names deserve visible labels in crowd scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Decide which background figures need a name at all versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide which background figures need a name at all",
        "outline": [
          "Explain the specific decision: Decide which background figures need a name at all",
          "Define the applicable contract and limits for Anonymous crowd reference plan",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide which background figures need a name at all; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide which background figures need a name at all",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:120",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-name-relationship-heatmap",
      "slug": "cast-name-relationship-heatmap",
      "name": "Cast name relationship heatmap",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-name-relationship-heatmap/",
        "ja": "/ja/tools/cast-name-relationship-heatmap/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Combine scene proximity with similarity for targeted review",
      "task": "Combine scene proximity with similarity for targeted review",
      "searchIntent": {
        "primary": "Complete the task: Combine scene proximity with similarity for targeted review",
        "queryHypothesis": "cast name relationship heatmap",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to combine scene proximity with similarity for targeted review?",
        "When should cast name relationship heatmap be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Combine scene proximity with similarity for targeted review",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Combine scene proximity with similarity for targeted review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cousin-reunion-cast-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Combine scene proximity with similarity for targeted review versus Avoid collisions during a large family gathering scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-kanji-resemblance",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Combine scene proximity with similarity for targeted review versus Review character shape overlap in a selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-introduction-comprehension",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Combine scene proximity with similarity for targeted review versus Measure who readers think was introduced after a scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Combine scene proximity with similarity for targeted review",
        "outline": [
          "Explain the specific decision: Combine scene proximity with similarity for targeted review",
          "Define the applicable contract and limits for Cast name relationship heatmap",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Combine scene proximity with similarity for targeted review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Combine scene proximity with similarity for targeted review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:121",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-onboarding-reader-test",
      "slug": "cast-onboarding-reader-test",
      "name": "Cast onboarding reader test",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-onboarding-reader-test/",
        "ja": "/ja/tools/cast-onboarding-reader-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Generate recall tasks after staged introductions",
      "task": "Generate recall tasks after staged introductions",
      "searchIntent": {
        "primary": "Complete the task: Generate recall tasks after staged introductions",
        "queryHypothesis": "cast onboarding reader test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate recall tasks after staged introductions?",
        "When should cast onboarding reader test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate recall tasks after staged introductions",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate recall tasks after staged introductions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-delayed-recall-test",
          "score": 0.23484848484848486,
          "sharedProfile": false,
          "difference": "Generate recall tasks after staged introductions versus Test recall after a defined reading passage and delay; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-beta-reader-test",
          "score": 0.1990909090909091,
          "sharedProfile": false,
          "difference": "Generate recall tasks after staged introductions versus Generate blind comparison prompts and record reader confusion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-departure-return-names",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Generate recall tasks after staged introductions versus Reintroduce a returning character after a long narrative absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate recall tasks after staged introductions",
        "outline": [
          "Explain the specific decision: Generate recall tasks after staged introductions",
          "Define the applicable contract and limits for Cast onboarding reader test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate recall tasks after staged introductions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate recall tasks after staged introductions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:122",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-departure-return-names",
      "slug": "cast-departure-return-names",
      "name": "Cast departure return names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-departure-return-names/",
        "ja": "/ja/tools/cast-departure-return-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Reintroduce a returning character after a long narrative absence",
      "task": "Reintroduce a returning character after a long narrative absence",
      "searchIntent": {
        "primary": "Complete the task: Reintroduce a returning character after a long narrative absence",
        "queryHypothesis": "cast departure return names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reintroduce a returning character after a long narrative absence?",
        "When should cast departure return names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reintroduce a returning character after a long narrative absence",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reintroduce a returning character after a long narrative absence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-episodic-name-reintroduction",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reintroduce a returning character after a long narrative absence versus Reintroduce a recurring character after publication gaps; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-introduction-comprehension",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Reintroduce a returning character after a long narrative absence versus Measure who readers think was introduced after a scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-onboarding-reader-test",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Reintroduce a returning character after a long narrative absence versus Generate recall tasks after staged introductions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reintroduce a returning character after a long narrative absence",
        "outline": [
          "Explain the specific decision: Reintroduce a returning character after a long narrative absence",
          "Define the applicable contract and limits for Cast departure return names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reintroduce a returning character after a long narrative absence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reintroduce a returning character after a long narrative absence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:123",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-faction-crossing-character-names",
      "slug": "faction-crossing-character-names",
      "name": "Faction crossing character names",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/faction-crossing-character-names/",
        "ja": "/ja/tools/faction-crossing-character-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Keep allegiance changes from creating duplicate identities",
      "task": "Keep allegiance changes from creating duplicate identities",
      "searchIntent": {
        "primary": "Complete the task: Keep allegiance changes from creating duplicate identities",
        "queryHypothesis": "faction crossing character names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep allegiance changes from creating duplicate identities?",
        "When should faction crossing character names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep allegiance changes from creating duplicate identities",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep allegiance changes from creating duplicate identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-hostile-friendly-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep allegiance changes from creating duplicate identities versus Maintain character continuity through allegiance changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-school-uniform-name-patch",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Keep allegiance changes from creating duplicate identities versus Track prop name changes across character transfers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Keep allegiance changes from creating duplicate identities versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep allegiance changes from creating duplicate identities",
        "outline": [
          "Explain the specific decision: Keep allegiance changes from creating duplicate identities",
          "Define the applicable contract and limits for Faction crossing character names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep allegiance changes from creating duplicate identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep allegiance changes from creating duplicate identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:124",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-dialogue-address-permissions",
      "slug": "cast-dialogue-address-permissions",
      "name": "Cast dialogue address permissions",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-dialogue-address-permissions/",
        "ja": "/ja/tools/cast-dialogue-address-permissions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Map permitted address forms across all speaker pairs",
      "task": "Map permitted address forms across all speaker pairs",
      "searchIntent": {
        "primary": "Complete the task: Map permitted address forms across all speaker pairs",
        "queryHypothesis": "cast dialogue address permissions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map permitted address forms across all speaker pairs?",
        "When should cast dialogue address permissions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map permitted address forms across all speaker pairs",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map permitted address forms across all speaker pairs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-address-relationship-graph",
          "score": 0.275,
          "sharedProfile": false,
          "difference": "Map permitted address forms across all speaker pairs versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-household-servant-address",
          "score": 0.1976190476190476,
          "sharedProfile": false,
          "difference": "Map permitted address forms across all speaker pairs versus Map speaker status and address without making a universal cultural claim; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-border-town-name-register",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Map permitted address forms across all speaker pairs versus Map local and official forms across a fictional frontier; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map permitted address forms across all speaker pairs",
        "outline": [
          "Explain the specific decision: Map permitted address forms across all speaker pairs",
          "Define the applicable contract and limits for Cast dialogue address permissions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map permitted address forms across all speaker pairs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map permitted address forms across all speaker pairs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:125",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-glossary-spoiler-audit",
      "slug": "cast-glossary-spoiler-audit",
      "name": "Cast glossary spoiler audit",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-glossary-spoiler-audit/",
        "ja": "/ja/tools/cast-glossary-spoiler-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Compare reader knowledge by chapter against glossary entries",
      "task": "Compare reader knowledge by chapter against glossary entries",
      "searchIntent": {
        "primary": "Complete the task: Compare reader knowledge by chapter against glossary entries",
        "queryHypothesis": "cast glossary spoiler audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reader knowledge by chapter against glossary entries?",
        "When should cast glossary spoiler audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reader knowledge by chapter against glossary entries",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reader knowledge by chapter against glossary entries. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-chapter-title-name-spoiler",
          "score": 0.22727272727272727,
          "sharedProfile": false,
          "difference": "Compare reader knowledge by chapter against glossary entries versus Evaluate a title against the reader's current identity knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-spoiler-safe-glossary",
          "score": 0.22499999999999998,
          "sharedProfile": false,
          "difference": "Compare reader knowledge by chapter against glossary entries versus Export entries only after the reader reaches the relevant reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-list-spoiler-test",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Compare reader knowledge by chapter against glossary entries versus Compare cast list entries against mystery disclosure timing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reader knowledge by chapter against glossary entries",
        "outline": [
          "Explain the specific decision: Compare reader knowledge by chapter against glossary entries",
          "Define the applicable contract and limits for Cast glossary spoiler audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reader knowledge by chapter against glossary entries; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reader knowledge by chapter against glossary entries",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:126",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-name-budget",
      "slug": "cast-name-budget",
      "name": "Cast name budget",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-name-budget/",
        "ja": "/ja/tools/cast-name-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Allocate memorable naming signals to narratively important roles",
      "task": "Allocate memorable naming signals to narratively important roles",
      "searchIntent": {
        "primary": "Complete the task: Allocate memorable naming signals to narratively important roles",
        "queryHypothesis": "cast name budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to allocate memorable naming signals to narratively important roles?",
        "When should cast name budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Allocate memorable naming signals to narratively important roles",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Allocate memorable naming signals to narratively important roles. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-school-club-cast-names",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Allocate memorable naming signals to narratively important roles versus Separate playful member roles from narrator identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-one-shot-cast-memory-budget",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Allocate memorable naming signals to narratively important roles versus Keep a short session cast distinguishable without a glossary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Allocate memorable naming signals to narratively important roles versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Allocate memorable naming signals to narratively important roles",
        "outline": [
          "Explain the specific decision: Allocate memorable naming signals to narratively important roles",
          "Define the applicable contract and limits for Cast name budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Allocate memorable naming signals to narratively important roles; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Allocate memorable naming signals to narratively important roles",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:127",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-cast-naming-change-impact",
      "slug": "cast-naming-change-impact",
      "name": "Cast naming change impact",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-naming-change-impact/",
        "ja": "/ja/tools/cast-naming-change-impact/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Trace a proposed rename across relationships and scenes",
      "task": "Trace a proposed rename across relationships and scenes",
      "searchIntent": {
        "primary": "Complete the task: Trace a proposed rename across relationships and scenes",
        "queryHypothesis": "cast naming change impact",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace a proposed rename across relationships and scenes?",
        "When should cast naming change impact be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace a proposed rename across relationships and scenes",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace a proposed rename across relationships and scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-rename-impact-map",
          "score": 0.25333333333333335,
          "sharedProfile": false,
          "difference": "Trace a proposed rename across relationships and scenes versus List scenes, props and clues dependent on a proposed rename; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-change-impact",
          "score": 0.22916666666666666,
          "sharedProfile": false,
          "difference": "Trace a proposed rename across relationships and scenes versus Trace edits through dialogue, art props and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rural-urban-name-adaptation",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Trace a proposed rename across relationships and scenes versus Trace specific character choices across a move; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace a proposed rename across relationships and scenes",
        "outline": [
          "Explain the specific decision: Trace a proposed rename across relationships and scenes",
          "Define the applicable contract and limits for Cast naming change impact",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace a proposed rename across relationships and scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace a proposed rename across relationships and scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:128",
      "profileSource": "data/profiles.json#ensemble"
    },
    {
      "id": "nw-true-name-alias-bridge",
      "slug": "true-name-alias-bridge",
      "name": "True name alias bridge",
      "category": "identities",
      "urls": {
        "en": "/en/tools/true-name-alias-bridge/",
        "ja": "/ja/tools/true-name-alias-bridge/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Design linked identities with an explicit clue strength limit",
      "task": "Design linked identities with an explicit clue strength limit",
      "searchIntent": {
        "primary": "Complete the task: Design linked identities with an explicit clue strength limit",
        "queryHypothesis": "true name alias bridge",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design linked identities with an explicit clue strength limit?",
        "When should true name alias bridge be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "trueForm",
          "use": "Anchor a hidden identity without automatically exposing it."
        },
        {
          "key": "coverBrief",
          "use": "Constrain the public persona's invented biography."
        },
        {
          "key": "bridgeRules",
          "use": "Choose authored links such as initials, retained morpheme or no visible overlap."
        },
        {
          "key": "knowledge",
          "use": "Declare observer and chapter knowledge flags."
        }
      ],
      "rules": [
        "Store identities under one stable person ID.",
        "Generate only links explicitly allowed by bridgeRules.",
        "Evaluate clue visibility per observer and scene.",
        "A resemblance is a creative clue, never documentary proof of identity.",
        "No public export includes hidden forms without an explicit knowledge scope.",
        "Resolve true identity only at or after permitted reveal",
        "Evaluate each identity layer against observer state"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Store identities under one stable person ID.",
        "Generate only links explicitly allowed by bridgeRules.",
        "Evaluate clue visibility per observer and scene.",
        "A resemblance is a creative clue, never documentary proof of identity.",
        "No public export includes hidden forms without an explicit knowledge scope.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "true and public form with visibility flags",
        "authored linkage explanation",
        "clue placement timeline",
        "observer knowledge violations",
        "alternative less revealing bridges",
        "Observer-safe display form",
        "Visible layers and withheld count"
      ],
      "capabilities": [
        "View the identity sheet as one character at one chapter.",
        "Adjust link strength while preserving the established cover name component."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The output is a controlled relationship between identity layers and a reveal ledger, rather than one standalone name.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-parallel-universe-true-name",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Design linked identities with an explicit clue strength limit versus Separate corresponding identities and world specific reference rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Design linked identities with an explicit clue strength limit versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-scene-exercise",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Design linked identities with an explicit clue strength limit versus Compare fair clue placement before a controlled reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A fair alias connection controls information rather than guaranteeing a surprise.",
        "outline": [
          "Decide who must be fooled",
          "Build a cover biography before tuning the clue",
          "Compare three bridges with different costs",
          "A borrowed signature at a public auction",
          "Audit earlier scenes after changing the reveal"
        ],
        "story": "Fictional example: an auction restorer signs with the workshop name she inherited. A former apprentice recognizes a private abbreviation, while strangers see an ordinary credit. She later chooses to disclose the personal name behind it.",
        "storyAnalysis": "The clue depends on a taught abbreviation and relationship knowledge. Replacing it with a conspicuous anagram would change who can solve the identity and when.",
        "evidence": "Original observer-state fixtures; Ink state documentation informs implementation, not claims about reader response.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/alias.md",
        "localizedBodies": {
          "en": "content/en/alias.md",
          "ja": "content/ja/alias.md"
        }
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "A chapter-one export omits a true name revealed in chapter six.",
        "Disabling all visible bridges produces no shared-morpheme explanation.",
        "A locked cover surname persists across rerolls.",
        "A clue requiring unknown language knowledge is flagged for review.",
        "Chapter before reveal omits hidden true name",
        "One observer knowing an alias does not grant every observer access"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:131",
      "profileSource": "data/profiles.json#identities",
      "absorbedModules": [
        {
          "sourceId": "nw-alias-reveal-timing",
          "input": "revealChapter",
          "rule": "Resolve true identity only at or after permitted reveal",
          "output": "Observer-safe display form",
          "acceptance": "Chapter before reveal omits hidden true name",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-alias-knowledge-ledger",
          "input": "observerKnowledge",
          "rule": "Evaluate each identity layer against observer state",
          "output": "Visible layers and withheld count",
          "acceptance": "One observer knowing an alias does not grant every observer access",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-character-introduction-naming",
          "input": "referenceForms; referenceEvents; existing observerId, chapter, reveal and knowledge",
          "rule": "Resolve references chronologically per observer. Short forms need a disclosed anchor or authored ambiguity; true-layer forms require reveal and event-time knowledge. Unnamed stays descriptive.",
          "output": "First-use timeline, connection chapter and recap issues in the existing observer-safe identity handoff; concealed displays withheld.",
          "acceptance": "Moving a connection after a short-form use restores a warning; another observer never supplies reader knowledge; a later reveal does not backfill an earlier recap; unnamed does not autofill a hidden name.",
          "evidence": [
            "INTRO-01",
            "INTRO-02",
            "INTRO-03"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-manuscript-nickname-introduction",
          "input": "One confirmed identity, explicit full/short/label forms, chapter and sequence positions, observer-scoped introduce/link/use/unnamed/recap events and authored intentional ambiguity.",
          "rule": "Do not borrow a connection from another observer or infer identities from manuscript strings. An ordered connection must precede use; redacted handoffs respect knowledge at the event time.",
          "output": "First-use connection issues, deliberate ambiguity records and observer-safe handoff. No automatic manuscript scan.",
          "acceptance": "Moving a short-form connection after use adds an issue; another observer connection does not clear it. Hidden recap identity stays withheld. Invalid event positions and anchors fail explicitly.",
          "evidence": [
            "INTRO-01",
            "INTRO-02",
            "INTRO-03",
            "reports/introduction-merge-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-manuscript-name-introduction-audit",
          "input": "One confirmed identity, explicit full/short/label forms, chapter and sequence positions, observer-scoped introduce/link/use/unnamed/recap events and authored intentional ambiguity.",
          "rule": "Do not borrow a connection from another observer or infer identities from manuscript strings. An ordered connection must precede use; redacted handoffs respect knowledge at the event time.",
          "output": "First-use connection issues, deliberate ambiguity records and observer-safe handoff. No automatic manuscript scan.",
          "acceptance": "Moving a short-form connection after use adds an issue; another observer connection does not clear it. Hidden recap identity stays withheld. Invalid event positions and anchors fail explicitly.",
          "evidence": [
            "INTRO-01",
            "INTRO-02",
            "INTRO-03",
            "reports/introduction-merge-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "alias",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/editorial-engines.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/editorial.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "trueName",
          "label": [
            "Author-known true name",
            "作者が把握する本名"
          ],
          "type": "text",
          "default": "Aven Reed",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "lockSurname",
          "label": [
            "Fixed cover surname · optional",
            "別名の姓を固定・任意"
          ],
          "type": "text",
          "default": "Slate",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "bridge",
          "label": [
            "Visible creative link",
            "創作上の関連"
          ],
          "type": "select",
          "default": "none",
          "help": null,
          "options": [
            [
              "none",
              [
                "No required overlap",
                "共通部分を必須にしない"
              ]
            ],
            [
              "initial",
              [
                "Retain initial",
                "頭文字を残す"
              ]
            ],
            [
              "fragment",
              [
                "Retain first two letters",
                "先頭2文字を残す"
              ]
            ]
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Current chapter",
            "現在の章"
          ],
          "type": "number",
          "default": 1,
          "help": null
        },
        {
          "key": "reveal",
          "label": [
            "Earliest reveal chapter",
            "開示できる最初の章"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "knows",
          "label": [
            "This observer knows the identity",
            "この観察者は正体を知っている"
          ],
          "type": "checkbox",
          "default": false,
          "help": null
        },
        {
          "key": "seed",
          "label": [
            "Reproducible seed",
            "再現用シード"
          ],
          "type": "text",
          "default": "woven-01",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "count",
          "label": [
            "Results · 1–30",
            "生成数 · 1〜30"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "exclude",
          "label": [
            "Excluded strings",
            "除外する文字列"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Comma-separated. Matching is case-insensitive.",
            "カンマ区切り。大文字と小文字は区別しません。"
          ]
        },
        {
          "key": "exclusionMode",
          "label": [
            "Exclusion scope",
            "除外の範囲"
          ],
          "type": "select",
          "default": "contains",
          "help": null,
          "options": [
            [
              "contains",
              [
                "Contains string",
                "文字列を含む"
              ]
            ],
            [
              "exact",
              [
                "Exact full name",
                "姓名の完全一致"
              ]
            ]
          ]
        },
        {
          "key": "identityId",
          "label": [
            "Stable character ID",
            "固定の人物ID"
          ],
          "type": "text",
          "default": "person-1",
          "help": null
        },
        {
          "key": "observerId",
          "label": [
            "Observer ID",
            "観察者ID"
          ],
          "type": "text",
          "default": "reader",
          "help": null
        },
        {
          "key": "knowledge",
          "label": [
            "Observer knowledge events",
            "観察者の知識イベント"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "observer ID | true | first chapter known",
            "観察者ID | true | 知る最初の章"
          ]
        },
        {
          "key": "clueTimeline",
          "label": [
            "Disclosed clue timeline",
            "手掛かりの開示予定"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "chapter | clue type | clue text | required knowledge, optional | provided, if established",
            "章 | 種類 | 内容 | 必要な知識・任意 | 設定済みなら provided"
          ]
        },
        {
          "key": "referenceForms",
          "label": [
            "Introduction forms · one identity",
            "初登場時の表記・一人の人物"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "form ID | display | public/true | full/short/label. True-layer forms remain hidden until allowed.",
            "表記ID | 表記 | public/true | full/short/label。trueの表記は許可まで隠します。"
          ]
        },
        {
          "key": "referenceEvents",
          "label": [
            "First-use and connection timeline",
            "最初の使用と対応の提示"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "event ID | chapter | sequence | observer ID | introduce/link/use/unnamed/recap | form ID | anchor form ID | intentional ambiguity reason. unnamed needs only its description in the last field.",
            "イベントID | 章 | 順序 | 観察者ID | introduce/link/use/unnamed/recap | 表記ID | 参照先の表記ID | 意図した曖昧さの理由。unnamedは最後の欄に描写のみ。"
          ]
        }
      ]
    },
    {
      "id": "nw-cover-identity-dossier",
      "slug": "cover-identity-dossier",
      "name": "Cover identity dossier",
      "category": "identities",
      "urls": {
        "en": "/en/tools/cover-identity-dossier/",
        "ja": "/ja/tools/cover-identity-dossier/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Keep an alias consistent with a fictional biography and document set",
      "task": "Keep an alias consistent with a fictional biography and document set",
      "searchIntent": {
        "primary": "Complete the task: Keep an alias consistent with a fictional biography and document set",
        "queryHypothesis": "cover identity dossier",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep an alias consistent with a fictional biography and document set?",
        "When should cover identity dossier be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep an alias consistent with a fictional biography and document set",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep an alias consistent with a fictional biography and document set. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-android-cover-identity",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Keep an alias consistent with a fictional biography and document set versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Keep an alias consistent with a fictional biography and document set versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-time-traveler-cover-names",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Keep an alias consistent with a fictional biography and document set versus Check alias references against story dates and social context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep an alias consistent with a fictional biography and document set",
        "outline": [
          "Explain the specific decision: Keep an alias consistent with a fictional biography and document set",
          "Define the applicable contract and limits for Cover identity dossier",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep an alias consistent with a fictional biography and document set; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep an alias consistent with a fictional biography and document set",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:132",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-disguise-introduction-name",
      "slug": "disguise-introduction-name",
      "name": "Disguise introduction name",
      "category": "identities",
      "urls": {
        "en": "/en/tools/disguise-introduction-name/",
        "ja": "/ja/tools/disguise-introduction-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Choose a name that fits what an observer can plausibly know",
      "task": "Choose a name that fits what an observer can plausibly know",
      "searchIntent": {
        "primary": "Complete the task: Choose a name that fits what an observer can plausibly know",
        "queryHypothesis": "disguise introduction name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to choose a name that fits what an observer can plausibly know?",
        "When should disguise introduction name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Choose a name that fits what an observer can plausibly know",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Choose a name that fits what an observer can plausibly know. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-introduction-rewrite",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Choose a name that fits what an observer can plausibly know versus Revise a supplied introduction to make identity clear sooner; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-gloss-placement",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Choose a name that fits what an observer can plausibly know versus Choose reading notes that preserve panel reading order; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-recognition-trigger",
          "score": 0.1,
          "sharedProfile": true,
          "difference": "Choose a name that fits what an observer can plausibly know versus Test which observer can recognize which form and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Choose a name that fits what an observer can plausibly know",
        "outline": [
          "Explain the specific decision: Choose a name that fits what an observer can plausibly know",
          "Define the applicable contract and limits for Disguise introduction name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Choose a name that fits what an observer can plausibly know; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Choose a name that fits what an observer can plausibly know",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:135",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-impostor-stolen-name",
      "slug": "impostor-stolen-name",
      "name": "Impostor stolen name",
      "category": "identities",
      "urls": {
        "en": "/en/tools/impostor-stolen-name/",
        "ja": "/ja/tools/impostor-stolen-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Separate the impersonator, original holder and audience knowledge",
      "task": "Separate the impersonator, original holder and audience knowledge",
      "searchIntent": {
        "primary": "Complete the task: Separate the impersonator, original holder and audience knowledge",
        "queryHypothesis": "impostor stolen name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate the impersonator, original holder and audience knowledge?",
        "When should impostor stolen name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate the impersonator, original holder and audience knowledge",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate the impersonator, original holder and audience knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-stolen-family-name-motive",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate the impersonator, original holder and audience knowledge versus Connect naming conflict to character stakes rather than a puzzle alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-obsolete-glyph-handling",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate the impersonator, original holder and audience knowledge versus Preserve original and readable fallback separately; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Separate the impersonator, original holder and audience knowledge versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate the impersonator, original holder and audience knowledge",
        "outline": [
          "Explain the specific decision: Separate the impersonator, original holder and audience knowledge",
          "Define the applicable contract and limits for Impostor stolen name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate the impersonator, original holder and audience knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate the impersonator, original holder and audience knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:136",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-amnesiac-placeholder-name",
      "slug": "amnesiac-placeholder-name",
      "name": "Amnesiac placeholder name",
      "category": "identities",
      "urls": {
        "en": "/en/tools/amnesiac-placeholder-name/",
        "ja": "/ja/tools/amnesiac-placeholder-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Transition from assigned label to recovered or chosen identity",
      "task": "Transition from assigned label to recovered or chosen identity",
      "searchIntent": {
        "primary": "Complete the task: Transition from assigned label to recovered or chosen identity",
        "queryHypothesis": "amnesiac placeholder name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transition from assigned label to recovered or chosen identity?",
        "When should amnesiac placeholder name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transition from assigned label to recovered or chosen identity",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transition from assigned label to recovered or chosen identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Transition from assigned label to recovered or chosen identity versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Transition from assigned label to recovered or chosen identity versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-rescue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Transition from assigned label to recovered or chosen identity versus Avoid reducing a rescued character to a rescuer assigned label; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transition from assigned label to recovered or chosen identity",
        "outline": [
          "Explain the specific decision: Transition from assigned label to recovered or chosen identity",
          "Define the applicable contract and limits for Amnesiac placeholder name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transition from assigned label to recovered or chosen identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transition from assigned label to recovered or chosen identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:137",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-witness-protection-fiction-names",
      "slug": "witness-protection-fiction-names",
      "name": "Witness protection fiction names",
      "category": "identities",
      "urls": {
        "en": "/en/tools/witness-protection-fiction-names/",
        "ja": "/ja/tools/witness-protection-fiction-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Design fictional continuity without offering real evasion procedures",
      "task": "Design fictional continuity without offering real evasion procedures",
      "searchIntent": {
        "primary": "Complete the task: Design fictional continuity without offering real evasion procedures",
        "queryHypothesis": "witness protection fiction names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design fictional continuity without offering real evasion procedures?",
        "When should witness protection fiction names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design fictional continuity without offering real evasion procedures",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design fictional continuity without offering real evasion procedures. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-assassin-order-fictional-identities",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Design fictional continuity without offering real evasion procedures versus Focus on narrative continuity and knowledge rather than real evasion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collaborative-fiction-name-proposal",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Design fictional continuity without offering real evasion procedures versus Collect votes and reasons without presenting popularity as quality; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-post-collapse-record-loss",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Design fictional continuity without offering real evasion procedures versus Design personal continuity when documents become unreliable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design fictional continuity without offering real evasion procedures",
        "outline": [
          "Explain the specific decision: Design fictional continuity without offering real evasion procedures",
          "Define the applicable contract and limits for Witness protection fiction names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design fictional continuity without offering real evasion procedures; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design fictional continuity without offering real evasion procedures",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:138",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-undercover-relationship-address",
      "slug": "undercover-relationship-address",
      "name": "Undercover relationship address",
      "category": "identities",
      "urls": {
        "en": "/en/tools/undercover-relationship-address/",
        "ja": "/ja/tools/undercover-relationship-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Keep intimate speech from contradicting a cover identity",
      "task": "Keep intimate speech from contradicting a cover identity",
      "searchIntent": {
        "primary": "Complete the task: Keep intimate speech from contradicting a cover identity",
        "queryHypothesis": "undercover relationship address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep intimate speech from contradicting a cover identity?",
        "When should undercover relationship address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep intimate speech from contradicting a cover identity",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep intimate speech from contradicting a cover identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-address-relationship-graph",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Keep intimate speech from contradicting a cover identity versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-fake-document-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep intimate speech from contradicting a cover identity versus Reconcile a fictional document with cover identity constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Keep intimate speech from contradicting a cover identity versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep intimate speech from contradicting a cover identity",
        "outline": [
          "Explain the specific decision: Keep intimate speech from contradicting a cover identity",
          "Define the applicable contract and limits for Undercover relationship address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep intimate speech from contradicting a cover identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep intimate speech from contradicting a cover identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:139",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-vigilante-civilian-identity",
      "slug": "vigilante-civilian-identity",
      "name": "Vigilante civilian identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/vigilante-civilian-identity/",
        "ja": "/ja/tools/vigilante-civilian-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Separate public moniker, civilian name and witness descriptions",
      "task": "Separate public moniker, civilian name and witness descriptions",
      "searchIntent": {
        "primary": "Complete the task: Separate public moniker, civilian name and witness descriptions",
        "queryHypothesis": "vigilante civilian identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate public moniker, civilian name and witness descriptions?",
        "When should vigilante civilian identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate public moniker, civilian name and witness descriptions",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate public moniker, civilian name and witness descriptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Separate public moniker, civilian name and witness descriptions versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-returning-emigrant-identity",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Separate public moniker, civilian name and witness descriptions versus Reconcile home references with an adopted public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-outgrows-stage-identity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Separate public moniker, civilian name and witness descriptions versus Connect public persona change to career and self understanding; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate public moniker, civilian name and witness descriptions",
        "outline": [
          "Explain the specific decision: Separate public moniker, civilian name and witness descriptions",
          "Define the applicable contract and limits for Vigilante civilian identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate public moniker, civilian name and witness descriptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate public moniker, civilian name and witness descriptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:140",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-masked-antagonist-reference-map",
      "slug": "masked-antagonist-reference-map",
      "name": "Masked antagonist reference map",
      "category": "identities",
      "urls": {
        "en": "/en/tools/masked-antagonist-reference-map/",
        "ja": "/ja/tools/masked-antagonist-reference-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Coordinate clues, epithets and restricted narrator knowledge",
      "task": "Coordinate clues, epithets and restricted narrator knowledge",
      "searchIntent": {
        "primary": "Complete the task: Coordinate clues, epithets and restricted narrator knowledge",
        "queryHypothesis": "masked antagonist reference map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate clues, epithets and restricted narrator knowledge?",
        "When should masked antagonist reference map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate clues, epithets and restricted narrator knowledge",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate clues, epithets and restricted narrator knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-reveal-fairness",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Coordinate clues, epithets and restricted narrator knowledge versus Audit clues that require unsupported cultural knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-split-timeline-identity-map",
          "score": 0.1090909090909091,
          "sharedProfile": true,
          "difference": "Coordinate clues, epithets and restricted narrator knowledge versus Prevent a shared character ID from leaking future knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-rename-impact-map",
          "score": 0.10416666666666666,
          "sharedProfile": false,
          "difference": "Coordinate clues, epithets and restricted narrator knowledge versus List scenes, props and clues dependent on a proposed rename; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate clues, epithets and restricted narrator knowledge",
        "outline": [
          "Explain the specific decision: Coordinate clues, epithets and restricted narrator knowledge",
          "Define the applicable contract and limits for Masked antagonist reference map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate clues, epithets and restricted narrator knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate clues, epithets and restricted narrator knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:141",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-secret-royal-identity",
      "slug": "secret-royal-identity",
      "name": "Secret royal identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/secret-royal-identity/",
        "ja": "/ja/tools/secret-royal-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Manage birth title, assumed name and recognition triggers",
      "task": "Manage birth title, assumed name and recognition triggers",
      "searchIntent": {
        "primary": "Complete the task: Manage birth title, assumed name and recognition triggers",
        "queryHypothesis": "secret royal identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to manage birth title, assumed name and recognition triggers?",
        "When should secret royal identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Manage birth title, assumed name and recognition triggers",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Manage birth title, assumed name and recognition triggers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-gm-secret-identity-sheet",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Manage birth title, assumed name and recognition triggers versus Separate private true names from player facing references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Manage birth title, assumed name and recognition triggers versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-deity-mortal-avatar-identity",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Manage birth title, assumed name and recognition triggers versus Keep an avatar's local name distinct from a divine title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Manage birth title, assumed name and recognition triggers",
        "outline": [
          "Explain the specific decision: Manage birth title, assumed name and recognition triggers",
          "Define the applicable contract and limits for Secret royal identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Manage birth title, assumed name and recognition triggers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Manage birth title, assumed name and recognition triggers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:142",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-exiled-ruler-identity",
      "slug": "exiled-ruler-identity",
      "name": "Exiled ruler identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/exiled-ruler-identity/",
        "ja": "/ja/tools/exiled-ruler-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Track titles claimed, rejected and recognized by different factions",
      "task": "Track titles claimed, rejected and recognized by different factions",
      "searchIntent": {
        "primary": "Complete the task: Track titles claimed, rejected and recognized by different factions",
        "queryHypothesis": "exiled ruler identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track titles claimed, rejected and recognized by different factions?",
        "When should exiled ruler identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track titles claimed, rejected and recognized by different factions",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track titles claimed, rejected and recognized by different factions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Track titles claimed, rejected and recognized by different factions versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-identity-ambiguity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Track titles claimed, rejected and recognized by different factions versus Avoid merging different people solely because names match; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnated-identity-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Track titles claimed, rejected and recognized by different factions versus Link past and present names with controlled narrative evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track titles claimed, rejected and recognized by different factions",
        "outline": [
          "Explain the specific decision: Track titles claimed, rejected and recognized by different factions",
          "Define the applicable contract and limits for Exiled ruler identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track titles claimed, rejected and recognized by different factions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track titles claimed, rejected and recognized by different factions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:143",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-reincarnated-identity-names",
      "slug": "reincarnated-identity-names",
      "name": "Reincarnated identity names",
      "category": "identities",
      "urls": {
        "en": "/en/tools/reincarnated-identity-names/",
        "ja": "/ja/tools/reincarnated-identity-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Link past and present names with controlled narrative evidence",
      "task": "Link past and present names with controlled narrative evidence",
      "searchIntent": {
        "primary": "Complete the task: Link past and present names with controlled narrative evidence",
        "queryHypothesis": "reincarnated identity names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link past and present names with controlled narrative evidence?",
        "When should reincarnated identity names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link past and present names with controlled narrative evidence",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link past and present names with controlled narrative evidence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-confession-identity",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Link past and present names with controlled narrative evidence versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-recognition-clue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Link past and present names with controlled narrative evidence versus Limit a name resemblance to one piece of narrative evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-identity-growth-outline",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Link past and present names with controlled narrative evidence versus Link name choices to concrete decisions over an arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link past and present names with controlled narrative evidence",
        "outline": [
          "Explain the specific decision: Link past and present names with controlled narrative evidence",
          "Define the applicable contract and limits for Reincarnated identity names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link past and present names with controlled narrative evidence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link past and present names with controlled narrative evidence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:144",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-possessed-body-identity",
      "slug": "possessed-body-identity",
      "name": "Possessed body identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/possessed-body-identity/",
        "ja": "/ja/tools/possessed-body-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Distinguish body owner and inhabiting voice in references",
      "task": "Distinguish body owner and inhabiting voice in references",
      "searchIntent": {
        "primary": "Complete the task: Distinguish body owner and inhabiting voice in references",
        "queryHypothesis": "possessed body identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish body owner and inhabiting voice in references?",
        "When should possessed body identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish body owner and inhabiting voice in references",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish body owner and inhabiting voice in references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hive-member-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Distinguish body owner and inhabiting voice in references versus Distinguish collective reference from individual agents; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-returning-emigrant-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Distinguish body owner and inhabiting voice in references versus Reconcile home references with an adopted public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-weapon-personal-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Distinguish body owner and inhabiting voice in references versus Separate artifact model, owner nickname and self name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish body owner and inhabiting voice in references",
        "outline": [
          "Explain the specific decision: Distinguish body owner and inhabiting voice in references",
          "Define the applicable contract and limits for Possessed body identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish body owner and inhabiting voice in references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish body owner and inhabiting voice in references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:145",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-body-swap-name-tracking",
      "slug": "body-swap-name-tracking",
      "name": "Body swap name tracking",
      "category": "identities",
      "urls": {
        "en": "/en/tools/body-swap-name-tracking/",
        "ja": "/ja/tools/body-swap-name-tracking/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Resolve speaker labels against mind and body state",
      "task": "Resolve speaker labels against mind and body state",
      "searchIntent": {
        "primary": "Complete the task: Resolve speaker labels against mind and body state",
        "queryHypothesis": "body swap name tracking",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve speaker labels against mind and body state?",
        "When should body swap name tracking be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve speaker labels against mind and body state",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve speaker labels against mind and body state. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Resolve speaker labels against mind and body state versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Resolve speaker labels against mind and body state versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-subtitle-speaker-name-fit",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Resolve speaker labels against mind and body state versus Test names in speaker labels at supplied subtitle widths; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve speaker labels against mind and body state",
        "outline": [
          "Explain the specific decision: Resolve speaker labels against mind and body state",
          "Define the applicable contract and limits for Body swap name tracking",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve speaker labels against mind and body state; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve speaker labels against mind and body state",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:146",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-clone-identity-differentiation",
      "slug": "clone-identity-differentiation",
      "name": "Clone identity differentiation",
      "category": "identities",
      "urls": {
        "en": "/en/tools/clone-identity-differentiation/",
        "ja": "/ja/tools/clone-identity-differentiation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Assign legal, personal and laboratory identities to cloned characters",
      "task": "Assign legal, personal and laboratory identities to cloned characters",
      "searchIntent": {
        "primary": "Complete the task: Assign legal, personal and laboratory identities to cloned characters",
        "queryHypothesis": "clone identity differentiation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to assign legal, personal and laboratory identities to cloned characters?",
        "When should clone identity differentiation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Assign legal, personal and laboratory identities to cloned characters",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Assign legal, personal and laboratory identities to cloned characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Assign legal, personal and laboratory identities to cloned characters versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Assign legal, personal and laboratory identities to cloned characters versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-telepathic-identity-tokens",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Assign legal, personal and laboratory identities to cloned characters versus Define how shared mental identities appear in prose; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Assign legal, personal and laboratory identities to cloned characters",
        "outline": [
          "Explain the specific decision: Assign legal, personal and laboratory identities to cloned characters",
          "Define the applicable contract and limits for Clone identity differentiation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Assign legal, personal and laboratory identities to cloned characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Assign legal, personal and laboratory identities to cloned characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:147",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-immortal-historical-aliases",
      "slug": "immortal-historical-aliases",
      "name": "Immortal historical aliases",
      "category": "identities",
      "urls": {
        "en": "/en/tools/immortal-historical-aliases/",
        "ja": "/ja/tools/immortal-historical-aliases/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Maintain a dated identity chain without fabricated historical records",
      "task": "Maintain a dated identity chain without fabricated historical records",
      "searchIntent": {
        "primary": "Complete the task: Maintain a dated identity chain without fabricated historical records",
        "queryHypothesis": "immortal historical aliases",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain a dated identity chain without fabricated historical records?",
        "When should immortal historical aliases be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain a dated identity chain without fabricated historical records",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain a dated identity chain without fabricated historical records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-immortal-order-alias-archive",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Maintain a dated identity chain without fabricated historical records versus Track dated public names without flattening a long identity history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Maintain a dated identity chain without fabricated historical records versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-migration-name-records",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Maintain a dated identity chain without fabricated historical records versus Trace documented variants without assuming identity from similarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain a dated identity chain without fabricated historical records",
        "outline": [
          "Explain the specific decision: Maintain a dated identity chain without fabricated historical records",
          "Define the applicable contract and limits for Immortal historical aliases",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain a dated identity chain without fabricated historical records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain a dated identity chain without fabricated historical records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:149",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-time-traveler-cover-names",
      "slug": "time-traveler-cover-names",
      "name": "Time traveler cover names",
      "category": "identities",
      "urls": {
        "en": "/en/tools/time-traveler-cover-names/",
        "ja": "/ja/tools/time-traveler-cover-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Check alias references against story dates and social context",
      "task": "Check alias references against story dates and social context",
      "searchIntent": {
        "primary": "Complete the task: Check alias references against story dates and social context",
        "queryHypothesis": "time traveler cover names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check alias references against story dates and social context?",
        "When should time traveler cover names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check alias references against story dates and social context",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check alias references against story dates and social context. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Check alias references against story dates and social context versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-android-cover-identity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Check alias references against story dates and social context versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cover-identity-dossier",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Check alias references against story dates and social context versus Keep an alias consistent with a fictional biography and document set; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check alias references against story dates and social context",
        "outline": [
          "Explain the specific decision: Check alias references against story dates and social context",
          "Define the applicable contract and limits for Time traveler cover names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check alias references against story dates and social context; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check alias references against story dates and social context",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:150",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-split-timeline-identity-map",
      "slug": "split-timeline-identity-map",
      "name": "Split timeline identity map",
      "category": "identities",
      "urls": {
        "en": "/en/tools/split-timeline-identity-map/",
        "ja": "/ja/tools/split-timeline-identity-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Prevent a shared character ID from leaking future knowledge",
      "task": "Prevent a shared character ID from leaking future knowledge",
      "searchIntent": {
        "primary": "Complete the task: Prevent a shared character ID from leaking future knowledge",
        "queryHypothesis": "split timeline identity map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent a shared character ID from leaking future knowledge?",
        "When should split timeline identity map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent a shared character ID from leaking future knowledge",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent a shared character ID from leaking future knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-collective-identity-names",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Prevent a shared character ID from leaking future knowledge versus Name members whose society treats identity as shared; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-detective-notebook-identity-map",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Prevent a shared character ID from leaking future knowledge versus Separate hypothesis, testimony and corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Prevent a shared character ID from leaking future knowledge versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent a shared character ID from leaking future knowledge",
        "outline": [
          "Explain the specific decision: Prevent a shared character ID from leaking future knowledge",
          "Define the applicable contract and limits for Split timeline identity map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent a shared character ID from leaking future knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent a shared character ID from leaking future knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:151",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-false-confession-identity",
      "slug": "false-confession-identity",
      "name": "False confession identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/false-confession-identity/",
        "ja": "/ja/tools/false-confession-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Keep the confessed name distinct from verified identity evidence",
      "task": "Keep the confessed name distinct from verified identity evidence",
      "searchIntent": {
        "primary": "Complete the task: Keep the confessed name distinct from verified identity evidence",
        "queryHypothesis": "false confession identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep the confessed name distinct from verified identity evidence?",
        "When should false confession identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep the confessed name distinct from verified identity evidence",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep the confessed name distinct from verified identity evidence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-name-confession-audit",
          "score": 0.24,
          "sharedProfile": false,
          "difference": "Keep the confessed name distinct from verified identity evidence versus Compare what is confessed with what the story actually establishes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep the confessed name distinct from verified identity evidence versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep the confessed name distinct from verified identity evidence versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep the confessed name distinct from verified identity evidence",
        "outline": [
          "Explain the specific decision: Keep the confessed name distinct from verified identity evidence",
          "Define the applicable contract and limits for False confession identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep the confessed name distinct from verified identity evidence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep the confessed name distinct from verified identity evidence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:152",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-secret-sibling-alias-clues",
      "slug": "secret-sibling-alias-clues",
      "name": "Secret sibling alias clues",
      "category": "identities",
      "urls": {
        "en": "/en/tools/secret-sibling-alias-clues/",
        "ja": "/ja/tools/secret-sibling-alias-clues/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Limit overlaps that would expose a relationship prematurely",
      "task": "Limit overlaps that would expose a relationship prematurely",
      "searchIntent": {
        "primary": "Complete the task: Limit overlaps that would expose a relationship prematurely",
        "queryHypothesis": "secret sibling alias clues",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to limit overlaps that would expose a relationship prematurely?",
        "When should secret sibling alias clues be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Limit overlaps that would expose a relationship prematurely",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Limit overlaps that would expose a relationship prematurely. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-estranged-sibling-name-clues",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Limit overlaps that would expose a relationship prematurely versus Control how much shared structure reveals relatedness; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-parentage-name-clues",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Limit overlaps that would expose a relationship prematurely versus Place bounded clues without proving lineage through a name alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-shares-secret-name",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Limit overlaps that would expose a relationship prematurely versus Make disclosure a meaningful relationship choice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Limit overlaps that would expose a relationship prematurely",
        "outline": [
          "Explain the specific decision: Limit overlaps that would expose a relationship prematurely",
          "Define the applicable contract and limits for Secret sibling alias clues",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Limit overlaps that would expose a relationship prematurely; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Limit overlaps that would expose a relationship prematurely",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:153",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-hidden-author-identity",
      "slug": "hidden-author-identity",
      "name": "Hidden author identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/hidden-author-identity/",
        "ja": "/ja/tools/hidden-author-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Plan fictional manuscript credit and eventual author disclosure",
      "task": "Plan fictional manuscript credit and eventual author disclosure",
      "searchIntent": {
        "primary": "Complete the task: Plan fictional manuscript credit and eventual author disclosure",
        "queryHypothesis": "hidden author identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to plan fictional manuscript credit and eventual author disclosure?",
        "When should hidden author identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Plan fictional manuscript credit and eventual author disclosure",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Plan fictional manuscript credit and eventual author disclosure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pseudonym-disclosure-statement",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Plan fictional manuscript credit and eventual author disclosure versus Draft accurate disclosure levels selected by the author; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-author-note-signoff",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Plan fictional manuscript credit and eventual author disclosure versus Align informal signoff with the chosen public author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-existing-pen-name-revision",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Plan fictional manuscript credit and eventual author disclosure versus Plan continuity notes and old to new credit mappings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Plan fictional manuscript credit and eventual author disclosure",
        "outline": [
          "Explain the specific decision: Plan fictional manuscript credit and eventual author disclosure",
          "Define the applicable contract and limits for Hidden author identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Plan fictional manuscript credit and eventual author disclosure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Plan fictional manuscript credit and eventual author disclosure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:154",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-anonymous-letter-signatures",
      "slug": "anonymous-letter-signatures",
      "name": "Anonymous letter signatures",
      "category": "identities",
      "urls": {
        "en": "/en/tools/anonymous-letter-signatures/",
        "ja": "/ja/tools/anonymous-letter-signatures/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Map signature forms to sender knowledge and clue fairness",
      "task": "Map signature forms to sender knowledge and clue fairness",
      "searchIntent": {
        "primary": "Complete the task: Map signature forms to sender knowledge and clue fairness",
        "queryHypothesis": "anonymous letter signatures",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map signature forms to sender knowledge and clue fairness?",
        "When should anonymous letter signatures be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map signature forms to sender knowledge and clue fairness",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map signature forms to sender knowledge and clue fairness. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Map signature forms to sender knowledge and clue fairness versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-border-town-name-register",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Map signature forms to sender knowledge and clue fairness versus Map local and official forms across a fictional frontier; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-betrayal",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Map signature forms to sender knowledge and clue fairness versus Map who retains or rejects earlier intimate forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map signature forms to sender knowledge and clue fairness",
        "outline": [
          "Explain the specific decision: Map signature forms to sender knowledge and clue fairness",
          "Define the applicable contract and limits for Anonymous letter signatures",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map signature forms to sender knowledge and clue fairness; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map signature forms to sender knowledge and clue fairness",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:155",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-anonymous-narrator-reveal",
      "slug": "anonymous-narrator-reveal",
      "name": "Anonymous narrator reveal",
      "category": "identities",
      "urls": {
        "en": "/en/tools/anonymous-narrator-reveal/",
        "ja": "/ja/tools/anonymous-narrator-reveal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Test earlier self references against a later identity disclosure",
      "task": "Test earlier self references against a later identity disclosure",
      "searchIntent": {
        "primary": "Complete the task: Test earlier self references against a later identity disclosure",
        "queryHypothesis": "anonymous narrator reveal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test earlier self references against a later identity disclosure?",
        "When should anonymous narrator reveal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test earlier self references against a later identity disclosure",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test earlier self references against a later identity disclosure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Test earlier self references against a later identity disclosure versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mystery-reveal-name-recap",
          "score": 0.23249999999999998,
          "sharedProfile": false,
          "difference": "Test earlier self references against a later identity disclosure versus Explain the identity solution without contradicting earlier references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unreliable-narrator-naming",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Test earlier self references against a later identity disclosure versus Separate self presentation from externally documented identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test earlier self references against a later identity disclosure",
        "outline": [
          "Explain the specific decision: Test earlier self references against a later identity disclosure",
          "Define the applicable contract and limits for Anonymous narrator reveal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test earlier self references against a later identity disclosure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test earlier self references against a later identity disclosure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:156",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-unreliable-name-attribution",
      "slug": "unreliable-name-attribution",
      "name": "Unreliable name attribution",
      "category": "identities",
      "urls": {
        "en": "/en/tools/unreliable-name-attribution/",
        "ja": "/ja/tools/unreliable-name-attribution/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Separate a narrator's claim from corroborated identity",
      "task": "Separate a narrator's claim from corroborated identity",
      "searchIntent": {
        "primary": "Complete the task: Separate a narrator's claim from corroborated identity",
        "queryHypothesis": "unreliable name attribution",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a narrator's claim from corroborated identity?",
        "When should unreliable name attribution be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a narrator's claim from corroborated identity",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a narrator's claim from corroborated identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-unreliable-narrator-naming",
          "score": 0.18888888888888888,
          "sharedProfile": false,
          "difference": "Separate a narrator's claim from corroborated identity versus Separate self presentation from externally documented identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-detective-notebook-identity-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate a narrator's claim from corroborated identity versus Separate hypothesis, testimony and corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hostile-nickname-perspective",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate a narrator's claim from corroborated identity versus Distinguish a character's insult from narrator endorsement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a narrator's claim from corroborated identity",
        "outline": [
          "Explain the specific decision: Separate a narrator's claim from corroborated identity",
          "Define the applicable contract and limits for Unreliable name attribution",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a narrator's claim from corroborated identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a narrator's claim from corroborated identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:157",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-name-theft-magic-contract",
      "slug": "name-theft-magic-contract",
      "name": "Name theft magic contract",
      "category": "identities",
      "urls": {
        "en": "/en/tools/name-theft-magic-contract/",
        "ja": "/ja/tools/name-theft-magic-contract/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Model who loses what when an invented name is stolen",
      "task": "Model who loses what when an invented name is stolen",
      "searchIntent": {
        "primary": "Complete the task: Model who loses what when an invented name is stolen",
        "queryHypothesis": "name theft magic contract",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model who loses what when an invented name is stolen?",
        "When should name theft magic contract be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model who loses what when an invented name is stolen",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model who loses what when an invented name is stolen. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-name-tradeoff-exercise",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model who loses what when an invented name is stolen versus Explain what a localization preserves and loses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-oath-name-contract",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Model who loses what when an invented name is stolen versus Define invented magical name permissions in player readable terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-name-confession-audit",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Model who loses what when an invented name is stolen versus Compare what is confessed with what the story actually establishes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model who loses what when an invented name is stolen",
        "outline": [
          "Explain the specific decision: Model who loses what when an invented name is stolen",
          "Define the applicable contract and limits for Name theft magic contract",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model who loses what when an invented name is stolen; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model who loses what when an invented name is stolen",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:158",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-true-name-magic-access",
      "slug": "true-name-magic-access",
      "name": "True name magic access",
      "category": "identities",
      "urls": {
        "en": "/en/tools/true-name-magic-access/",
        "ja": "/ja/tools/true-name-magic-access/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Set explicit knowledge and permission rules for a magic system",
      "task": "Set explicit knowledge and permission rules for a magic system",
      "searchIntent": {
        "primary": "Complete the task: Set explicit knowledge and permission rules for a magic system",
        "queryHypothesis": "true name magic access",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to set explicit knowledge and permission rules for a magic system?",
        "When should true name magic access be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Set explicit knowledge and permission rules for a magic system",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Set explicit knowledge and permission rules for a magic system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-parallel-universe-true-name",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Set explicit knowledge and permission rules for a magic system versus Separate corresponding identities and world specific reference rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-true-name-decoy",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Set explicit knowledge and permission rules for a magic system versus Make the decoy plausible under an established magic rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Set explicit knowledge and permission rules for a magic system versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Set explicit knowledge and permission rules for a magic system",
        "outline": [
          "Explain the specific decision: Set explicit knowledge and permission rules for a magic system",
          "Define the applicable contract and limits for True name magic access",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Set explicit knowledge and permission rules for a magic system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Set explicit knowledge and permission rules for a magic system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:159",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-name-erasure-story-continuity",
      "slug": "name-erasure-story-continuity",
      "name": "Name erasure story continuity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/name-erasure-story-continuity/",
        "ja": "/ja/tools/name-erasure-story-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Define how records and memories change after erasure",
      "task": "Define how records and memories change after erasure",
      "searchIntent": {
        "primary": "Complete the task: Define how records and memories change after erasure",
        "queryHypothesis": "name erasure story continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define how records and memories change after erasure?",
        "When should name erasure story continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define how records and memories change after erasure",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define how records and memories change after erasure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Define how records and memories change after erasure versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-divorce-name-continuity",
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Define how records and memories change after erasure versus Maintain records and dialogue references before and after separation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-swarm-character-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Define how records and memories change after erasure versus Preserve identity when constituent members change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define how records and memories change after erasure",
        "outline": [
          "Explain the specific decision: Define how records and memories change after erasure",
          "Define the applicable contract and limits for Name erasure story continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define how records and memories change after erasure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define how records and memories change after erasure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:160",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-identity-reset-story-rules",
      "slug": "identity-reset-story-rules",
      "name": "Identity reset story rules",
      "category": "identities",
      "urls": {
        "en": "/en/tools/identity-reset-story-rules/",
        "ja": "/ja/tools/identity-reset-story-rules/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Preserve selected ties when a character renames themselves",
      "task": "Preserve selected ties when a character renames themselves",
      "searchIntent": {
        "primary": "Complete the task: Preserve selected ties when a character renames themselves",
        "queryHypothesis": "identity reset story rules",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve selected ties when a character renames themselves?",
        "When should identity reset story rules be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve selected ties when a character renames themselves",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve selected ties when a character renames themselves. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-katakana-identity-choice",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Preserve selected ties when a character renames themselves versus Explain author selected script effects without claiming universal meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-kanji-resemblance",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve selected ties when a character renames themselves versus Review character shape overlap in a selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-font-coverage-test",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve selected ties when a character renames themselves versus Detect missing glyphs in the actual selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve selected ties when a character renames themselves",
        "outline": [
          "Explain the specific decision: Preserve selected ties when a character renames themselves",
          "Define the applicable contract and limits for Identity reset story rules",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve selected ties when a character renames themselves; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve selected ties when a character renames themselves",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:161",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-secret-title-inheritance",
      "slug": "secret-title-inheritance",
      "name": "Secret title inheritance",
      "category": "identities",
      "urls": {
        "en": "/en/tools/secret-title-inheritance/",
        "ja": "/ja/tools/secret-title-inheritance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Transfer a shared public identity without collapsing individual holders",
      "task": "Transfer a shared public identity without collapsing individual holders",
      "searchIntent": {
        "primary": "Complete the task: Transfer a shared public identity without collapsing individual holders",
        "queryHypothesis": "secret title inheritance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transfer a shared public identity without collapsing individual holders?",
        "When should secret title inheritance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transfer a shared public identity without collapsing individual holders",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transfer a shared public identity without collapsing individual holders. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-collective-name-succession",
          "score": 0.2363636363636364,
          "sharedProfile": false,
          "difference": "Transfer a shared public identity without collapsing individual holders versus Transfer a communal identity without erasing individual histories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-abandons-heroic-title",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Transfer a shared public identity without collapsing individual holders versus Show identity beyond an earned public role; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inherited-questgiver-title",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Transfer a shared public identity without collapsing individual holders versus Transfer office without merging save identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transfer a shared public identity without collapsing individual holders",
        "outline": [
          "Explain the specific decision: Transfer a shared public identity without collapsing individual holders",
          "Define the applicable contract and limits for Secret title inheritance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transfer a shared public identity without collapsing individual holders; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transfer a shared public identity without collapsing individual holders",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:162",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-shared-alias-conspiracy",
      "slug": "shared-alias-conspiracy",
      "name": "Shared alias conspiracy",
      "category": "identities",
      "urls": {
        "en": "/en/tools/shared-alias-conspiracy/",
        "ja": "/ja/tools/shared-alias-conspiracy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Track multiple people using one handle across a timeline",
      "task": "Track multiple people using one handle across a timeline",
      "searchIntent": {
        "primary": "Complete the task: Track multiple people using one handle across a timeline",
        "queryHypothesis": "shared alias conspiracy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track multiple people using one handle across a timeline?",
        "When should shared alias conspiracy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track multiple people using one handle across a timeline",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track multiple people using one handle across a timeline. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Track multiple people using one handle across a timeline versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-alias-reveal-parity",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Track multiple people using one handle across a timeline versus Keep clue timing comparable across language editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-bible",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track multiple people using one handle across a timeline versus Export people, naming rules and exception decisions as one reference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track multiple people using one handle across a timeline",
        "outline": [
          "Explain the specific decision: Track multiple people using one handle across a timeline",
          "Define the applicable contract and limits for Shared alias conspiracy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track multiple people using one handle across a timeline; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track multiple people using one handle across a timeline",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:163",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-dead-character-identity-reuse",
      "slug": "dead-character-identity-reuse",
      "name": "Dead character identity reuse",
      "category": "identities",
      "urls": {
        "en": "/en/tools/dead-character-identity-reuse/",
        "ja": "/ja/tools/dead-character-identity-reuse/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Show who interprets the reused name as survival",
      "task": "Show who interprets the reused name as survival",
      "searchIntent": {
        "primary": "Complete the task: Show who interprets the reused name as survival",
        "queryHypothesis": "dead character identity reuse",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show who interprets the reused name as survival?",
        "When should dead character identity reuse be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show who interprets the reused name as survival",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show who interprets the reused name as survival. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Show who interprets the reused name as survival versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnated-identity-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Show who interprets the reused name as survival versus Link past and present names with controlled narrative evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-villain-public-moniker",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Show who interprets the reused name as survival versus Track who coined the name and who rejects it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show who interprets the reused name as survival",
        "outline": [
          "Explain the specific decision: Show who interprets the reused name as survival",
          "Define the applicable contract and limits for Dead character identity reuse",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show who interprets the reused name as survival; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show who interprets the reused name as survival",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:164",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-false-genealogy-naming",
      "slug": "false-genealogy-naming",
      "name": "False genealogy naming",
      "category": "identities",
      "urls": {
        "en": "/en/tools/false-genealogy-naming/",
        "ja": "/ja/tools/false-genealogy-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Separate forged lineage claims from author known relations",
      "task": "Separate forged lineage claims from author known relations",
      "searchIntent": {
        "primary": "Complete the task: Separate forged lineage claims from author known relations",
        "queryHypothesis": "false genealogy naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate forged lineage claims from author known relations?",
        "When should false genealogy naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate forged lineage claims from author known relations",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate forged lineage claims from author known relations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Separate forged lineage claims from author known relations versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-serial-reader-correction-log",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Separate forged lineage claims from author known relations versus Track reports as claims pending author confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Separate forged lineage claims from author known relations versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate forged lineage claims from author known relations",
        "outline": [
          "Explain the specific decision: Separate forged lineage claims from author known relations",
          "Define the applicable contract and limits for False genealogy naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate forged lineage claims from author known relations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate forged lineage claims from author known relations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:165",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-name-based-reveal-fairness",
      "slug": "name-based-reveal-fairness",
      "name": "Name based reveal fairness",
      "category": "identities",
      "urls": {
        "en": "/en/tools/name-based-reveal-fairness/",
        "ja": "/ja/tools/name-based-reveal-fairness/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Audit clues that require unsupported cultural knowledge",
      "task": "Audit clues that require unsupported cultural knowledge",
      "searchIntent": {
        "primary": "Complete the task: Audit clues that require unsupported cultural knowledge",
        "queryHypothesis": "name based reveal fairness",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to audit clues that require unsupported cultural knowledge?",
        "When should name based reveal fairness be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Audit clues that require unsupported cultural knowledge",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Audit clues that require unsupported cultural knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-reveal-splash",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Audit clues that require unsupported cultural knowledge versus Compare reveal text hierarchy with prior identity clues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Audit clues that require unsupported cultural knowledge versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-masked-antagonist-reference-map",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Audit clues that require unsupported cultural knowledge versus Coordinate clues, epithets and restricted narrator knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Audit clues that require unsupported cultural knowledge",
        "outline": [
          "Explain the specific decision: Audit clues that require unsupported cultural knowledge",
          "Define the applicable contract and limits for Name based reveal fairness",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Audit clues that require unsupported cultural knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Audit clues that require unsupported cultural knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:166",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-identity-reveal-dialogue-revision",
      "slug": "identity-reveal-dialogue-revision",
      "name": "Identity reveal dialogue revision",
      "category": "identities",
      "urls": {
        "en": "/en/tools/identity-reveal-dialogue-revision/",
        "ja": "/ja/tools/identity-reveal-dialogue-revision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Update address forms at a scene boundary without global replacement",
      "task": "Update address forms at a scene boundary without global replacement",
      "searchIntent": {
        "primary": "Complete the task: Update address forms at a scene boundary without global replacement",
        "queryHypothesis": "identity reveal dialogue revision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update address forms at a scene boundary without global replacement?",
        "When should identity reveal dialogue revision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update address forms at a scene boundary without global replacement",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update address forms at a scene boundary without global replacement. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Update address forms at a scene boundary without global replacement versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-team-callsign-dialogue",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Update address forms at a scene boundary without global replacement versus Keep operational and personal address contexts separate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-correction-dialogue",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Update address forms at a scene boundary without global replacement versus Draft corrections that fit the character and scene stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update address forms at a scene boundary without global replacement",
        "outline": [
          "Explain the specific decision: Update address forms at a scene boundary without global replacement",
          "Define the applicable contract and limits for Identity reveal dialogue revision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update address forms at a scene boundary without global replacement; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update address forms at a scene boundary without global replacement",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:167",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-alias-retirement-plan",
      "slug": "alias-retirement-plan",
      "name": "Alias retirement plan",
      "category": "identities",
      "urls": {
        "en": "/en/tools/alias-retirement-plan/",
        "ja": "/ja/tools/alias-retirement-plan/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Decide what records and relationships retain a retired identity",
      "task": "Decide what records and relationships retain a retired identity",
      "searchIntent": {
        "primary": "Complete the task: Decide what records and relationships retain a retired identity",
        "queryHypothesis": "alias retirement plan",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide what records and relationships retain a retired identity?",
        "When should alias retirement plan be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide what records and relationships retain a retired identity",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide what records and relationships retain a retired identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-respawn-identity",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Decide what records and relationships retain a retired identity versus Decide whether respawned units retain or replace identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-obituary-clue",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Decide what records and relationships retain a retired identity versus Reconcile dates, names and witnesses in fictional records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-idol-group-fictional-identities",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Decide what records and relationships retain a retired identity versus Keep stage persona and private identity relationships explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide what records and relationships retain a retired identity",
        "outline": [
          "Explain the specific decision: Decide what records and relationships retain a retired identity",
          "Define the applicable contract and limits for Alias retirement plan",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide what records and relationships retain a retired identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide what records and relationships retain a retired identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:168",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-name-recognition-trigger",
      "slug": "name-recognition-trigger",
      "name": "Name recognition trigger",
      "category": "identities",
      "urls": {
        "en": "/en/tools/name-recognition-trigger/",
        "ja": "/ja/tools/name-recognition-trigger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Test which observer can recognize which form and why",
      "task": "Test which observer can recognize which form and why",
      "searchIntent": {
        "primary": "Complete the task: Test which observer can recognize which form and why",
        "queryHypothesis": "name recognition trigger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test which observer can recognize which form and why?",
        "When should name recognition trigger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test which observer can recognize which form and why",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test which observer can recognize which form and why. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manga-balloon-name-recognition",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Test which observer can recognize which form and why versus Test names in an actual panel layout; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magical-contract-signatory-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test which observer can recognize which form and why versus Define which identity form a fictional contract recognizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-setting-name-rule-exception-map",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test which observer can recognize which form and why versus Identify which characters violate local rules and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test which observer can recognize which form and why",
        "outline": [
          "Explain the specific decision: Test which observer can recognize which form and why",
          "Define the applicable contract and limits for Name recognition trigger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test which observer can recognize which form and why; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test which observer can recognize which form and why",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:169",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-alias-continuity-contradiction-scan",
      "slug": "alias-continuity-contradiction-scan",
      "name": "Alias continuity contradiction scan",
      "category": "identities",
      "urls": {
        "en": "/en/tools/alias-continuity-contradiction-scan/",
        "ja": "/ja/tools/alias-continuity-contradiction-scan/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Find incompatible forms in dated identity appearances",
      "task": "Find incompatible forms in dated identity appearances",
      "searchIntent": {
        "primary": "Complete the task: Find incompatible forms in dated identity appearances",
        "queryHypothesis": "alias continuity contradiction scan",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find incompatible forms in dated identity appearances?",
        "When should alias continuity contradiction scan be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find incompatible forms in dated identity appearances",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find incompatible forms in dated identity appearances. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.24833333333333332,
          "sharedProfile": false,
          "difference": "Find incompatible forms in dated identity appearances versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-immortal-order-alias-archive",
          "score": 0.16818181818181818,
          "sharedProfile": false,
          "difference": "Find incompatible forms in dated identity appearances versus Track dated public names without flattening a long identity history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Find incompatible forms in dated identity appearances versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find incompatible forms in dated identity appearances",
        "outline": [
          "Explain the specific decision: Find incompatible forms in dated identity appearances",
          "Define the applicable contract and limits for Alias continuity contradiction scan",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find incompatible forms in dated identity appearances; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find incompatible forms in dated identity appearances",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:170",
      "profileSource": "data/profiles.json#identities"
    },
    {
      "id": "nw-address-relationship-graph",
      "slug": "address-relationship-graph",
      "name": "Address relationship graph",
      "category": "address",
      "urls": {
        "en": "/en/tools/address-relationship-graph/",
        "ja": "/ja/tools/address-relationship-graph/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Generate permitted address forms for each speaker listener pair",
      "task": "Generate permitted address forms for each speaker listener pair",
      "searchIntent": {
        "primary": "Complete the task: Generate permitted address forms for each speaker listener pair",
        "queryHypothesis": "address relationship graph",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate permitted address forms for each speaker listener pair?",
        "When should address relationship graph be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "people",
          "use": "Assign stable IDs and approved possible address forms."
        },
        {
          "key": "permissions",
          "use": "Map speaker, listener, context and permitted form."
        },
        {
          "key": "events",
          "use": "Make each familiarity change depend on an authored event."
        },
        {
          "key": "scene",
          "use": "Resolve current time, audience and speaker pair."
        }
      ],
      "rules": [
        "Address permissions are directed; A calling B a nickname does not authorize the reverse.",
        "Private forms do not automatically become public.",
        "Resolve the most specific context rule; ambiguous competing rules return a conflict.",
        "Keep a deliberate violation as an attributed action with a review note, not a data correction.",
        "Permit first-name use only after the configured relationship event",
        "Private nickname requires directed context permission",
        "A context-specific full form does not replace ordinary address"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Address permissions are directed; A calling B a nickname does not authorize the reverse.",
        "Private forms do not automatically become public.",
        "Resolve the most specific context rule; ambiguous competing rules return a conflict.",
        "Keep a deliberate violation as an attributed action with a review note, not a data correction.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "resolved forms by speaker pair",
        "event that authorized a transition",
        "private or public boundary",
        "dialogue violation list",
        "Permission transition trace",
        "Speaker-specific resolved address",
        "Contextual address with rule source"
      ],
      "capabilities": [
        "Compare public and private address for the same pair.",
        "Replay a relationship timeline and expose unearned transitions."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "A directed speaker-listener graph and timed permission changes cannot be expressed as a single preferred nickname field.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.275,
          "sharedProfile": false,
          "difference": "Generate permitted address forms for each speaker listener pair versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.23285714285714285,
          "sharedProfile": false,
          "difference": "Generate permitted address forms for each speaker listener pair versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Generate permitted address forms for each speaker listener pair versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Who may say a name can matter more than the name itself.",
        "outline": [
          "Model direction before intimacy",
          "Distinguish a boundary violation from a continuity mistake",
          "One rehearsal room, two audiences",
          "How to earn an address transition",
          "Revise dialogue using the permissions ledger"
        ],
        "story": "Fictional example: a stage manager uses a friend's private nickname during a public rehearsal. The friend asks for the professional surname, then later permits the private form backstage.",
        "storyAnalysis": "The same words have different consequences because the audience changes. A universal nickname field would erase the distinction.",
        "evidence": "Original directed relationship fixtures; language-specific honorific assertions remain subject to sources and native review.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/address.md",
        "localizedBodies": {
          "en": "content/en/address.md",
          "ja": "content/ja/address.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "A permitted private nickname is rejected in a public context unless separately allowed.",
        "Deleting a relationship event invalidates dependent later transitions.",
        "Reversing speaker and listener resolves a different rule where configured.",
        "Conflicting equal-priority rules produce an explanation rather than arbitrary selection.",
        "Earlier scene keeps formal form",
        "Reverse speaker direction does not inherit permission",
        "Normal scene retains usual address"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:173",
      "profileSource": "data/profiles.json#address",
      "absorbedModules": [
        {
          "sourceId": "nw-first-name-transition-scene",
          "input": "addressEvent",
          "rule": "Permit first-name use only after the configured relationship event",
          "output": "Permission transition trace",
          "acceptance": "Earlier scene keeps formal form",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-surname-to-nickname-transition",
          "input": "nicknamePermission",
          "rule": "Private nickname requires directed context permission",
          "output": "Speaker-specific resolved address",
          "acceptance": "Reverse speaker direction does not inherit permission",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-full-name-reprimand",
          "input": "context=reprimand",
          "rule": "A context-specific full form does not replace ordinary address",
          "output": "Contextual address with rule source",
          "acceptance": "Normal scene retains usual address",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "address",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "permissions",
          "label": [
            "Directed address rules",
            "方向のある呼称ルール"
          ],
          "type": "textarea",
          "default": "a | b | public | Morrow | 0 | 99\na | b | private | Sela | 3 | 99\nb | a | * | Reed | 0 | 99",
          "help": [
            "speaker ID | listener ID | context or * | permitted form | from chapter | through chapter. Use * as a wildcard.",
            "話者ID | 相手ID | 場面または * | 許可する呼び名 | 開始章 | 終了章。* は任意の値です。"
          ]
        },
        {
          "key": "speaker",
          "label": [
            "Speaker ID",
            "話者ID"
          ],
          "type": "text",
          "default": "a",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "listener",
          "label": [
            "Listener ID",
            "相手ID"
          ],
          "type": "text",
          "default": "b",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "context",
          "label": [
            "Context",
            "場面"
          ],
          "type": "text",
          "default": "private",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Scene chapter",
            "場面の章"
          ],
          "type": "number",
          "default": 4,
          "help": null
        },
        {
          "key": "relationshipEvents",
          "label": [
            "Relationship milestones",
            "関係の節目"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "event ID | chapter | active/cancelled. A permission may add event ID as column 7.",
            "イベントID | 章 | active/cancelled。呼称ルールの7列目から参照できます。"
          ]
        },
        {
          "key": "dialogue",
          "label": [
            "Dialogue occurrence audit",
            "会話での使用チェック"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "chapter | speaker | listener | context | actual form | intentional violation reason, optional",
            "章 | 話者 | 相手 | 場面 | 実際の呼称 | 意図的な違反の理由・任意"
          ]
        }
      ]
    },
    {
      "id": "nw-intimate-nickname-boundaries",
      "slug": "intimate-nickname-boundaries",
      "name": "Intimate nickname boundaries",
      "category": "address",
      "urls": {
        "en": "/en/tools/intimate-nickname-boundaries/",
        "ja": "/ja/tools/intimate-nickname-boundaries/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Restrict private names to authorized speakers and scenes",
      "task": "Restrict private names to authorized speakers and scenes",
      "searchIntent": {
        "primary": "Complete the task: Restrict private names to authorized speakers and scenes",
        "queryHypothesis": "intimate nickname boundaries",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to restrict private names to authorized speakers and scenes?",
        "When should intimate nickname boundaries be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Restrict private names to authorized speakers and scenes",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Restrict private names to authorized speakers and scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Restrict private names to authorized speakers and scenes versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-reclaims-intimate-name",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Restrict private names to authorized speakers and scenes versus Identify whose use becomes welcome and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Restrict private names to authorized speakers and scenes versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Restrict private names to authorized speakers and scenes",
        "outline": [
          "Explain the specific decision: Restrict private names to authorized speakers and scenes",
          "Define the applicable contract and limits for Intimate nickname boundaries",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Restrict private names to authorized speakers and scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Restrict private names to authorized speakers and scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:176",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-hostile-nickname-perspective",
      "slug": "hostile-nickname-perspective",
      "name": "Hostile nickname perspective",
      "category": "address",
      "urls": {
        "en": "/en/tools/hostile-nickname-perspective/",
        "ja": "/ja/tools/hostile-nickname-perspective/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Distinguish a character's insult from narrator endorsement",
      "task": "Distinguish a character's insult from narrator endorsement",
      "searchIntent": {
        "primary": "Complete the task: Distinguish a character's insult from narrator endorsement",
        "queryHypothesis": "hostile nickname perspective",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish a character's insult from narrator endorsement?",
        "When should hostile nickname perspective be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish a character's insult from narrator endorsement",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish a character's insult from narrator endorsement. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish a character's insult from narrator endorsement versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-servant-master-voice-audit",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Distinguish a character's insult from narrator endorsement versus Distinguish hierarchy conventions from narrator assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unreliable-name-attribution",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish a character's insult from narrator endorsement versus Separate a narrator's claim from corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish a character's insult from narrator endorsement",
        "outline": [
          "Explain the specific decision: Distinguish a character's insult from narrator endorsement",
          "Define the applicable contract and limits for Hostile nickname perspective",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish a character's insult from narrator endorsement; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish a character's insult from narrator endorsement",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:177",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-respectful-address-disagreement",
      "slug": "respectful-address-disagreement",
      "name": "Respectful address disagreement",
      "category": "address",
      "urls": {
        "en": "/en/tools/respectful-address-disagreement/",
        "ja": "/ja/tools/respectful-address-disagreement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Model speakers who differ about a preferred form",
      "task": "Model speakers who differ about a preferred form",
      "searchIntent": {
        "primary": "Complete the task: Model speakers who differ about a preferred form",
        "queryHypothesis": "respectful address disagreement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model speakers who differ about a preferred form?",
        "When should respectful address disagreement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model speakers who differ about a preferred form",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model speakers who differ about a preferred form. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-grandparent-address-network",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Model speakers who differ about a preferred form versus Keep different speakers' kin terms attached to the same person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-secret-address-slip",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Model speakers who differ about a preferred form versus Design a revealing form of address with a scene knowledge ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.10476190476190475,
          "sharedProfile": false,
          "difference": "Model speakers who differ about a preferred form versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model speakers who differ about a preferred form",
        "outline": [
          "Explain the specific decision: Model speakers who differ about a preferred form",
          "Define the applicable contract and limits for Respectful address disagreement",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model speakers who differ about a preferred form; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model speakers who differ about a preferred form",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:178",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-honorific-policy-for-fiction",
      "slug": "honorific-policy-for-fiction",
      "name": "Honorific policy for fiction",
      "category": "address",
      "urls": {
        "en": "/en/tools/honorific-policy-for-fiction/",
        "ja": "/ja/tools/honorific-policy-for-fiction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Define a consistent policy using sourced language guidance",
      "task": "Define a consistent policy using sourced language guidance",
      "searchIntent": {
        "primary": "Complete the task: Define a consistent policy using sourced language guidance",
        "queryHypothesis": "honorific policy for fiction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define a consistent policy using sourced language guidance?",
        "When should honorific policy for fiction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define a consistent policy using sourced language guidance",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define a consistent policy using sourced language guidance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-honorific-policy",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Define a consistent policy using sourced language guidance versus Compare retained, translated and omitted forms with scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-order-policy",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Define a consistent policy using sourced language guidance versus Keep display order consistent across narration and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-streamer-name-visibility",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define a consistent policy using sourced language guidance versus Define a local presentation policy for chosen display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define a consistent policy using sourced language guidance",
        "outline": [
          "Explain the specific decision: Define a consistent policy using sourced language guidance",
          "Define the applicable contract and limits for Honorific policy for fiction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define a consistent policy using sourced language guidance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define a consistent policy using sourced language guidance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:179",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-title-versus-personal-name",
      "slug": "title-versus-personal-name",
      "name": "Title versus personal name",
      "category": "address",
      "urls": {
        "en": "/en/tools/title-versus-personal-name/",
        "ja": "/ja/tools/title-versus-personal-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Choose references when office and individual interests conflict",
      "task": "Choose references when office and individual interests conflict",
      "searchIntent": {
        "primary": "Complete the task: Choose references when office and individual interests conflict",
        "queryHypothesis": "title versus personal name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to choose references when office and individual interests conflict?",
        "When should title versus personal name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Choose references when office and individual interests conflict",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Choose references when office and individual interests conflict. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-title-drift",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Choose references when office and individual interests conflict versus Compare office references against character promotions and succession; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-title-translation-ambiguity",
          "score": 0.1875,
          "sharedProfile": false,
          "difference": "Choose references when office and individual interests conflict versus Preserve office function when a target language term is imperfect; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Choose references when office and individual interests conflict versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Choose references when office and individual interests conflict",
        "outline": [
          "Explain the specific decision: Choose references when office and individual interests conflict",
          "Define the applicable contract and limits for Title versus personal name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Choose references when office and individual interests conflict; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Choose references when office and individual interests conflict",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:180",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-rank-change-address-timeline",
      "slug": "rank-change-address-timeline",
      "name": "Rank change address timeline",
      "category": "address",
      "urls": {
        "en": "/en/tools/rank-change-address-timeline/",
        "ja": "/ja/tools/rank-change-address-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Update dialogue after promotions and demotions",
      "task": "Update dialogue after promotions and demotions",
      "searchIntent": {
        "primary": "Complete the task: Update dialogue after promotions and demotions",
        "queryHypothesis": "rank change address timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update dialogue after promotions and demotions?",
        "When should rank change address timeline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update dialogue after promotions and demotions",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update dialogue after promotions and demotions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Update dialogue after promotions and demotions versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-renounces-title",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Update dialogue after promotions and demotions versus Update address and social reactions after rejection; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shipboard-rank-reference",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Update dialogue after promotions and demotions versus Handle promotions without replacing personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update dialogue after promotions and demotions",
        "outline": [
          "Explain the specific decision: Update dialogue after promotions and demotions",
          "Define the applicable contract and limits for Rank change address timeline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update dialogue after promotions and demotions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update dialogue after promotions and demotions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:181",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-teacher-student-address-map",
      "slug": "teacher-student-address-map",
      "name": "Teacher student address map",
      "category": "address",
      "urls": {
        "en": "/en/tools/teacher-student-address-map/",
        "ja": "/ja/tools/teacher-student-address-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Differentiate institutional and private relationships",
      "task": "Differentiate institutional and private relationships",
      "searchIntent": {
        "primary": "Complete the task: Differentiate institutional and private relationships",
        "queryHypothesis": "teacher student address map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to differentiate institutional and private relationships?",
        "When should teacher student address map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Differentiate institutional and private relationships",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Differentiate institutional and private relationships. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-idol-group-fictional-identities",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Differentiate institutional and private relationships versus Keep stage persona and private identity relationships explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stepfamily-address-map",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Differentiate institutional and private relationships versus Distinguish household membership from inherited naming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-court-ensemble-address-map",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Differentiate institutional and private relationships versus Disambiguate personal names, offices and ranked titles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Differentiate institutional and private relationships",
        "outline": [
          "Explain the specific decision: Differentiate institutional and private relationships",
          "Define the applicable contract and limits for Teacher student address map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Differentiate institutional and private relationships; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Differentiate institutional and private relationships",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:182",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-mentor-public-private-address",
      "slug": "mentor-public-private-address",
      "name": "Mentor public private address",
      "category": "address",
      "urls": {
        "en": "/en/tools/mentor-public-private-address/",
        "ja": "/ja/tools/mentor-public-private-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Contrast training scenes and formal gatherings",
      "task": "Contrast training scenes and formal gatherings",
      "searchIntent": {
        "primary": "Complete the task: Contrast training scenes and formal gatherings",
        "queryHypothesis": "mentor public private address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast training scenes and formal gatherings?",
        "When should mentor public private address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast training scenes and formal gatherings",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast training scenes and formal gatherings. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-investigator-public-reputation",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Contrast training scenes and formal gatherings versus Contrast newspaper label, professional title and self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Contrast training scenes and formal gatherings versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-revision-history",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Contrast training scenes and formal gatherings versus Track why a name changed and dependent scenes to revisit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast training scenes and formal gatherings",
        "outline": [
          "Explain the specific decision: Contrast training scenes and formal gatherings",
          "Define the applicable contract and limits for Mentor public private address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast training scenes and formal gatherings; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast training scenes and formal gatherings",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:183",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-rival-respect-address-arc",
      "slug": "rival-respect-address-arc",
      "name": "Rival respect address arc",
      "category": "address",
      "urls": {
        "en": "/en/tools/rival-respect-address-arc/",
        "ja": "/ja/tools/rival-respect-address-arc/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Encode changes in mutual regard without changing legal names",
      "task": "Encode changes in mutual regard without changing legal names",
      "searchIntent": {
        "primary": "Complete the task: Encode changes in mutual regard without changing legal names",
        "queryHypothesis": "rival respect address arc",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to encode changes in mutual regard without changing legal names?",
        "When should rival respect address arc be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Encode changes in mutual regard without changing legal names",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Encode changes in mutual regard without changing legal names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rival-character-name-pairing",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Encode changes in mutual regard without changing legal names versus Express opposition without making names indistinguishable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estrangement-address-reversal",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Encode changes in mutual regard without changing legal names versus Restore distance through deliberate naming changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-emotional-continuity",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Encode changes in mutual regard without changing legal names versus Test whether naming changes match the surrounding character behavior; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Encode changes in mutual regard without changing legal names",
        "outline": [
          "Explain the specific decision: Encode changes in mutual regard without changing legal names",
          "Define the applicable contract and limits for Rival respect address arc",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Encode changes in mutual regard without changing legal names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Encode changes in mutual regard without changing legal names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:184",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-romantic-address-progression",
      "slug": "romantic-address-progression",
      "name": "Romantic address progression",
      "category": "address",
      "urls": {
        "en": "/en/tools/romantic-address-progression/",
        "ja": "/ja/tools/romantic-address-progression/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Tie endearments to story milestones and consent",
      "task": "Tie endearments to story milestones and consent",
      "searchIntent": {
        "primary": "Complete the task: Tie endearments to story milestones and consent",
        "queryHypothesis": "romantic address progression",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie endearments to story milestones and consent?",
        "When should romantic address progression be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie endearments to story milestones and consent",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie endearments to story milestones and consent. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-gives-another-a-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Tie endearments to story milestones and consent versus Make consent, power and relationship explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Tie endearments to story milestones and consent versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-corrects-public-record",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Tie endearments to story milestones and consent versus Trace the cost and story consequences of correction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie endearments to story milestones and consent",
        "outline": [
          "Explain the specific decision: Tie endearments to story milestones and consent",
          "Define the applicable contract and limits for Romantic address progression",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie endearments to story milestones and consent; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie endearments to story milestones and consent",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:185",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-estrangement-address-reversal",
      "slug": "estrangement-address-reversal",
      "name": "Estrangement address reversal",
      "category": "address",
      "urls": {
        "en": "/en/tools/estrangement-address-reversal/",
        "ja": "/ja/tools/estrangement-address-reversal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Restore distance through deliberate naming changes",
      "task": "Restore distance through deliberate naming changes",
      "searchIntent": {
        "primary": "Complete the task: Restore distance through deliberate naming changes",
        "queryHypothesis": "estrangement address reversal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to restore distance through deliberate naming changes?",
        "When should estrangement address reversal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Restore distance through deliberate naming changes",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Restore distance through deliberate naming changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-hostile-friendly-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Restore distance through deliberate naming changes versus Maintain character continuity through allegiance changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-formal-informal-contrast",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Restore distance through deliberate naming changes versus Rebuild relationship distance through approved language choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-seasonal-population-naming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Restore distance through deliberate naming changes versus Maintain continuity through time based population changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Restore distance through deliberate naming changes",
        "outline": [
          "Explain the specific decision: Restore distance through deliberate naming changes",
          "Define the applicable contract and limits for Estrangement address reversal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Restore distance through deliberate naming changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Restore distance through deliberate naming changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:186",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-reconciliation-name-return",
      "slug": "reconciliation-name-return",
      "name": "Reconciliation name return",
      "category": "address",
      "urls": {
        "en": "/en/tools/reconciliation-name-return/",
        "ja": "/ja/tools/reconciliation-name-return/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Make the return of a form of address legible",
      "task": "Make the return of a form of address legible",
      "searchIntent": {
        "primary": "Complete the task: Make the return of a form of address legible",
        "queryHypothesis": "reconciliation name return",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make the return of a form of address legible?",
        "When should reconciliation name return be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make the return of a form of address legible",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make the return of a form of address legible. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-letter-salutation-clue",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Make the return of a form of address legible versus Make an address form reveal a specific relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Make the return of a form of address legible versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-secret-address-slip",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Make the return of a form of address legible versus Design a revealing form of address with a scene knowledge ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make the return of a form of address legible",
        "outline": [
          "Explain the specific decision: Make the return of a form of address legible",
          "Define the applicable contract and limits for Reconciliation name return",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make the return of a form of address legible; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make the return of a form of address legible",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:187",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-child-adult-address-shift",
      "slug": "child-adult-address-shift",
      "name": "Child adult address shift",
      "category": "address",
      "urls": {
        "en": "/en/tools/child-adult-address-shift/",
        "ja": "/ja/tools/child-adult-address-shift/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Update a fictional relationship across a time skip",
      "task": "Update a fictional relationship across a time skip",
      "searchIntent": {
        "primary": "Complete the task: Update a fictional relationship across a time skip",
        "queryHypothesis": "child adult address shift",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update a fictional relationship across a time skip?",
        "When should child adult address shift be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update a fictional relationship across a time skip",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update a fictional relationship across a time skip. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-name-planner",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Update a fictional relationship across a time skip versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-multilingual-address-switching",
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Update a fictional relationship across a time skip versus Track language and relationship triggers independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Update a fictional relationship across a time skip versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update a fictional relationship across a time skip",
        "outline": [
          "Explain the specific decision: Update a fictional relationship across a time skip",
          "Define the applicable contract and limits for Child adult address shift",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update a fictional relationship across a time skip; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update a fictional relationship across a time skip",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:188",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-servant-master-voice-audit",
      "slug": "servant-master-voice-audit",
      "name": "Servant master voice audit",
      "category": "address",
      "urls": {
        "en": "/en/tools/servant-master-voice-audit/",
        "ja": "/ja/tools/servant-master-voice-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Distinguish hierarchy conventions from narrator assumptions",
      "task": "Distinguish hierarchy conventions from narrator assumptions",
      "searchIntent": {
        "primary": "Complete the task: Distinguish hierarchy conventions from narrator assumptions",
        "queryHypothesis": "servant master voice audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish hierarchy conventions from narrator assumptions?",
        "When should servant master voice audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish hierarchy conventions from narrator assumptions",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish hierarchy conventions from narrator assumptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hostile-nickname-perspective",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Distinguish hierarchy conventions from narrator assumptions versus Distinguish a character's insult from narrator endorsement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-syllable-misconception-audit",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Distinguish hierarchy conventions from narrator assumptions versus Distinguish mora based analysis from English syllable estimates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-lore-naming-conflict",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish hierarchy conventions from narrator assumptions versus Reconcile two contributor supplied naming conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish hierarchy conventions from narrator assumptions",
        "outline": [
          "Explain the specific decision: Distinguish hierarchy conventions from narrator assumptions",
          "Define the applicable contract and limits for Servant master voice audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish hierarchy conventions from narrator assumptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish hierarchy conventions from narrator assumptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:189",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-team-callsign-dialogue",
      "slug": "team-callsign-dialogue",
      "name": "Team callsign dialogue",
      "category": "address",
      "urls": {
        "en": "/en/tools/team-callsign-dialogue/",
        "ja": "/ja/tools/team-callsign-dialogue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Keep operational and personal address contexts separate",
      "task": "Keep operational and personal address contexts separate",
      "searchIntent": {
        "primary": "Complete the task: Keep operational and personal address contexts separate",
        "queryHypothesis": "team callsign dialogue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep operational and personal address contexts separate?",
        "When should team callsign dialogue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep operational and personal address contexts separate",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep operational and personal address contexts separate. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-in-farewell-dialogue",
          "score": 0.16875,
          "sharedProfile": true,
          "difference": "Keep operational and personal address contexts separate versus Compare last address choices against the relationship arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Keep operational and personal address contexts separate versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identity-reveal-dialogue-revision",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Keep operational and personal address contexts separate versus Update address forms at a scene boundary without global replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep operational and personal address contexts separate",
        "outline": [
          "Explain the specific decision: Keep operational and personal address contexts separate",
          "Define the applicable contract and limits for Team callsign dialogue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep operational and personal address contexts separate; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep operational and personal address contexts separate",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:190",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-sibling-birth-order-address",
      "slug": "sibling-birth-order-address",
      "name": "Sibling birth order address",
      "category": "address",
      "urls": {
        "en": "/en/tools/sibling-birth-order-address/",
        "ja": "/ja/tools/sibling-birth-order-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Use a supplied cultural policy rather than infer kin terms",
      "task": "Use a supplied cultural policy rather than infer kin terms",
      "searchIntent": {
        "primary": "Complete the task: Use a supplied cultural policy rather than infer kin terms",
        "queryHypothesis": "sibling birth order address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to use a supplied cultural policy rather than infer kin terms?",
        "When should sibling birth order address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Use a supplied cultural policy rather than infer kin terms",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Use a supplied cultural policy rather than infer kin terms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-grandparent-address-network",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Use a supplied cultural policy rather than infer kin terms versus Keep different speakers' kin terms attached to the same person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-assassin-order-fictional-identities",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Use a supplied cultural policy rather than infer kin terms versus Focus on narrative continuity and knowledge rather than real evasion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Use a supplied cultural policy rather than infer kin terms versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Use a supplied cultural policy rather than infer kin terms",
        "outline": [
          "Explain the specific decision: Use a supplied cultural policy rather than infer kin terms",
          "Define the applicable contract and limits for Sibling birth order address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Use a supplied cultural policy rather than infer kin terms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Use a supplied cultural policy rather than infer kin terms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:191",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-grandparent-nickname-dialogue",
      "slug": "grandparent-nickname-dialogue",
      "name": "Grandparent nickname dialogue",
      "category": "address",
      "urls": {
        "en": "/en/tools/grandparent-nickname-dialogue/",
        "ja": "/ja/tools/grandparent-nickname-dialogue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Map each child's term to a stable character identity",
      "task": "Map each child's term to a stable character identity",
      "searchIntent": {
        "primary": "Complete the task: Map each child's term to a stable character identity",
        "queryHypothesis": "grandparent nickname dialogue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map each child's term to a stable character identity?",
        "When should grandparent nickname dialogue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map each child's term to a stable character identity",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map each child's term to a stable character identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Map each child's term to a stable character identity versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Map each child's term to a stable character identity versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Map each child's term to a stable character identity versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map each child's term to a stable character identity",
        "outline": [
          "Explain the specific decision: Map each child's term to a stable character identity",
          "Define the applicable contract and limits for Grandparent nickname dialogue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map each child's term to a stable character identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map each child's term to a stable character identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:192",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-former-name-reference-policy",
      "slug": "former-name-reference-policy",
      "name": "Former name reference policy",
      "category": "address",
      "urls": {
        "en": "/en/tools/former-name-reference-policy/",
        "ja": "/ja/tools/former-name-reference-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Mark necessary historical references and avoid accidental exposure",
      "task": "Mark necessary historical references and avoid accidental exposure",
      "searchIntent": {
        "primary": "Complete the task: Mark necessary historical references and avoid accidental exposure",
        "queryHypothesis": "former name reference policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to mark necessary historical references and avoid accidental exposure?",
        "When should former name reference policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Mark necessary historical references and avoid accidental exposure",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Mark necessary historical references and avoid accidental exposure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-noble-house-personal-reference",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Mark necessary historical references and avoid accidental exposure versus Avoid confusing a house, estate and individual holder; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-romantic-lead-name-pairing",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Mark necessary historical references and avoid accidental exposure versus Test paired references, initials and accidental rhyme; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rebel-cell-identity-separation",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Mark necessary historical references and avoid accidental exposure versus Avoid accidental leakage between cells in story dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Mark necessary historical references and avoid accidental exposure",
        "outline": [
          "Explain the specific decision: Mark necessary historical references and avoid accidental exposure",
          "Define the applicable contract and limits for Former name reference policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Mark necessary historical references and avoid accidental exposure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Mark necessary historical references and avoid accidental exposure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:193",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-deliberate-misnaming-scene",
      "slug": "deliberate-misnaming-scene",
      "name": "Deliberate misnaming scene",
      "category": "address",
      "urls": {
        "en": "/en/tools/deliberate-misnaming-scene/",
        "ja": "/ja/tools/deliberate-misnaming-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Track intent, harm and response without normalizing the act",
      "task": "Track intent, harm and response without normalizing the act",
      "searchIntent": {
        "primary": "Complete the task: Track intent, harm and response without normalizing the act",
        "queryHypothesis": "deliberate misnaming scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track intent, harm and response without normalizing the act?",
        "When should deliberate misnaming scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track intent, harm and response without normalizing the act",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track intent, harm and response without normalizing the act. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-forgives-misnaming",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Track intent, harm and response without normalizing the act versus Show response and boundaries without treating forgiveness as required; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Track intent, harm and response without normalizing the act versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-anonymous-service-arc",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track intent, harm and response without normalizing the act versus Show the choice to act without seeking a named reputation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track intent, harm and response without normalizing the act",
        "outline": [
          "Explain the specific decision: Track intent, harm and response without normalizing the act",
          "Define the applicable contract and limits for Deliberate misnaming scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track intent, harm and response without normalizing the act; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track intent, harm and response without normalizing the act",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:194",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-mispronunciation-character-arc",
      "slug": "mispronunciation-character-arc",
      "name": "Mispronunciation character arc",
      "category": "address",
      "urls": {
        "en": "/en/tools/mispronunciation-character-arc/",
        "ja": "/ja/tools/mispronunciation-character-arc/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Record author verified pronunciation and speaker learning",
      "task": "Record author verified pronunciation and speaker learning",
      "searchIntent": {
        "primary": "Complete the task: Record author verified pronunciation and speaker learning",
        "queryHypothesis": "mispronunciation character arc",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record author verified pronunciation and speaker learning?",
        "When should mispronunciation character arc be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record author verified pronunciation and speaker learning",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record author verified pronunciation and speaker learning. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Record author verified pronunciation and speaker learning versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-anonymous-service-arc",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Record author verified pronunciation and speaker learning versus Show the choice to act without seeking a named reputation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-alternative-ending",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Record author verified pronunciation and speaker learning versus Compare how a final naming choice changes the story's implied resolution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record author verified pronunciation and speaker learning",
        "outline": [
          "Explain the specific decision: Record author verified pronunciation and speaker learning",
          "Define the applicable contract and limits for Mispronunciation character arc",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record author verified pronunciation and speaker learning; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record author verified pronunciation and speaker learning",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:195",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-name-correction-dialogue",
      "slug": "name-correction-dialogue",
      "name": "Name correction dialogue",
      "category": "address",
      "urls": {
        "en": "/en/tools/name-correction-dialogue/",
        "ja": "/ja/tools/name-correction-dialogue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Draft corrections that fit the character and scene stakes",
      "task": "Draft corrections that fit the character and scene stakes",
      "searchIntent": {
        "primary": "Complete the task: Draft corrections that fit the character and scene stakes",
        "queryHypothesis": "name correction dialogue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to draft corrections that fit the character and scene stakes?",
        "When should name correction dialogue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Draft corrections that fit the character and scene stakes",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Draft corrections that fit the character and scene stakes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-editor-name-correction-sheet",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Draft corrections that fit the character and scene stakes versus Track corrections with page and panel references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-vocative-pacing",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Draft corrections that fit the character and scene stakes versus Measure recorded name duration against a scene timing budget; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-name-dialogue-grammar",
          "score": 0.128125,
          "sharedProfile": false,
          "difference": "Draft corrections that fit the character and scene stakes versus Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Draft corrections that fit the character and scene stakes",
        "outline": [
          "Explain the specific decision: Draft corrections that fit the character and scene stakes",
          "Define the applicable contract and limits for Name correction dialogue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Draft corrections that fit the character and scene stakes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Draft corrections that fit the character and scene stakes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:196",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-name-avoidance-subtext",
      "slug": "name-avoidance-subtext",
      "name": "Name avoidance subtext",
      "category": "address",
      "urls": {
        "en": "/en/tools/name-avoidance-subtext/",
        "ja": "/ja/tools/name-avoidance-subtext/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Show relationship tension through circumlocution",
      "task": "Show relationship tension through circumlocution",
      "searchIntent": {
        "primary": "Complete the task: Show relationship tension through circumlocution",
        "queryHypothesis": "name avoidance subtext",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show relationship tension through circumlocution?",
        "When should name avoidance subtext be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show relationship tension through circumlocution",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show relationship tension through circumlocution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Show relationship tension through circumlocution versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-formal-informal-contrast",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Show relationship tension through circumlocution versus Rebuild relationship distance through approved language choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nickname-consent-scene-exercise",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Show relationship tension through circumlocution versus Show acceptance and refusal through dialogue consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show relationship tension through circumlocution",
        "outline": [
          "Explain the specific decision: Show relationship tension through circumlocution",
          "Define the applicable contract and limits for Name avoidance subtext",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show relationship tension through circumlocution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show relationship tension through circumlocution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:197",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-name-repetition-in-arguments",
      "slug": "name-repetition-in-arguments",
      "name": "Name repetition in arguments",
      "category": "address",
      "urls": {
        "en": "/en/tools/name-repetition-in-arguments/",
        "ja": "/ja/tools/name-repetition-in-arguments/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Test whether repeated vocatives alter scene intensity",
      "task": "Test whether repeated vocatives alter scene intensity",
      "searchIntent": {
        "primary": "Complete the task: Test whether repeated vocatives alter scene intensity",
        "queryHypothesis": "name repetition in arguments",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test whether repeated vocatives alter scene intensity?",
        "When should name repetition in arguments be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test whether repeated vocatives alter scene intensity",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test whether repeated vocatives alter scene intensity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Test whether repeated vocatives alter scene intensity versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-emotional-continuity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test whether repeated vocatives alter scene intensity versus Test whether naming changes match the surrounding character behavior; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-rename-counterfactual",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Test whether repeated vocatives alter scene intensity versus Test whether a mystery remains fair after a naming change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test whether repeated vocatives alter scene intensity",
        "outline": [
          "Explain the specific decision: Test whether repeated vocatives alter scene intensity",
          "Define the applicable contract and limits for Name repetition in arguments",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test whether repeated vocatives alter scene intensity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test whether repeated vocatives alter scene intensity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:199",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-unspoken-name-scene",
      "slug": "unspoken-name-scene",
      "name": "Unspoken name scene",
      "category": "address",
      "urls": {
        "en": "/en/tools/unspoken-name-scene/",
        "ja": "/ja/tools/unspoken-name-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Keep a name off the page while preserving referential clarity",
      "task": "Keep a name off the page while preserving referential clarity",
      "searchIntent": {
        "primary": "Complete the task: Keep a name off the page while preserving referential clarity",
        "queryHypothesis": "unspoken name scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep a name off the page while preserving referential clarity?",
        "When should unspoken name scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep a name off the page while preserving referential clarity",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep a name off the page while preserving referential clarity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Keep a name off the page while preserving referential clarity versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mononym-character-design",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep a name off the page while preserving referential clarity versus Maintain referential clarity for a character with one public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-replacement",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Keep a name off the page while preserving referential clarity versus Replace one established name while preserving story dependencies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep a name off the page while preserving referential clarity",
        "outline": [
          "Explain the specific decision: Keep a name off the page while preserving referential clarity",
          "Define the applicable contract and limits for Unspoken name scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep a name off the page while preserving referential clarity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep a name off the page while preserving referential clarity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:200",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-name-in-farewell-dialogue",
      "slug": "name-in-farewell-dialogue",
      "name": "Name in farewell dialogue",
      "category": "address",
      "urls": {
        "en": "/en/tools/name-in-farewell-dialogue/",
        "ja": "/ja/tools/name-in-farewell-dialogue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Compare last address choices against the relationship arc",
      "task": "Compare last address choices against the relationship arc",
      "searchIntent": {
        "primary": "Complete the task: Compare last address choices against the relationship arc",
        "queryHypothesis": "name in farewell dialogue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare last address choices against the relationship arc?",
        "When should name in farewell dialogue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare last address choices against the relationship arc",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare last address choices against the relationship arc. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-team-callsign-dialogue",
          "score": 0.16875,
          "sharedProfile": true,
          "difference": "Compare last address choices against the relationship arc versus Keep operational and personal address contexts separate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-vocative-pacing",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Compare last address choices against the relationship arc versus Measure recorded name duration against a scene timing budget; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare last address choices against the relationship arc versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare last address choices against the relationship arc",
        "outline": [
          "Explain the specific decision: Compare last address choices against the relationship arc",
          "Define the applicable contract and limits for Name in farewell dialogue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare last address choices against the relationship arc; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare last address choices against the relationship arc",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:201",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-name-in-confession-scene",
      "slug": "name-in-confession-scene",
      "name": "Name in confession scene",
      "category": "address",
      "urls": {
        "en": "/en/tools/name-in-confession-scene/",
        "ja": "/ja/tools/name-in-confession-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Control who is identified by an emotionally loaded address",
      "task": "Control who is identified by an emotionally loaded address",
      "searchIntent": {
        "primary": "Complete the task: Control who is identified by an emotionally loaded address",
        "queryHypothesis": "name in confession scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to control who is identified by an emotionally loaded address?",
        "When should name in confession scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Control who is identified by an emotionally loaded address",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Control who is identified by an emotionally loaded address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-name-confession-audit",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Control who is identified by an emotionally loaded address versus Compare what is confessed with what the story actually establishes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-scene-cooccurrence-name-audit",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Control who is identified by an emotionally loaded address versus Prioritize collisions between characters who share scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-scene-checklist",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Control who is identified by an emotionally loaded address versus Link every address change to an earned story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Control who is identified by an emotionally loaded address",
        "outline": [
          "Explain the specific decision: Control who is identified by an emotionally loaded address",
          "Define the applicable contract and limits for Name in confession scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Control who is identified by an emotionally loaded address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Control who is identified by an emotionally loaded address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:202",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-crowd-shouted-name-clarity",
      "slug": "crowd-shouted-name-clarity",
      "name": "Crowd shouted name clarity",
      "category": "address",
      "urls": {
        "en": "/en/tools/crowd-shouted-name-clarity/",
        "ja": "/ja/tools/crowd-shouted-name-clarity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Test distinguishability against other names in the scene",
      "task": "Test distinguishability against other names in the scene",
      "searchIntent": {
        "primary": "Complete the task: Test distinguishability against other names in the scene",
        "queryHypothesis": "crowd shouted name clarity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test distinguishability against other names in the scene?",
        "When should crowd shouted name clarity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test distinguishability against other names in the scene",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test distinguishability against other names in the scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-chapter-heading",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test distinguishability against other names in the scene versus Test headings against viewpoint identity and spoiler exposure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-vocative-pacing",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test distinguishability against other names in the scene versus Measure recorded name duration against a scene timing budget; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-system-reader-load",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test distinguishability against other names in the scene versus Test grammar complexity against reader recall exercises; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test distinguishability against other names in the scene",
        "outline": [
          "Explain the specific decision: Test distinguishability against other names in the scene",
          "Define the applicable contract and limits for Crowd shouted name clarity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test distinguishability against other names in the scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test distinguishability against other names in the scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:203",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-letters-versus-speech-address",
      "slug": "letters-versus-speech-address",
      "name": "Letters versus speech address",
      "category": "address",
      "urls": {
        "en": "/en/tools/letters-versus-speech-address/",
        "ja": "/ja/tools/letters-versus-speech-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Compare written and spoken relationship registers",
      "task": "Compare written and spoken relationship registers",
      "searchIntent": {
        "primary": "Complete the task: Compare written and spoken relationship registers",
        "queryHypothesis": "letters versus speech address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare written and spoken relationship registers?",
        "When should letters versus speech address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare written and spoken relationship registers",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare written and spoken relationship registers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare written and spoken relationship registers versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-in-letters",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Compare written and spoken relationship registers versus Create signoffs and salutations tied to relationship distance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-multilingual-address-switching",
          "score": 0.15119047619047618,
          "sharedProfile": true,
          "difference": "Compare written and spoken relationship registers versus Track language and relationship triggers independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare written and spoken relationship registers",
        "outline": [
          "Explain the specific decision: Compare written and spoken relationship registers",
          "Define the applicable contract and limits for Letters versus speech address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare written and spoken relationship registers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare written and spoken relationship registers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:204",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-dialogue-label-name-policy",
      "slug": "dialogue-label-name-policy",
      "name": "Dialogue label name policy",
      "category": "address",
      "urls": {
        "en": "/en/tools/dialogue-label-name-policy/",
        "ja": "/ja/tools/dialogue-label-name-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Separate screenplay speaker labels from spoken names",
      "task": "Separate screenplay speaker labels from spoken names",
      "searchIntent": {
        "primary": "Complete the task: Separate screenplay speaker labels from spoken names",
        "queryHypothesis": "dialogue label name policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate screenplay speaker labels from spoken names?",
        "When should dialogue label name policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate screenplay speaker labels from spoken names",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate screenplay speaker labels from spoken names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-dialogue-tag-rename",
          "score": 0.24404761904761904,
          "sharedProfile": false,
          "difference": "Separate screenplay speaker labels from spoken names versus Distinguish script labels from spoken name text; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-subtitle-speaker-name-fit",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate screenplay speaker labels from spoken names versus Test names in speaker labels at supplied subtitle widths; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-body-swap-name-tracking",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Separate screenplay speaker labels from spoken names versus Resolve speaker labels against mind and body state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate screenplay speaker labels from spoken names",
        "outline": [
          "Explain the specific decision: Separate screenplay speaker labels from spoken names",
          "Define the applicable contract and limits for Dialogue label name policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate screenplay speaker labels from spoken names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate screenplay speaker labels from spoken names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:205",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-multilingual-address-switching",
      "slug": "multilingual-address-switching",
      "name": "Multilingual address switching",
      "category": "address",
      "urls": {
        "en": "/en/tools/multilingual-address-switching/",
        "ja": "/ja/tools/multilingual-address-switching/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Track language and relationship triggers independently",
      "task": "Track language and relationship triggers independently",
      "searchIntent": {
        "primary": "Complete the task: Track language and relationship triggers independently",
        "queryHypothesis": "multilingual address switching",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track language and relationship triggers independently?",
        "When should multilingual address switching be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track language and relationship triggers independently",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track language and relationship triggers independently. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-formal-informal-contrast",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track language and relationship triggers independently versus Rebuild relationship distance through approved language choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Track language and relationship triggers independently versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Track language and relationship triggers independently versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track language and relationship triggers independently",
        "outline": [
          "Explain the specific decision: Track language and relationship triggers independently",
          "Define the applicable contract and limits for Multilingual address switching",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track language and relationship triggers independently; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track language and relationship triggers independently",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:206",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-address-continuity-audit",
      "slug": "address-continuity-audit",
      "name": "Address continuity audit",
      "category": "address",
      "urls": {
        "en": "/en/tools/address-continuity-audit/",
        "ja": "/ja/tools/address-continuity-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Find speaker pairs using unearned levels of familiarity",
      "task": "Find speaker pairs using unearned levels of familiarity",
      "searchIntent": {
        "primary": "Complete the task: Find speaker pairs using unearned levels of familiarity",
        "queryHypothesis": "address continuity audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find speaker pairs using unearned levels of familiarity?",
        "When should address continuity audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find speaker pairs using unearned levels of familiarity",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find speaker pairs using unearned levels of familiarity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.19,
          "sharedProfile": false,
          "difference": "Find speaker pairs using unearned levels of familiarity versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Find speaker pairs using unearned levels of familiarity versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Find speaker pairs using unearned levels of familiarity versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find speaker pairs using unearned levels of familiarity",
        "outline": [
          "Explain the specific decision: Find speaker pairs using unearned levels of familiarity",
          "Define the applicable contract and limits for Address continuity audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find speaker pairs using unearned levels of familiarity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find speaker pairs using unearned levels of familiarity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:207",
      "profileSource": "data/profiles.json#address"
    },
    {
      "id": "nw-pen-name-designer",
      "slug": "pen-name-designer",
      "name": "Pen name designer",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-designer/",
        "ja": "/ja/tools/pen-name-designer/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Match an author brief to readable signature candidates",
      "task": "Match an author brief to readable signature candidates",
      "searchIntent": {
        "primary": "Complete the task: Match an author brief to readable signature candidates",
        "queryHypothesis": "pen name designer",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match an author brief to readable signature candidates?",
        "When should pen name designer be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "authorBrief",
          "use": "State genres, intended tone and public identity preferences without requiring legal identity."
        },
        {
          "key": "candidates",
          "use": "Use supplied or original invented forms with provenance labels."
        },
        {
          "key": "surfaces",
          "use": "Select cover, spine, contributor list and spoken introduction fixtures."
        },
        {
          "key": "boundaries",
          "use": "Exclude personal details the user does not want incorporated."
        }
      ],
      "rules": [
        "Never require a legal name to generate a pen name.",
        "Show exact forms in selected layout fixtures.",
        "A local collision scan only covers the loaded corpus; external checks are dated manual notes.",
        "Any fit score is a disclosed heuristic with editable weights.",
        "Do not infer trademark, domain or platform availability.",
        "Preview initials and expanded byline as alternatives",
        "Allow a single component without fake surname",
        "Retain original alongside platform-specific fallback",
        "Mark fallback as editorial transformation, not equivalence proof",
        "Compare the same name across configured surfaces"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Never require a legal name to generate a pen name.",
        "Show exact forms in selected layout fixtures.",
        "A local collision scan only covers the loaded corpus; external checks are dated manual notes.",
        "Any fit score is a disclosed heuristic with editable weights.",
        "Do not infer trademark, domain or platform availability.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "candidate and pronunciation note",
        "byline proofs",
        "readability heuristic components",
        "creative positioning explanation",
        "verification scope and unresolved checks",
        "Two byline renderings",
        "Complete single-part credit",
        "Original and transformed forms",
        "Original and fallback with loss note",
        "Surface proof with overflow"
      ],
      "capabilities": [
        "Compare one candidate at cover and compact spine sizes.",
        "Run a blind spelling recall worksheet without revealing the intended spelling first."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The decision concerns an author's public credit, reader recall and disclosure boundaries rather than fictional character plausibility.",
        "proposedDifferenceAxes": [
          "inputs",
          "evaluation",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Match an author brief to readable signature candidates versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-pen-name-fiction",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Match an author brief to readable signature candidates versus Track multiple fictional holders of a famous author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-translation-brief",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Match an author brief to readable signature candidates versus Preserve author intent across localized bylines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A useful byline survives ordinary reader and production tasks.",
        "outline": [
          "Start with the work and the desired boundary",
          "Read a name aloud before designing its logo",
          "Cover and spine tradeoffs",
          "Two collaborators negotiate one shared byline",
          "Keep external checks precise and dated"
        ],
        "story": "Fictional example: two coauthors discover their joint byline reads like one contributor's full name. They revise the credit structure and add an accurate collaboration note rather than imply a nonexistent solo author.",
        "storyAnalysis": "Compare a new collective name with a paired byline. Explain attribution, recall and governance tradeoffs without predicting sales.",
        "evidence": "Original layout fixtures and user-authored disclosure decisions; no external availability data imported.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/pen.md",
        "localizedBodies": {
          "en": "content/en/pen.md",
          "ja": "content/ja/pen.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "medium",
      "acceptance": [
        "Changing a credit width changes measured overflow without changing the name.",
        "Excluded personal tokens never appear in generated candidates.",
        "No result claims global uniqueness.",
        "A missing external check is shown as not checked, not available.",
        "Initials preserve configured order of components",
        "One token passes structure validation",
        "Stripping punctuation does not overwrite original identity",
        "Original accents survive export in original field",
        "Narrower width flags the same long name"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:210",
      "profileSource": "data/profiles.json#pen-names",
      "absorbedModules": [
        {
          "sourceId": "nw-pen-name-initials-decision",
          "input": "initialDisplay",
          "rule": "Preview initials and expanded byline as alternatives",
          "output": "Two byline renderings",
          "acceptance": "Initials preserve configured order of components",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-mononym-author-credit",
          "input": "nameStructure=mononym",
          "rule": "Allow a single component without fake surname",
          "output": "Complete single-part credit",
          "acceptance": "One token passes structure validation",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-pen-name-punctuation-fallback",
          "input": "fallbackPunctuation",
          "rule": "Retain original alongside platform-specific fallback",
          "output": "Original and transformed forms",
          "acceptance": "Stripping punctuation does not overwrite original identity",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-pen-name-diacritic-fallback",
          "input": "fallbackDiacritics",
          "rule": "Mark fallback as editorial transformation, not equivalence proof",
          "output": "Original and fallback with loss note",
          "acceptance": "Original accents survive export in original field",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-author-byline-preview",
          "input": "candidates; surfaces; scoped fallback settings",
          "rule": "Proof an accepted identity on separate surfaces without renaming the original.",
          "output": "Measured cover/spine proofs and preserved original/variant handoff.",
          "acceptance": "Narrowing the spine changes overflow; original spelling survives fallback export.",
          "evidence": [
            "PEN-01",
            "PEN-03",
            "reports/browser-delivery-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-pen-name-typography-comparison",
          "input": "fontAndWidth",
          "rule": "Compare the same name across configured surfaces",
          "output": "Surface proof with overflow",
          "acceptance": "Narrower width flags the same long name",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "pen",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/corpus.mjs",
          "web/corpus-ui.js"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/corpus.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "sourceMode",
          "label": [
            "Generation source",
            "生成に使う資料"
          ],
          "type": "select",
          "default": "us-reference",
          "help": null,
          "options": [
            [
              "invented",
              [
                "Invented pool or manual shortlist",
                "創作プール・手動候補"
              ]
            ],
            [
              "us-reference",
              [
                "SSA + Census source components",
                "SSAとCensusの出典付き要素"
              ]
            ]
          ]
        },
        {
          "key": "tone",
          "label": [
            "Creative register",
            "創作上の方向"
          ],
          "type": "select",
          "default": "quiet",
          "help": null,
          "options": [
            [
              "quiet",
              [
                "Understated",
                "控えめ"
              ]
            ],
            [
              "bright",
              [
                "Lively",
                "軽やか"
              ]
            ],
            [
              "precise",
              [
                "Crisp",
                "端正"
              ]
            ]
          ]
        },
        {
          "key": "lockFirst",
          "label": [
            "Fixed first component · optional",
            "前半を固定・任意"
          ],
          "type": "text",
          "default": "",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "lockSurname",
          "label": [
            "Fixed last component · optional",
            "後半を固定・任意"
          ],
          "type": "text",
          "default": "",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "width",
          "label": [
            "Approximate byline budget · px",
            "署名幅の目安 · px"
          ],
          "type": "number",
          "default": 160,
          "help": null
        },
        {
          "key": "seed",
          "label": [
            "Reproducible seed",
            "再現用シード"
          ],
          "type": "text",
          "default": "woven-01",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "count",
          "label": [
            "Results · 1–30",
            "生成数 · 1〜30"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "exclude",
          "label": [
            "Excluded strings",
            "除外する文字列"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Comma-separated. Matching is case-insensitive.",
            "カンマ区切り。大文字と小文字は区別しません。"
          ]
        },
        {
          "key": "exclusionMode",
          "label": [
            "Exclusion scope",
            "除外の範囲"
          ],
          "type": "select",
          "default": "contains",
          "help": null,
          "options": [
            [
              "contains",
              [
                "Contains string",
                "文字列を含む"
              ]
            ],
            [
              "exact",
              [
                "Exact full name",
                "姓名の完全一致"
              ]
            ]
          ]
        },
        {
          "key": "candidates",
          "label": [
            "Your existing shortlist · optional",
            "既存の候補一覧・任意"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Comma-separated or one candidate per line. Locks and exclusions still apply.",
            "カンマまたは改行区切り。固定と除外は維持します。"
          ]
        },
        {
          "key": "fontFamily",
          "label": [
            "Local proof font",
            "プルーフのローカル書体"
          ],
          "type": "text",
          "default": "Georgia",
          "help": null
        },
        {
          "key": "surfaces",
          "label": [
            "Credit surfaces",
            "署名を置く面"
          ],
          "type": "textarea",
          "default": "Cover | 240 | 32\nSpine | 90 | 16",
          "help": [
            "label | inner width px | font size px",
            "ラベル | 内側の幅px | 文字サイズpx"
          ]
        },
        {
          "key": "externalChecks",
          "label": [
            "Dated manual external checks",
            "日付付きの外部確認メモ"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "scope | queried form | YYYY-MM-DD | finding. No external request is made.",
            "範囲 | 調べた表記 | YYYY-MM-DD | 結果。外部通信は行いません。"
          ]
        },
        {
          "key": "nameStructure",
          "label": [
            "Generated credit structure",
            "生成する署名の構造"
          ],
          "type": "select",
          "default": "two-part",
          "help": null,
          "options": [
            [
              "two-part",
              [
                "Two components",
                "二つの要素"
              ]
            ],
            [
              "mononym",
              [
                "One component",
                "単独の名義"
              ]
            ]
          ]
        },
        {
          "key": "punctuationFallback",
          "label": [
            "Platform punctuation fallback",
            "利用面ごとの句読点の扱い"
          ],
          "type": "select",
          "default": "keep",
          "help": null,
          "options": [
            [
              "keep",
              [
                "Keep",
                "保持"
              ]
            ],
            [
              "strip",
              [
                "Remove in fallback only",
                "代替表記のみ除去"
              ]
            ]
          ]
        },
        {
          "key": "diacriticFallback",
          "label": [
            "Platform diacritic fallback",
            "利用面ごとの付加記号の扱い"
          ],
          "type": "select",
          "default": "keep",
          "help": null,
          "options": [
            [
              "keep",
              [
                "Keep",
                "保持"
              ]
            ],
            [
              "strip",
              [
                "Remove combining marks in fallback",
                "代替表記のみ結合記号を除去"
              ]
            ]
          ]
        },
        {
          "key": "fallbackScope",
          "label": [
            "Fallback platform or credit surface",
            "代替表記を使う場所"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "givenPrefix",
          "label": [
            "Source given-name prefix",
            "資料の名の先頭文字"
          ],
          "type": "text",
          "default": "Ma",
          "help": null
        },
        {
          "key": "surnamePrefix",
          "label": [
            "Source surname prefix",
            "資料の姓の先頭文字"
          ],
          "type": "text",
          "default": "S",
          "help": null
        },
        {
          "key": "referenceVersion",
          "label": [
            "Pinned source-component version",
            "名前要素の固定した資料版"
          ],
          "type": "text",
          "default": "cd78e975ed7bb358e018dd62fbe14ced89295e9581c49172ca4eedcb011b3724:117c41cb4668727b7627b2845b6df3f83eb2a22a1813f42c0ff4bdcab86de135",
          "help": null
        },
        {
          "key": "minGivenCount",
          "label": [
            "Minimum aggregate published given-name count",
            "名の公開申請合計の下限"
          ],
          "type": "number",
          "default": 0,
          "help": null
        }
      ],
      "availableSourceManifest": "data/corpora/manifest.json"
    },
    {
      "id": "nw-pen-name-pronunciation",
      "slug": "pen-name-pronunciation",
      "name": "Pen name pronunciation",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-pronunciation/",
        "ja": "/ja/tools/pen-name-pronunciation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Produce an author approved spoken introduction and ambiguity notes",
      "task": "Produce an author approved spoken introduction and ambiguity notes",
      "searchIntent": {
        "primary": "Complete the task: Produce an author approved spoken introduction and ambiguity notes",
        "queryHypothesis": "pen name pronunciation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce an author approved spoken introduction and ambiguity notes?",
        "When should pen name pronunciation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce an author approved spoken introduction and ambiguity notes",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce an author approved spoken introduction and ambiguity notes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Produce an author approved spoken introduction and ambiguity notes versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.17575757575757575,
          "sharedProfile": false,
          "difference": "Produce an author approved spoken introduction and ambiguity notes versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-designer",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Produce an author approved spoken introduction and ambiguity notes versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce an author approved spoken introduction and ambiguity notes",
        "outline": [
          "Explain the specific decision: Produce an author approved spoken introduction and ambiguity notes",
          "Define the applicable contract and limits for Pen name pronunciation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce an author approved spoken introduction and ambiguity notes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce an author approved spoken introduction and ambiguity notes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:212",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-genre-positioning",
      "slug": "pen-name-genre-positioning",
      "name": "Pen name genre positioning",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-genre-positioning/",
        "ja": "/ja/tools/pen-name-genre-positioning/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare intended shelf signals without guaranteeing audience response",
      "task": "Compare intended shelf signals without guaranteeing audience response",
      "searchIntent": {
        "primary": "Complete the task: Compare intended shelf signals without guaranteeing audience response",
        "queryHypothesis": "pen name genre positioning",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare intended shelf signals without guaranteeing audience response?",
        "When should pen name genre positioning be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare intended shelf signals without guaranteeing audience response",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare intended shelf signals without guaranteeing audience response. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-positioning-exercise",
          "score": 0.22916666666666666,
          "sharedProfile": false,
          "difference": "Compare intended shelf signals without guaranteeing audience response versus Compare byline presentations using a declared audience brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-personal-safety-checklist",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Compare intended shelf signals without guaranteeing audience response versus Minimize volunteered identifying details without promising anonymity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-deliberate-misnaming-scene",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare intended shelf signals without guaranteeing audience response versus Track intent, harm and response without normalizing the act; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare intended shelf signals without guaranteeing audience response",
        "outline": [
          "Explain the specific decision: Compare intended shelf signals without guaranteeing audience response",
          "Define the applicable contract and limits for Pen name genre positioning",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare intended shelf signals without guaranteeing audience response; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare intended shelf signals without guaranteeing audience response",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:214",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-multi-genre-author-identities",
      "slug": "multi-genre-author-identities",
      "name": "Multi genre author identities",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/multi-genre-author-identities/",
        "ja": "/ja/tools/multi-genre-author-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Separate author brands while preserving optional reader connections",
      "task": "Separate author brands while preserving optional reader connections",
      "searchIntent": {
        "primary": "Complete the task: Separate author brands while preserving optional reader connections",
        "queryHypothesis": "multi genre author identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate author brands while preserving optional reader connections?",
        "When should multi genre author identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate author brands while preserving optional reader connections",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate author brands while preserving optional reader connections. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Separate author brands while preserving optional reader connections versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-doppelganger-cast-labeling",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Separate author brands while preserving optional reader connections versus Maintain intended likeness while preserving reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-refuses-name-disclosure",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate author brands while preserving optional reader connections versus Preserve agency while maintaining reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate author brands while preserving optional reader connections",
        "outline": [
          "Explain the specific decision: Separate author brands while preserving optional reader connections",
          "Define the applicable contract and limits for Multi genre author identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate author brands while preserving optional reader connections; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate author brands while preserving optional reader connections",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:215",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-coauthor-byline-order",
      "slug": "coauthor-byline-order",
      "name": "Coauthor byline order",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/coauthor-byline-order/",
        "ja": "/ja/tools/coauthor-byline-order/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare order, separators and visual prominence with recorded consent",
      "task": "Compare order, separators and visual prominence with recorded consent",
      "searchIntent": {
        "primary": "Complete the task: Compare order, separators and visual prominence with recorded consent",
        "queryHypothesis": "coauthor byline order",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare order, separators and visual prominence with recorded consent?",
        "When should coauthor byline order be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare order, separators and visual prominence with recorded consent",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare order, separators and visual prominence with recorded consent. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-order-policy",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare order, separators and visual prominence with recorded consent versus Keep display order consistent across narration and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-order-style-sheet",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Compare order, separators and visual prominence with recorded consent versus Record context dependent display order rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-order-clue",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare order, separators and visual prominence with recorded consent versus Establish the convention before making a reversal meaningful; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare order, separators and visual prominence with recorded consent",
        "outline": [
          "Explain the specific decision: Compare order, separators and visual prominence with recorded consent",
          "Define the applicable contract and limits for Coauthor byline order",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare order, separators and visual prominence with recorded consent; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare order, separators and visual prominence with recorded consent",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:217",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-manga-creator-signature",
      "slug": "manga-creator-signature",
      "name": "Manga creator signature",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/manga-creator-signature/",
        "ja": "/ja/tools/manga-creator-signature/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Coordinate a pen name with a compact production credit",
      "task": "Coordinate a pen name with a compact production credit",
      "searchIntent": {
        "primary": "Complete the task: Coordinate a pen name with a compact production credit",
        "queryHypothesis": "manga creator signature",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate a pen name with a compact production credit?",
        "When should manga creator signature be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate a pen name with a compact production credit",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate a pen name with a compact production credit. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manga-character-name-card",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Coordinate a pen name with a compact production credit versus Produce identity, reading and role cards for the production team; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-ending-signature",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Coordinate a pen name with a compact production credit versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-android-cover-identity",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Coordinate a pen name with a compact production credit versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate a pen name with a compact production credit",
        "outline": [
          "Explain the specific decision: Coordinate a pen name with a compact production credit",
          "Define the applicable contract and limits for Manga creator signature",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate a pen name with a compact production credit; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate a pen name with a compact production credit",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:218",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-script-artist-credit-pairing",
      "slug": "script-artist-credit-pairing",
      "name": "Script artist credit pairing",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/script-artist-credit-pairing/",
        "ja": "/ja/tools/script-artist-credit-pairing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Distinguish writer and artist names in limited credit space",
      "task": "Distinguish writer and artist names in limited credit space",
      "searchIntent": {
        "primary": "Complete the task: Distinguish writer and artist names in limited credit space",
        "queryHypothesis": "script artist credit pairing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish writer and artist names in limited credit space?",
        "When should script artist credit pairing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish writer and artist names in limited credit space",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish writer and artist names in limited credit space. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-research-collective-credit-names",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Distinguish writer and artist names in limited credit space versus Distinguish institutional authorship from fictional individuals; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-author-credit-governance",
          "score": 0.08421052631578947,
          "sharedProfile": true,
          "difference": "Distinguish writer and artist names in limited credit space versus Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Distinguish writer and artist names in limited credit space versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish writer and artist names in limited credit space",
        "outline": [
          "Explain the specific decision: Distinguish writer and artist names in limited credit space",
          "Define the applicable contract and limits for Script artist credit pairing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish writer and artist names in limited credit space; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish writer and artist names in limited credit space",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:219",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-anonymous-publication-byline",
      "slug": "anonymous-publication-byline",
      "name": "Anonymous publication byline",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/anonymous-publication-byline/",
        "ja": "/ja/tools/anonymous-publication-byline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare anonymity language and reader expectations without privacy guarantees",
      "task": "Compare anonymity language and reader expectations without privacy guarantees",
      "searchIntent": {
        "primary": "Complete the task: Compare anonymity language and reader expectations without privacy guarantees",
        "queryHypothesis": "anonymous publication byline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare anonymity language and reader expectations without privacy guarantees?",
        "When should anonymous publication byline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare anonymity language and reader expectations without privacy guarantees",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare anonymity language and reader expectations without privacy guarantees. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-translated-name-clue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare anonymity language and reader expectations without privacy guarantees versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-anonymous-service-arc",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Compare anonymity language and reader expectations without privacy guarantees versus Show the choice to act without seeking a named reputation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-forged-byline-clue",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Compare anonymity language and reader expectations without privacy guarantees versus Compare fictional attribution patterns without asserting real authentication expertise; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare anonymity language and reader expectations without privacy guarantees",
        "outline": [
          "Explain the specific decision: Compare anonymity language and reader expectations without privacy guarantees",
          "Define the applicable contract and limits for Anonymous publication byline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare anonymity language and reader expectations without privacy guarantees; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare anonymity language and reader expectations without privacy guarantees",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:220",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-identity-boundary",
      "slug": "pen-name-identity-boundary",
      "name": "Pen name identity boundary",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-identity-boundary/",
        "ja": "/ja/tools/pen-name-identity-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Record what public biography may connect to a private identity",
      "task": "Record what public biography may connect to a private identity",
      "searchIntent": {
        "primary": "Complete the task: Record what public biography may connect to a private identity",
        "queryHypothesis": "pen name identity boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record what public biography may connect to a private identity?",
        "When should pen name identity boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record what public biography may connect to a private identity",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record what public biography may connect to a private identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-arena-fighter-ring-name",
          "score": 0.26,
          "sharedProfile": false,
          "difference": "Record what public biography may connect to a private identity versus Connect public persona, announcer readability and private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Record what public biography may connect to a private identity versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-outgrows-stage-identity",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Record what public biography may connect to a private identity versus Connect public persona change to career and self understanding; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record what public biography may connect to a private identity",
        "outline": [
          "Explain the specific decision: Record what public biography may connect to a private identity",
          "Define the applicable contract and limits for Pen name identity boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record what public biography may connect to a private identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record what public biography may connect to a private identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:221",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-existing-pen-name-revision",
      "slug": "existing-pen-name-revision",
      "name": "Existing pen name revision",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/existing-pen-name-revision/",
        "ja": "/ja/tools/existing-pen-name-revision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Plan continuity notes and old to new credit mappings",
      "task": "Plan continuity notes and old to new credit mappings",
      "searchIntent": {
        "primary": "Complete the task: Plan continuity notes and old to new credit mappings",
        "queryHypothesis": "existing pen name revision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to plan continuity notes and old to new credit mappings?",
        "When should existing pen name revision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Plan continuity notes and old to new credit mappings",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Plan continuity notes and old to new credit mappings. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Plan continuity notes and old to new credit mappings versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-future-proofing",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Plan continuity notes and old to new credit mappings versus Test planned genres and credit formats against a candidate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hidden-author-identity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Plan continuity notes and old to new credit mappings versus Plan fictional manuscript credit and eventual author disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Plan continuity notes and old to new credit mappings",
        "outline": [
          "Explain the specific decision: Plan continuity notes and old to new credit mappings",
          "Define the applicable contract and limits for Existing pen name revision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Plan continuity notes and old to new credit mappings; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Plan continuity notes and old to new credit mappings",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:222",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-author-rebrand-timeline",
      "slug": "author-rebrand-timeline",
      "name": "Author rebrand timeline",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/author-rebrand-timeline/",
        "ja": "/ja/tools/author-rebrand-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Schedule name changes across a backlist and active series",
      "task": "Schedule name changes across a backlist and active series",
      "searchIntent": {
        "primary": "Complete the task: Schedule name changes across a backlist and active series",
        "queryHypothesis": "author rebrand timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to schedule name changes across a backlist and active series?",
        "When should author rebrand timeline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Schedule name changes across a backlist and active series",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Schedule name changes across a backlist and active series. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-school-uniform-name-patch",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Schedule name changes across a backlist and active series versus Track prop name changes across character transfers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Schedule name changes across a backlist and active series versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-live-roleplay-alias-reveal",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Schedule name changes across a backlist and active series versus Schedule badge or roster changes at an agreed story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Schedule name changes across a backlist and active series",
        "outline": [
          "Explain the specific decision: Schedule name changes across a backlist and active series",
          "Define the applicable contract and limits for Author rebrand timeline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Schedule name changes across a backlist and active series; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Schedule name changes across a backlist and active series",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:223",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-search-collision-log",
      "slug": "pen-name-search-collision-log",
      "name": "Pen name search collision log",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-search-collision-log/",
        "ja": "/ja/tools/pen-name-search-collision-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Record dated external checks without claiming exclusivity",
      "task": "Record dated external checks without claiming exclusivity",
      "searchIntent": {
        "primary": "Complete the task: Record dated external checks without claiming exclusivity",
        "queryHypothesis": "pen name search collision log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record dated external checks without claiming exclusivity?",
        "When should pen name search collision log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Keep dated domain checks separate from naming quality"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record dated external checks without claiming exclusivity",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist",
        "Checked-at and scope"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record dated external checks without claiming exclusivity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-public-figure-collision",
          "score": 0.33888888888888885,
          "sharedProfile": false,
          "difference": "Record dated external checks without claiming exclusivity versus Structure external checks without claiming uniqueness or clearance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Record dated external checks without claiming exclusivity versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-surname-locality-check",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Record dated external checks without claiming exclusivity versus Record geographic evidence without claiming universal distribution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record dated external checks without claiming exclusivity",
        "outline": [
          "Explain the specific decision: Record dated external checks without claiming exclusivity",
          "Define the applicable contract and limits for Pen name search collision log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record dated external checks without claiming exclusivity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record dated external checks without claiming exclusivity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Missing check reads not checked"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:226",
      "profileSource": "data/profiles.json#pen-names",
      "absorbedModules": [
        {
          "sourceId": "nw-pen-name-domain-checklist",
          "input": "externalChecks.domain",
          "rule": "Keep dated domain checks separate from naming quality",
          "output": "Checked-at and scope",
          "acceptance": "Missing check reads not checked",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-pen-name-bookstore-ambiguity",
      "slug": "pen-name-bookstore-ambiguity",
      "name": "Pen name bookstore ambiguity",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-bookstore-ambiguity/",
        "ja": "/ja/tools/pen-name-bookstore-ambiguity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Distinguish an author from similarly named authors in a manual review",
      "task": "Distinguish an author from similarly named authors in a manual review",
      "searchIntent": {
        "primary": "Complete the task: Distinguish an author from similarly named authors in a manual review",
        "queryHypothesis": "pen name bookstore ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish an author from similarly named authors in a manual review?",
        "When should pen name bookstore ambiguity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish an author from similarly named authors in a manual review",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish an author from similarly named authors in a manual review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-designer",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Distinguish an author from similarly named authors in a manual review versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Distinguish an author from similarly named authors in a manual review versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-pen-name-fiction",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Distinguish an author from similarly named authors in a manual review versus Track multiple fictional holders of a famous author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish an author from similarly named authors in a manual review",
        "outline": [
          "Explain the specific decision: Distinguish an author from similarly named authors in a manual review",
          "Define the applicable contract and limits for Pen name bookstore ambiguity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish an author from similarly named authors in a manual review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish an author from similarly named authors in a manual review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:227",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-signature-legibility",
      "slug": "pen-name-signature-legibility",
      "name": "Pen name signature legibility",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-signature-legibility/",
        "ja": "/ja/tools/pen-name-signature-legibility/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare supplied signatures at realistic display sizes",
      "task": "Compare supplied signatures at realistic display sizes",
      "searchIntent": {
        "primary": "Complete the task: Compare supplied signatures at realistic display sizes",
        "queryHypothesis": "pen name signature legibility",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare supplied signatures at realistic display sizes?",
        "When should pen name signature legibility be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare supplied signatures at realistic display sizes",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare supplied signatures at realistic display sizes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-signature-discrepancy-clue",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Compare supplied signatures at realistic display sizes versus Compare supplied signatures and plot relevant differences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-social-handle-mapping",
          "score": 0.15119047619047618,
          "sharedProfile": true,
          "difference": "Compare supplied signatures at realistic display sizes versus Keep display name and platform identifier decisions separate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-android-cover-identity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Compare supplied signatures at realistic display sizes versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare supplied signatures at realistic display sizes",
        "outline": [
          "Explain the specific decision: Compare supplied signatures at realistic display sizes",
          "Define the applicable contract and limits for Pen name signature legibility",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare supplied signatures at realistic display sizes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare supplied signatures at realistic display sizes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:228",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-social-handle-mapping",
      "slug": "pen-name-social-handle-mapping",
      "name": "Pen name social handle mapping",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-social-handle-mapping/",
        "ja": "/ja/tools/pen-name-social-handle-mapping/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Keep display name and platform identifier decisions separate",
      "task": "Keep display name and platform identifier decisions separate",
      "searchIntent": {
        "primary": "Complete the task: Keep display name and platform identifier decisions separate",
        "queryHypothesis": "pen name social handle mapping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep display name and platform identifier decisions separate?",
        "When should pen name social handle mapping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep display name and platform identifier decisions separate",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep display name and platform identifier decisions separate. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-signature-legibility",
          "score": 0.15119047619047618,
          "sharedProfile": true,
          "difference": "Keep display name and platform identifier decisions separate versus Compare supplied signatures at realistic display sizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-android-cover-identity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Keep display name and platform identifier decisions separate versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-in-records",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Keep display name and platform identifier decisions separate versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep display name and platform identifier decisions separate",
        "outline": [
          "Explain the specific decision: Keep display name and platform identifier decisions separate",
          "Define the applicable contract and limits for Pen name social handle mapping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep display name and platform identifier decisions separate; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep display name and platform identifier decisions separate",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:230",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-translation-brief",
      "slug": "pen-name-translation-brief",
      "name": "Pen name translation brief",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-translation-brief/",
        "ja": "/ja/tools/pen-name-translation-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Preserve author intent across localized bylines",
      "task": "Preserve author intent across localized bylines",
      "searchIntent": {
        "primary": "Complete the task: Preserve author intent across localized bylines",
        "queryHypothesis": "pen name translation brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve author intent across localized bylines?",
        "When should pen name translation brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve author intent across localized bylines",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve author intent across localized bylines. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-consistency-audit",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Preserve author intent across localized bylines versus Find mismatched author forms across a supplied publication list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Preserve author intent across localized bylines versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-designer",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Preserve author intent across localized bylines versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve author intent across localized bylines",
        "outline": [
          "Explain the specific decision: Preserve author intent across localized bylines",
          "Define the applicable contract and limits for Pen name translation brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve author intent across localized bylines; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve author intent across localized bylines",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:231",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-japanese-pen-name-reading",
      "slug": "japanese-pen-name-reading",
      "name": "Japanese pen name reading",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/japanese-pen-name-reading/",
        "ja": "/ja/tools/japanese-pen-name-reading/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Store approved kana and romanized credits alongside the name",
      "task": "Store approved kana and romanized credits alongside the name",
      "searchIntent": {
        "primary": "Complete the task: Store approved kana and romanized credits alongside the name",
        "queryHypothesis": "japanese pen name reading",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to store approved kana and romanized credits alongside the name?",
        "When should japanese pen name reading be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Store approved kana and romanized credits alongside the name",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Store approved kana and romanized credits alongside the name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.19791666666666666,
          "sharedProfile": false,
          "difference": "Store approved kana and romanized credits alongside the name versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-reading-collision",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Store approved kana and romanized credits alongside the name versus Detect different written names with the same confirmed reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Store approved kana and romanized credits alongside the name versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Store approved kana and romanized credits alongside the name",
        "outline": [
          "Explain the specific decision: Store approved kana and romanized credits alongside the name",
          "Define the applicable contract and limits for Japanese pen name reading",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Store approved kana and romanized credits alongside the name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Store approved kana and romanized credits alongside the name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:232",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-bilingual-author-byline",
      "slug": "bilingual-author-byline",
      "name": "Bilingual author byline",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/bilingual-author-byline/",
        "ja": "/ja/tools/bilingual-author-byline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Coordinate English and Japanese forms without counting two tools",
      "task": "Coordinate English and Japanese forms without counting two tools",
      "searchIntent": {
        "primary": "Complete the task: Coordinate English and Japanese forms without counting two tools",
        "queryHypothesis": "bilingual author byline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate English and Japanese forms without counting two tools?",
        "When should bilingual author byline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate English and Japanese forms without counting two tools",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate English and Japanese forms without counting two tools. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-localization-name-map",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Coordinate English and Japanese forms without counting two tools versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-publication-byline",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Coordinate English and Japanese forms without counting two tools versus Compare anonymity language and reader expectations without privacy guarantees; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-forged-byline-clue",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Coordinate English and Japanese forms without counting two tools versus Compare fictional attribution patterns without asserting real authentication expertise; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate English and Japanese forms without counting two tools",
        "outline": [
          "Explain the specific decision: Coordinate English and Japanese forms without counting two tools",
          "Define the applicable contract and limits for Bilingual author byline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate English and Japanese forms without counting two tools; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate English and Japanese forms without counting two tools",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:233",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-audio-introduction",
      "slug": "pen-name-audio-introduction",
      "name": "Pen name audio introduction",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-audio-introduction/",
        "ja": "/ja/tools/pen-name-audio-introduction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Test host introductions and spoken acknowledgments",
      "task": "Test host introductions and spoken acknowledgments",
      "searchIntent": {
        "primary": "Complete the task: Test host introductions and spoken acknowledgments",
        "queryHypothesis": "pen name audio introduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test host introductions and spoken acknowledgments?",
        "When should pen name audio introduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test host introductions and spoken acknowledgments",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test host introductions and spoken acknowledgments. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Test host introductions and spoken acknowledgments versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audiobook-chapter-name-headings",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Test host introductions and spoken acknowledgments versus Test spoken headings for identity spoilers and clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-only-identity-introduction",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Test host introductions and spoken acknowledgments versus Introduce characters without relying on visual name cards; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test host introductions and spoken acknowledgments",
        "outline": [
          "Explain the specific decision: Test host introductions and spoken acknowledgments",
          "Define the applicable contract and limits for Pen name audio introduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test host introductions and spoken acknowledgments; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test host introductions and spoken acknowledgments",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:236",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-negative-association-review",
      "slug": "pen-name-negative-association-review",
      "name": "Pen name negative association review",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-negative-association-review/",
        "ja": "/ja/tools/pen-name-negative-association-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Structure human checks for unintended associations",
      "task": "Structure human checks for unintended associations",
      "searchIntent": {
        "primary": "Complete the task: Structure human checks for unintended associations",
        "queryHypothesis": "pen name negative association review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to structure human checks for unintended associations?",
        "When should pen name negative association review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Structure human checks for unintended associations",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Structure human checks for unintended associations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-offensive-association-review",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Structure human checks for unintended associations versus Route context dependent issues to human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-gender-assumption-audit",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Structure human checks for unintended associations versus Flag unintended target language signals for human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-public-figure-collision",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Structure human checks for unintended associations versus Structure external checks without claiming uniqueness or clearance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Structure human checks for unintended associations",
        "outline": [
          "Explain the specific decision: Structure human checks for unintended associations",
          "Define the applicable contract and limits for Pen name negative association review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Structure human checks for unintended associations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Structure human checks for unintended associations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:238",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-personal-safety-checklist",
      "slug": "pen-name-personal-safety-checklist",
      "name": "Pen name personal safety checklist",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-personal-safety-checklist/",
        "ja": "/ja/tools/pen-name-personal-safety-checklist/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Minimize volunteered identifying details without promising anonymity",
      "task": "Minimize volunteered identifying details without promising anonymity",
      "searchIntent": {
        "primary": "Complete the task: Minimize volunteered identifying details without promising anonymity",
        "queryHypothesis": "pen name personal safety checklist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to minimize volunteered identifying details without promising anonymity?",
        "When should pen name personal safety checklist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Minimize volunteered identifying details without promising anonymity",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Minimize volunteered identifying details without promising anonymity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-genre-positioning",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Minimize volunteered identifying details without promising anonymity versus Compare intended shelf signals without guaranteeing audience response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-search-collision-log",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Minimize volunteered identifying details without promising anonymity versus Record dated external checks without claiming exclusivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-publication-byline",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Minimize volunteered identifying details without promising anonymity versus Compare anonymity language and reader expectations without privacy guarantees; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Minimize volunteered identifying details without promising anonymity",
        "outline": [
          "Explain the specific decision: Minimize volunteered identifying details without promising anonymity",
          "Define the applicable contract and limits for Pen name personal safety checklist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Minimize volunteered identifying details without promising anonymity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Minimize volunteered identifying details without promising anonymity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:239",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-collective-author-credit-governance",
      "slug": "collective-author-credit-governance",
      "name": "Collective author credit governance",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/collective-author-credit-governance/",
        "ja": "/ja/tools/collective-author-credit-governance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Collaborative fiction, comics and game-writing teams planning collective credits.",
      "scenario": "A contributor leaves a collective before a new edition; old title pages should retain their recorded credits while a new credit proposal needs the correct scope.",
      "task": "Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change.",
      "searchIntent": {
        "primary": "Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change.",
        "queryHypothesis": "collective author credit governance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Does a contributor leaving alter the credits printed in an earlier edition?",
        "Which internal review records still apply after the collective byline changes?"
      ],
      "inputs": [
        {
          "key": "members",
          "use": "Stable contributor IDs and exact chosen credit strings."
        },
        {
          "key": "membership",
          "use": "Explicit join/leave intervals in the authored production timeline."
        },
        {
          "key": "editions",
          "use": "Stable work/edition IDs, release point and collective byline proposal."
        },
        {
          "key": "contributions",
          "use": "Edition-specific member roles and chosen attribution scope."
        },
        {
          "key": "reviewRecords",
          "use": "Author-supplied granted/declined/unknown internal review for a specific credit/version, not inferred consent."
        },
        {
          "key": "snapshots",
          "use": "Optional exact supplied historical credit records to compare with a new proposal; preserved by the computation, not a tamper-proof archive."
        }
      ],
      "rules": [
        "Membership does not automatically prove contribution or permission for a particular edition.",
        "A member leaving does not silently remove their contribution from a historical snapshot.",
        "Internal review records must match the exact edition/byline version; no blanket transfer to revised credits.",
        "Unknown or declined records remain unresolved; no invented approval.",
        "Freeze historical output separately from a current proposal and list their differences.",
        "Preserve contributor IDs when display strings coincide.",
        "Provide planning records only, not legal advice, signatures or external verification."
      ],
      "requiredData": [
        {
          "description": "Original fictional collective and edition fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied internal review records; no external people database or contract interpretation",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Membership does not automatically prove contribution or permission for a particular edition.",
        "A member leaving does not silently remove their contribution from a historical snapshot.",
        "Internal review records must match the exact edition/byline version; no blanket transfer to revised credits.",
        "Unknown or declined records remain unresolved; no invented approval.",
        "Freeze historical output separately from a current proposal and list their differences.",
        "Preserve contributor IDs when display strings coincide.",
        "Provide planning records only, not legal advice, signatures or external verification."
      ],
      "outputs": [
        "Edition credit proposal with contributing identities and roles",
        "Unknown/declined/version-mismatched review list",
        "Historical snapshot versus new proposal change sheet",
        "Private credit-review package; nothing sent to collaborators"
      ],
      "capabilities": [
        "Retain an earlier edition’s credit after membership changes without automatically authorizing the next edition.",
        "Show which contributor and byline-version review records need renewed attention."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The work is edition-scoped credit continuity, not generating a pen name or measuring one byline. A single current member list cannot correctly represent both a historical edition and a new proposal.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "pen-name-designer",
          "difference": "The pen tool designs and proofs an individual credit. This workbench associates editions, contributor roles, membership intervals, explicit internal review records and frozen credit snapshots; it does not certify legal permission."
        }
      },
      "nearestTools": [
        {
          "id": "nw-research-collective-credit-names",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change. versus Distinguish institutional authorship from fictional individuals; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hidden-author-identity",
          "score": 0.0925438596491228,
          "sharedProfile": false,
          "difference": "Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change. versus Plan fictional manuscript credit and eventual author disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-mind-speaker-labels",
          "score": 0.08611111111111111,
          "sharedProfile": false,
          "difference": "Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change. versus Track which voice acts for a distributed consciousness; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "The name on a title page describes a particular collaboration at a particular edition.",
        "outline": [
          "Begin with two title pages, not one current roster",
          "Credit and membership answer different questions",
          "An earlier edition is a recorded snapshot",
          "Original scene: a collective name on the reprint table",
          "Prepare questions without manufacturing permission"
        ],
        "story": "A collective prepares a revised comic after one member leaves. Removing the departed artist from the old edition would rewrite its history; carrying forward every internal review would ignore the new title-page text. The team preserves one snapshot and prepares a clearly unresolved new proposal.",
        "storyAnalysis": "A new collective pen name can conceal neither the old contribution nor the edition-specific decisions. Distinguish a display change from a permission record.",
        "evidence": "Fictional contributors and explicit review-state fixtures; no actual approvals or legal conclusions.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/collectiveCredit.md",
        "localizedBodies": {
          "en": "content/en/collectiveCredit.md",
          "ja": "content/ja/collectiveCredit.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A departure changes current membership but not a frozen earlier credit.",
        "A non-contributing current member is not silently credited as an edition contributor.",
        "A changed byline version invalidates reuse of a narrowly scoped review record.",
        "Unknown does not become granted.",
        "Duplicate contributor IDs conflict; identical credit strings do not merge contributors.",
        "Export states internal planning scope and sends no messages or approvals."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:240",
      "profileSource": "data/profiles.json#pen-names",
      "specBatch": "batch-03",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Dedicated state, scoped references and failure handling; no production time or cost estimate fabricated."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-collaborative-pen-name",
          "input": "Stable member IDs; explicit edition byline and contribution display/role/order/visibility; recorded membership; exact scoped authored review records and supplied historical snapshots.",
          "rule": "Do not infer contribution or review from membership. Match version plus exact byline and full credit package; keep unknown/declined/stale records unresolved. Preserve supplied history and private IDs independently of public displays.",
          "output": "Proposed public credit text, retained historical comparison and a private record/question package; nothing is sent. Pen-name generation and typography remain in the connected pen tool.",
          "acceptance": "Former contributor remains when edition work remains; current non-contributor is not invented; same-version wording or visibility edits invalidate stale records; explicit capture/replacement/guarded undo works; public draft omits internal fields.",
          "evidence": [
            "CREDIT-01",
            "CREDIT-02",
            "CREDIT-03",
            "CREDIT-04",
            "CREDIT-05",
            "CREDIT-06",
            "CREDIT-07",
            "CREDIT-11",
            "reports/collective-credit-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-pen-name-contributor-agreement-brief",
          "input": "Stable member IDs; explicit edition byline and contribution display/role/order/visibility; recorded membership; exact scoped authored review records and supplied historical snapshots.",
          "rule": "Do not infer contribution or review from membership. Match version plus exact byline and full credit package; keep unknown/declined/stale records unresolved. Preserve supplied history and private IDs independently of public displays.",
          "output": "Proposed public credit text, retained historical comparison and a private record/question package; nothing is sent. Pen-name generation and typography remain in the connected pen tool.",
          "acceptance": "Former contributor remains when edition work remains; current non-contributor is not invented; same-version wording or visibility edits invalidate stale records; explicit capture/replacement/guarded undo works; public draft omits internal fields.",
          "evidence": [
            "CREDIT-01",
            "CREDIT-02",
            "CREDIT-03",
            "CREDIT-04",
            "CREDIT-05",
            "CREDIT-06",
            "CREDIT-07",
            "CREDIT-11",
            "reports/collective-credit-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "collectiveCredit",
        "engineFiles": [
          "web/collective-credit.mjs",
          "web/credit-capture.js",
          "scripts/render-credit-capture.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/collective-credit.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "members",
          "label": [
            "Private contributor roster · JSON",
            "内部用の参加者名簿・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"a\",\n    \"recordLabel\": \"Arden Reed\"\n  },\n  {\n    \"id\": \"b\",\n    \"recordLabel\": \"Briar Slate\"\n  },\n  {\n    \"id\": \"c\",\n    \"recordLabel\": \"Cora Vale\"\n  }\n]",
          "help": null
        },
        {
          "key": "membership",
          "label": [
            "Recorded membership intervals · JSON",
            "記録した所属期間・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"member\": \"a\",\n    \"from\": 0,\n    \"to\": null\n  },\n  {\n    \"member\": \"b\",\n    \"from\": 0,\n    \"to\": 4\n  },\n  {\n    \"member\": \"c\",\n    \"from\": 4,\n    \"to\": null\n  }\n]",
          "help": [
            "Half-open [from,to); departure does not erase an earlier edition contribution. Null end is open.",
            "半開区間[from,to)。脱退しても過去の版の貢献を消しません。終わりなしはnullです。"
          ]
        },
        {
          "key": "editions",
          "label": [
            "Edition proposals · JSON",
            "版ごとの案・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"first\",\n    \"work\": \"comic-one\",\n    \"version\": \"v1\",\n    \"releasePoint\": 2,\n    \"byline\": \"Woven Kite\",\n    \"approvers\": []\n  },\n  {\n    \"id\": \"revised\",\n    \"work\": \"comic-one\",\n    \"version\": \"v2\",\n    \"releasePoint\": 6,\n    \"byline\": \"Woven Kite Studio\",\n    \"approvers\": []\n  }\n]",
          "help": [
            "All contributors require a scoped record; approvers adds explicitly named reviewers, not credits. These are planning records, not verified permission.",
            "全貢献者に範囲付き記録が必要です。approversは確認者を明示して加え、クレジットには加えません。計画用の記録で、検証した許可ではありません。"
          ]
        },
        {
          "key": "contributions",
          "label": [
            "Exact edition credits · JSON",
            "版の正確なクレジット・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"edition\": \"first\",\n    \"member\": \"a\",\n    \"display\": \"A. Reed\",\n    \"role\": \"Writing\",\n    \"order\": 1,\n    \"visibility\": \"public\"\n  },\n  {\n    \"edition\": \"first\",\n    \"member\": \"b\",\n    \"display\": \"B. Slate\",\n    \"role\": \"Art\",\n    \"order\": 2,\n    \"visibility\": \"public\"\n  },\n  {\n    \"edition\": \"revised\",\n    \"member\": \"a\",\n    \"display\": \"A. Reed\",\n    \"role\": \"Writing\",\n    \"order\": 1,\n    \"visibility\": \"public\"\n  },\n  {\n    \"edition\": \"revised\",\n    \"member\": \"b\",\n    \"display\": \"B. Slate\",\n    \"role\": \"Art\",\n    \"order\": 2,\n    \"visibility\": \"public\"\n  }\n]",
          "help": [
            "edition, member, exact display/role, unique order, public/internal visibility. Membership never generates a contribution automatically.",
            "edition、member、正確なdisplay/role、固有のorder、public/internalのvisibility。所属から貢献は自動生成しません。"
          ]
        },
        {
          "key": "reviewRecords",
          "label": [
            "Authored internal review records · JSON",
            "作者が入力する内部確認記録・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"r1\",\n    \"member\": \"a\",\n    \"edition\": \"first\",\n    \"version\": \"v1\",\n    \"byline\": \"Woven Kite\",\n    \"credits\": [\n      {\n        \"member\": \"a\",\n        \"display\": \"A. Reed\",\n        \"role\": \"Writing\",\n        \"order\": 1,\n        \"visibility\": \"public\"\n      },\n      {\n        \"member\": \"b\",\n        \"display\": \"B. Slate\",\n        \"role\": \"Art\",\n        \"order\": 2,\n        \"visibility\": \"public\"\n      }\n    ],\n    \"decision\": \"granted\",\n    \"note\": \"Fictional example record for the exact first-edition content.\"\n  },\n  {\n    \"id\": \"r2\",\n    \"member\": \"b\",\n    \"edition\": \"first\",\n    \"version\": \"v1\",\n    \"byline\": \"Woven Kite\",\n    \"credits\": [\n      {\n        \"member\": \"a\",\n        \"display\": \"A. Reed\",\n        \"role\": \"Writing\",\n        \"order\": 1,\n        \"visibility\": \"public\"\n      },\n      {\n        \"member\": \"b\",\n        \"display\": \"B. Slate\",\n        \"role\": \"Art\",\n        \"order\": 2,\n        \"visibility\": \"public\"\n      }\n    ],\n    \"decision\": \"granted\",\n    \"note\": \"Fictional example record; not actual consent.\"\n  },\n  {\n    \"id\": \"r3\",\n    \"member\": \"a\",\n    \"edition\": \"revised\",\n    \"version\": \"v2\",\n    \"byline\": \"Woven Kite Studio\",\n    \"credits\": [\n      {\n        \"member\": \"a\",\n        \"display\": \"A. Reed\",\n        \"role\": \"Writing\",\n        \"order\": 1,\n        \"visibility\": \"public\"\n      },\n      {\n        \"member\": \"b\",\n        \"display\": \"B. Slate\",\n        \"role\": \"Art\",\n        \"order\": 2,\n        \"visibility\": \"public\"\n      }\n    ],\n    \"decision\": \"granted\",\n    \"note\": \"Fictional record for the new collective display.\"\n  },\n  {\n    \"id\": \"r4\",\n    \"member\": \"b\",\n    \"edition\": \"revised\",\n    \"version\": \"v1\",\n    \"byline\": \"Woven Kite\",\n    \"credits\": [\n      {\n        \"member\": \"a\",\n        \"display\": \"A. Reed\",\n        \"role\": \"Writing\",\n        \"order\": 1,\n        \"visibility\": \"public\"\n      },\n      {\n        \"member\": \"b\",\n        \"display\": \"B. Slate\",\n        \"role\": \"Art\",\n        \"order\": 2,\n        \"visibility\": \"public\"\n      }\n    ],\n    \"decision\": \"granted\",\n    \"note\": \"Old scope; does not silently authorize the new version.\"\n  }\n]",
          "help": [
            "Each record includes the exact reviewed byline and full credit package. Same version alone does not make changed content match. granted/declined/unknown are unverified input states.",
            "確認した正確なbylineと完全なcreditsを含めます。同じ版番号でも内容が違えば一致しません。granted/declined/unknownは未検証の入力状態です。"
          ],
          "maxLength": 180000,
          "requiredInProject": true
        },
        {
          "key": "snapshots",
          "label": [
            "Supplied historical snapshots · JSON",
            "入力した過去の記録・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"printed-first\",\n    \"edition\": \"first\",\n    \"work\": \"comic-one\",\n    \"version\": \"v1\",\n    \"releasePoint\": 2,\n    \"byline\": \"Woven Kite\",\n    \"credits\": [\n      {\n        \"member\": \"a\",\n        \"display\": \"A. Reed\",\n        \"role\": \"Writing\",\n        \"order\": 1,\n        \"visibility\": \"public\"\n      },\n      {\n        \"member\": \"b\",\n        \"display\": \"B. Slate\",\n        \"role\": \"Art\",\n        \"order\": 2,\n        \"visibility\": \"public\"\n      }\n    ]\n  }\n]",
          "help": [
            "The computation retains these exact supplied records. This is not a tamper-proof publication archive.",
            "計算は入力した記録を保持しますが、改変不能の出版記録ではありません。"
          ],
          "maxLength": 180000,
          "requiredInProject": true
        }
      ]
    },
    {
      "id": "nw-inherited-pen-name-fiction",
      "slug": "inherited-pen-name-fiction",
      "name": "Inherited pen name fiction",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/inherited-pen-name-fiction/",
        "ja": "/ja/tools/inherited-pen-name-fiction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Track multiple fictional holders of a famous author identity",
      "task": "Track multiple fictional holders of a famous author identity",
      "searchIntent": {
        "primary": "Complete the task: Track multiple fictional holders of a famous author identity",
        "queryHypothesis": "inherited pen name fiction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track multiple fictional holders of a famous author identity?",
        "When should inherited pen name fiction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track multiple fictional holders of a famous author identity",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track multiple fictional holders of a famous author identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track multiple fictional holders of a famous author identity versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-designer",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Track multiple fictional holders of a famous author identity versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Track multiple fictional holders of a famous author identity versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track multiple fictional holders of a famous author identity",
        "outline": [
          "Explain the specific decision: Track multiple fictional holders of a famous author identity",
          "Define the applicable contract and limits for Inherited pen name fiction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track multiple fictional holders of a famous author identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track multiple fictional holders of a famous author identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:241",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-serial-author-handle-migration",
      "slug": "serial-author-handle-migration",
      "name": "Serial author handle migration",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/serial-author-handle-migration/",
        "ja": "/ja/tools/serial-author-handle-migration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Reconcile old community handles with a book byline",
      "task": "Reconcile old community handles with a book byline",
      "searchIntent": {
        "primary": "Complete the task: Reconcile old community handles with a book byline",
        "queryHypothesis": "serial author handle migration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile old community handles with a book byline?",
        "When should serial author handle migration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile old community handles with a book byline",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile old community handles with a book byline. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-save-migration-renamed-npc",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Reconcile old community handles with a book byline versus Preserve old save IDs while changing approved display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-robot-serial-to-personal-name",
          "score": 0.1061111111111111,
          "sharedProfile": false,
          "difference": "Reconcile old community handles with a book byline versus Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-migration-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Reconcile old community handles with a book byline versus Track retained, adapted and imposed forms across a journey; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile old community handles with a book byline",
        "outline": [
          "Explain the specific decision: Reconcile old community handles with a book byline",
          "Define the applicable contract and limits for Serial author handle migration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile old community handles with a book byline; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile old community handles with a book byline",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:242",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-author-note-signoff",
      "slug": "author-note-signoff",
      "name": "Author note signoff",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/author-note-signoff/",
        "ja": "/ja/tools/author-note-signoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Align informal signoff with the chosen public author identity",
      "task": "Align informal signoff with the chosen public author identity",
      "searchIntent": {
        "primary": "Complete the task: Align informal signoff with the chosen public author identity",
        "queryHypothesis": "author note signoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to align informal signoff with the chosen public author identity?",
        "When should author note signoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Align informal signoff with the chosen public author identity",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Align informal signoff with the chosen public author identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-inherited-pen-name-fiction",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Align informal signoff with the chosen public author identity versus Track multiple fictional holders of a famous author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Align informal signoff with the chosen public author identity versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Align informal signoff with the chosen public author identity versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Align informal signoff with the chosen public author identity",
        "outline": [
          "Explain the specific decision: Align informal signoff with the chosen public author identity",
          "Define the applicable contract and limits for Author note signoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Align informal signoff with the chosen public author identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Align informal signoff with the chosen public author identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:243",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-illustrator-novelist-dual-credit",
      "slug": "illustrator-novelist-dual-credit",
      "name": "Illustrator novelist dual credit",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/illustrator-novelist-dual-credit/",
        "ja": "/ja/tools/illustrator-novelist-dual-credit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Present two creative roles without implying two separate people",
      "task": "Present two creative roles without implying two separate people",
      "searchIntent": {
        "primary": "Complete the task: Present two creative roles without implying two separate people",
        "queryHypothesis": "illustrator novelist dual credit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to present two creative roles without implying two separate people?",
        "When should illustrator novelist dual credit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Present two creative roles without implying two separate people",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Present two creative roles without implying two separate people. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-similarity-pair-test",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Present two creative roles without implying two separate people versus Ask readers whether two supplied names refer to different people; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-author-byline",
          "score": 0.1,
          "sharedProfile": true,
          "difference": "Present two creative roles without implying two separate people versus Coordinate English and Japanese forms without counting two tools; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-found-family-address-system",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Present two creative roles without implying two separate people versus Design elective kinship terms without implying blood relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Present two creative roles without implying two separate people",
        "outline": [
          "Explain the specific decision: Present two creative roles without implying two separate people",
          "Define the applicable contract and limits for Illustrator novelist dual credit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Present two creative roles without implying two separate people; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Present two creative roles without implying two separate people",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:244",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pseudonym-disclosure-statement",
      "slug": "pseudonym-disclosure-statement",
      "name": "Pseudonym disclosure statement",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pseudonym-disclosure-statement/",
        "ja": "/ja/tools/pseudonym-disclosure-statement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Draft accurate disclosure levels selected by the author",
      "task": "Draft accurate disclosure levels selected by the author",
      "searchIntent": {
        "primary": "Complete the task: Draft accurate disclosure levels selected by the author",
        "queryHypothesis": "pseudonym disclosure statement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to draft accurate disclosure levels selected by the author?",
        "When should pseudonym disclosure statement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Draft accurate disclosure levels selected by the author",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Draft accurate disclosure levels selected by the author. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hidden-author-identity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Draft accurate disclosure levels selected by the author versus Plan fictional manuscript credit and eventual author disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pseudonym-evidence",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Draft accurate disclosure levels selected by the author versus Distinguish documented pseudonyms from author invented analogues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-katakana-identity-choice",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Draft accurate disclosure levels selected by the author versus Explain author selected script effects without claiming universal meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Draft accurate disclosure levels selected by the author",
        "outline": [
          "Explain the specific decision: Draft accurate disclosure levels selected by the author",
          "Define the applicable contract and limits for Pseudonym disclosure statement",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Draft accurate disclosure levels selected by the author; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Draft accurate disclosure levels selected by the author",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:245",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-candidate-decision",
      "slug": "pen-name-candidate-decision",
      "name": "Pen name candidate decision",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-candidate-decision/",
        "ja": "/ja/tools/pen-name-candidate-decision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare a fixed shortlist using published heuristic criteria",
      "task": "Compare a fixed shortlist using published heuristic criteria",
      "searchIntent": {
        "primary": "Complete the task: Compare a fixed shortlist using published heuristic criteria",
        "queryHypothesis": "pen name candidate decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare a fixed shortlist using published heuristic criteria?",
        "When should pen name candidate decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare a fixed shortlist using published heuristic criteria",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare a fixed shortlist using published heuristic criteria. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-candidate-comparison",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Compare a fixed shortlist using published heuristic criteria versus Compare a fixed shortlist against task specific criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-naming-deadline",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare a fixed shortlist using published heuristic criteria versus Choose among supplied candidates using explicit rejection criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-positioning-exercise",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare a fixed shortlist using published heuristic criteria versus Compare byline presentations using a declared audience brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare a fixed shortlist using published heuristic criteria",
        "outline": [
          "Explain the specific decision: Compare a fixed shortlist using published heuristic criteria",
          "Define the applicable contract and limits for Pen name candidate decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare a fixed shortlist using published heuristic criteria; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare a fixed shortlist using published heuristic criteria",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:246",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-future-proofing",
      "slug": "pen-name-future-proofing",
      "name": "Pen name future proofing",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-future-proofing/",
        "ja": "/ja/tools/pen-name-future-proofing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Test planned genres and credit formats against a candidate",
      "task": "Test planned genres and credit formats against a candidate",
      "searchIntent": {
        "primary": "Complete the task: Test planned genres and credit formats against a candidate",
        "queryHypothesis": "pen name future proofing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test planned genres and credit formats against a candidate?",
        "When should pen name future proofing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test planned genres and credit formats against a candidate",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test planned genres and credit formats against a candidate. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test planned genres and credit formats against a candidate versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-audio-introduction",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Test planned genres and credit formats against a candidate versus Test host introductions and spoken acknowledgments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-existing-pen-name-revision",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Test planned genres and credit formats against a candidate versus Plan continuity notes and old to new credit mappings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test planned genres and credit formats against a candidate",
        "outline": [
          "Explain the specific decision: Test planned genres and credit formats against a candidate",
          "Define the applicable contract and limits for Pen name future proofing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test planned genres and credit formats against a candidate; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test planned genres and credit formats against a candidate",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:247",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-pen-name-consistency-audit",
      "slug": "pen-name-consistency-audit",
      "name": "Pen name consistency audit",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-consistency-audit/",
        "ja": "/ja/tools/pen-name-consistency-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Find mismatched author forms across a supplied publication list",
      "task": "Find mismatched author forms across a supplied publication list",
      "searchIntent": {
        "primary": "Complete the task: Find mismatched author forms across a supplied publication list",
        "queryHypothesis": "pen name consistency audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find mismatched author forms across a supplied publication list?",
        "When should pen name consistency audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find mismatched author forms across a supplied publication list",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find mismatched author forms across a supplied publication list. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-translation-brief",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Find mismatched author forms across a supplied publication list versus Preserve author intent across localized bylines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-morphology-collision-audit",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Find mismatched author forms across a supplied publication list versus Detect when generated forms collapse across grammatical operations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Find mismatched author forms across a supplied publication list versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find mismatched author forms across a supplied publication list",
        "outline": [
          "Explain the specific decision: Find mismatched author forms across a supplied publication list",
          "Define the applicable contract and limits for Pen name consistency audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find mismatched author forms across a supplied publication list; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find mismatched author forms across a supplied publication list",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:249",
      "profileSource": "data/profiles.json#pen-names"
    },
    {
      "id": "nw-japanese-character-name-record",
      "slug": "japanese-character-name-record",
      "name": "Japanese character name record",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-character-name-record/",
        "ja": "/ja/tools/japanese-character-name-record/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Keep kanji, kana and approved pronunciation as separate fields",
      "task": "Keep kanji, kana and approved pronunciation as separate fields",
      "searchIntent": {
        "primary": "Complete the task: Keep kanji, kana and approved pronunciation as separate fields",
        "queryHypothesis": "japanese character name record",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep kanji, kana and approved pronunciation as separate fields?",
        "When should japanese character name record be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "written",
          "use": "Preserve the exact author-selected kanji or kana form."
        },
        {
          "key": "readingKana",
          "use": "Require explicit confirmed or invented reading status."
        },
        {
          "key": "evidence",
          "use": "Attach URL, locator, scope and uncertainty to each factual claim."
        },
        {
          "key": "displayPolicy",
          "use": "Choose ruby, inline kana and plain text fallback."
        }
      ],
      "rules": [
        "Never manufacture a reading from kanji glosses.",
        "Keep attested, author-approved and invented reading statuses distinct.",
        "Compare normalized kana for collision detection while preserving original display.",
        "An official registration source does not validate a particular fictional name.",
        "Export ruby and plain text reading pairs with the same identity ID.",
        "Preserve small kana during display and controlled comparison",
        "Separate attestation from author association",
        "Label invented reading in all result formats",
        "Keep written form and reading together without ruby"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Never manufacture a reading from kanji glosses.",
        "Keep attested, author-approved and invented reading statuses distinct.",
        "Compare normalized kana for collision detection while preserving original display.",
        "An official registration source does not validate a particular fictional name.",
        "Export ruby and plain text reading pairs with the same identity ID.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "written and kana fields",
        "reading status and evidence",
        "creative association field clearly labeled",
        "ruby proof and plain text fallback",
        "unverified claim warnings",
        "Exact reading plus normalized comparison",
        "Typed claim fields",
        "Persistent reading-status label",
        "Plain paired form"
      ],
      "capabilities": [
        "Detect two written forms that share a confirmed kana reading.",
        "Export the same approved record for lettering and translator handoff."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is an evidence-linked written-form and reading record; guessing a Japanese reading from generic name strings would corrupt the result.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "rules",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-pen-name-reading",
          "score": 0.19791666666666666,
          "sharedProfile": false,
          "difference": "Keep kanji, kana and approved pronunciation as separate fields versus Store approved kana and romanized credits alongside the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-kana-only-character-identity",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Keep kanji, kana and approved pronunciation as separate fields versus Evaluate a supplied kana name in the story's reference system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Keep kanji, kana and approved pronunciation as separate fields versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Written form, reading and creative interpretation are three different decisions.",
        "outline": [
          "Keep a name record rather than a kanji meaning collage",
          "What evidence supports a reading",
          "Ruby is presentation, not proof",
          "A library card clue with a withheld reading",
          "When to request Japanese editorial review"
        ],
        "story": "Fictional example: a comic withholds the reading on a library card until a character introduces themselves. The later ruby reveals a narrator's earlier mistaken assumption, not a false dictionary claim.",
        "storyAnalysis": "Compare an actual alternative attested reading, an explicitly invented reading and a purely graphic clue. Each requires a different fairness explanation.",
        "evidence": "MOJ establishes that written name and reading are recorded separately in a specific institutional context; W3C supports flexible name fields. No name-specific reading corpus has been imported.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/japanese.md",
        "localizedBodies": {
          "en": "content/en/japanese.md",
          "ja": "content/ja/japanese.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Missing kana returns reading unknown and never a guessed pronunciation.",
        "An invented reading is labeled in every export.",
        "Changing a kanji gloss does not change the approved reading.",
        "A license-unreviewed dictionary entry cannot enter a redistributable name corpus.",
        "Small kana cannot be silently expanded in export",
        "Creative association never appears as sourced etymology",
        "Export retains invented status",
        "Plain export does not drop reading or status"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:252",
      "profileSource": "data/profiles.json#japanese-writing",
      "absorbedModules": [
        {
          "sourceId": "nw-japanese-name-small-kana-audit",
          "input": "confirmedKana",
          "rule": "Preserve small kana during display and controlled comparison",
          "output": "Exact reading plus normalized comparison",
          "acceptance": "Small kana cannot be silently expanded in export",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-japanese-name-fact-versus-association",
          "input": "claimType",
          "rule": "Separate attestation from author association",
          "output": "Typed claim fields",
          "acceptance": "Creative association never appears as sourced etymology",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-japanese-invented-reading-disclosure",
          "input": "readingStatus",
          "rule": "Label invented reading in all result formats",
          "output": "Persistent reading-status label",
          "acceptance": "Export retains invented status",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-japanese-name-plain-text-export",
          "input": "exportFormat=plain",
          "rule": "Keep written form and reading together without ruby",
          "output": "Plain paired form",
          "acceptance": "Plain export does not drop reading or status",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "japanese",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/corpus.mjs",
          "web/corpus-ui.js"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/corpus.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "names",
          "label": [
            "Written forms and readings",
            "表記と読み"
          ],
          "type": "textarea",
          "default": "a | 空織 | あおり | invented |\nb | 蒼織 | アオリ | invented |\nc | 光乃 | | unknown |",
          "help": [
            "ID | written form | kana | approved / invented / attested / unknown | source URL. Examples are fictional choices, not attested readings.",
            "ID | 表記 | 仮名 | approved / invented / attested / unknown | 出典URL。初期例は創作上の設定であり、実在の読みの根拠ではありません。"
          ]
        },
        {
          "key": "evidence",
          "label": [
            "Claim evidence and creative notes",
            "根拠と創作上のメモ"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | source locator | claim scope | creative association | cleared only if reviewed for intended reuse",
            "ID | 出典内の位置 | 主張の範囲 | 創作上の連想 | 利用条件確認済みの場合のみ cleared"
          ]
        }
      ],
      "availableSourceManifest": "data/corpora/manifest.json"
    },
    {
      "id": "nw-japanese-surname-reading-choice",
      "slug": "japanese-surname-reading-choice",
      "name": "Japanese surname reading choice",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-surname-reading-choice/",
        "ja": "/ja/tools/japanese-surname-reading-choice/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Compare sourced readings without guessing from individual kanji",
      "task": "Compare sourced readings without guessing from individual kanji",
      "searchIntent": {
        "primary": "Complete the task: Compare sourced readings without guessing from individual kanji",
        "queryHypothesis": "japanese surname reading choice",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare sourced readings without guessing from individual kanji?",
        "When should japanese surname reading choice be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare sourced readings without guessing from individual kanji",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare sourced readings without guessing from individual kanji. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Compare sourced readings without guessing from individual kanji versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-same-writing-different-reading",
          "score": 0.17222222222222222,
          "sharedProfile": true,
          "difference": "Compare sourced readings without guessing from individual kanji versus Require explicit readings and ambiguity disclosures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.17083333333333334,
          "sharedProfile": true,
          "difference": "Compare sourced readings without guessing from individual kanji versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare sourced readings without guessing from individual kanji",
        "outline": [
          "Explain the specific decision: Compare sourced readings without guessing from individual kanji",
          "Define the applicable contract and limits for Japanese surname reading choice",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare sourced readings without guessing from individual kanji; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare sourced readings without guessing from individual kanji",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:253",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-given-name-reading-choice",
      "slug": "japanese-given-name-reading-choice",
      "name": "Japanese given name reading choice",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-given-name-reading-choice/",
        "ja": "/ja/tools/japanese-given-name-reading-choice/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Attach evidence to each candidate reading",
      "task": "Attach evidence to each candidate reading",
      "searchIntent": {
        "primary": "Complete the task: Attach evidence to each candidate reading",
        "queryHypothesis": "japanese given name reading choice",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to attach evidence to each candidate reading?",
        "When should japanese given name reading choice be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Attach evidence to each candidate reading",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Attach evidence to each candidate reading. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-pronunciation-provenance",
          "score": 0.37142857142857144,
          "sharedProfile": false,
          "difference": "Attach evidence to each candidate reading versus Attach approved audio or reading evidence to each entry; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Attach evidence to each candidate reading versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-reading-collision",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Attach evidence to each candidate reading versus Detect different written names with the same confirmed reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Attach evidence to each candidate reading",
        "outline": [
          "Explain the specific decision: Attach evidence to each candidate reading",
          "Define the applicable contract and limits for Japanese given name reading choice",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Attach evidence to each candidate reading; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Attach evidence to each candidate reading",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:254",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-full-name-rhythm",
      "slug": "japanese-full-name-rhythm",
      "name": "Japanese full name rhythm",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-full-name-rhythm/",
        "ja": "/ja/tools/japanese-full-name-rhythm/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fiction, comic and game authors placing a chosen name inside an authored chant, song or verse.",
      "scenario": "A public chorus can fit the character’s chosen three-unit name but a casually substituted shorter form leaves a required position empty; the author must decide whether to change the line or the relationship implied by the short form.",
      "task": "Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation.",
      "searchIntent": {
        "primary": "Fit a supplied character-name reading into an authored verse or chant.",
        "queryHypothesis": "fit character name into song meter",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can an optional position still require a particular mark when occupied?",
        "Can a pickup licence shorten the name?",
        "Why can one displayed trace stand for many minimum alignments?"
      ],
      "inputs": [
        {
          "key": "variants",
          "type": "textarea",
          "purpose": "1–12 {id,name,units} objects; 1–24 units per name. Each unit is exactly {text,stress}; 0/1 are authored prominence marks and null is unknown. These are not inferred syllables, morae or Japanese accent."
        },
        {
          "key": "before",
          "type": "textarea",
          "purpose": "0–16 authored units. Only these units may become a licensed pickup outside the grid; no name unit can be removed."
        },
        {
          "key": "after",
          "type": "textarea",
          "purpose": "0–16 units, with the same explicit text/stress contract. Only these may become an external ending."
        },
        {
          "key": "pattern",
          "type": "textarea",
          "purpose": "1–60 {stress,required,hard} slots. Stress 0/1 requests that mark; null accepts either. required=false permits an empty slot; hard=false permits a known mismatch at cost 3. This grid is your fiction, not a verse tradition certification."
        },
        {
          "key": "pickup",
          "type": "number",
          "purpose": "Explicit task-specific bounded numeric control."
        },
        {
          "key": "ending",
          "type": "number",
          "purpose": "Explicit task-specific bounded numeric control."
        },
        {
          "key": "sampleLimit",
          "type": "number",
          "purpose": "Explicit task-specific bounded numeric control."
        },
        {
          "key": "context",
          "type": "textarea",
          "purpose": "≤1000 units; preserved in private copies and audits. Association and emotional purpose are author choices."
        }
      ],
      "rules": [
        "All readings are explicit user-authored units, each with text and a 0/1/null prominence mark. 1–12 variants with 1–24 name units, before/after arrays each ≤16 units and a 1–60-slot explicit grid. No inferred Japanese pronunciation, mora, syllable, accent or verse tradition.",
        "Slot occupancy and prominence constraints are independent. Required slots must be occupied; optional slots may be skipped. Known hard mismatches are forbidden, soft ones cost 3; unknown requested marks remain unknown at cost 2.",
        "Pickup and ending licences each 0–2 units can move only a prefix of before or suffix of after outside the grid. Every name unit is retained, ordered and inside the grid; no hidden stretching, splitting, merging or repetition.",
        "Enumerate permitted boundary choices and run a finite dynamic program per choice. BigInt counts cover all permitted alignments and all minimum-cost alignments independently of 1–12 displayed minimum witnesses. Costs also include skipped slots and external units at 1 each. Heuristic editing convention, not artistic score.",
        "Failed variants remain visible. A no-boundary-change relaxed-hard diagnostic can expose one hard conflict, but never counts as a valid alignment or exhaustive/minimum-edit repair.",
        "Private copies, favorites, comparisons, audits and saved projects retain source readings, marks, chosen line context and original constraints."
      ],
      "requiredData": [
        {
          "description": "Original fictional hall chorus, Iria/Iri supplied unit fixtures and binary grid.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-authored readings and prominence choices; no linguistic corpus is asserted.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "All readings are explicit user-authored units, each with text and a 0/1/null prominence mark. 1–12 variants with 1–24 name units, before/after arrays each ≤16 units and a 1–60-slot explicit grid. No inferred Japanese pronunciation, mora, syllable, accent or verse tradition.",
        "Slot occupancy and prominence constraints are independent. Required slots must be occupied; optional slots may be skipped. Known hard mismatches are forbidden, soft ones cost 3; unknown requested marks remain unknown at cost 2.",
        "Pickup and ending licences each 0–2 units can move only a prefix of before or suffix of after outside the grid. Every name unit is retained, ordered and inside the grid; no hidden stretching, splitting, merging or repetition.",
        "Enumerate permitted boundary choices and run a finite dynamic program per choice. BigInt counts cover all permitted alignments and all minimum-cost alignments independently of 1–12 displayed minimum witnesses. Costs also include skipped slots and external units at 1 each. Heuristic editing convention, not artistic score.",
        "Failed variants remain visible. A no-boundary-change relaxed-hard diagnostic can expose one hard conflict, but never counts as a valid alignment or exhaustive/minimum-edit repair.",
        "Private copies, favorites, comparisons, audits and saved projects retain source readings, marks, chosen line context and original constraints."
      ],
      "outputs": [
        "Per-variant all/minimum alignment counts and public heuristic cost.",
        "Ordered slot traces preserving before/name/after provenance, unknown marks and soft mismatches.",
        "Licensed pickup/ending material and sample-limit disclosure.",
        "Failed-variant shape diagnostics and separate relaxed hard-conflict witnesses.",
        "Private source-bound audit and editable project."
      ],
      "capabilities": [
        "Exact counting across optional-slot and boundary choices, with independent minimum-cost witness cap.",
        "Hard/soft/unknown prominence handling without inferred readings, retaining every name unit.",
        "Explicit failed alternatives with length diagnostics and invalid relaxed-conflict witnesses."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Spoken cast rehearsal compares readings and reported durations; this task places ordered units into a line’s required/optional positions under hard/soft marks and boundary licences. It needs occupancy DP, exact alternative counts and unit-to-slot traces, which audio comparison or visual fitting cannot supply.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "spoken-cast-rehearsal",
          "difference": "Duration and reading collisions concern a cast heard aloud. Here the primary task is preserving a full chosen name inside an authored verse structure, with optional positions, surrounding units, forbidden mismatches and explicitly licensed boundaries."
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-voicing-variation-ledger",
          "score": 0.15583333333333332,
          "sharedProfile": true,
          "difference": "Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation. versus Store documented variants without inventing alternation rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.15087719298245614,
          "sharedProfile": true,
          "difference": "Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation. versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-sibling-name-distinction",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation. versus Compare reading and graphic separation within one household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "The line must make room for a chosen form without silently changing the relationship carried by its public use; alignment is production evidence rather than pronunciation authority.",
        "outline": [
          "Leave room for the chosen name",
          "Original chorus and the final promise",
          "Declare readings",
          "Occupancy versus prominence",
          "Boundary licences preserve the person",
          "Disclosed minimum-cost compromises",
          "Diagnose before renaming",
          "Rehearsal handoff with reasons"
        ],
        "story": "A community chorus replaces Iria with Iri to fit a printed heading, then discovers the shorter supplied reading leaves a required slot empty. Iria chooses the full form for the public promise, with the short form remaining in a private exchange.",
        "storyAnalysis": "If the person explicitly chose Iri for public use, retaining the long form could become exclusion. Revising a slot or surrounding phrase can honor that choice; no calculation decides consent or authenticity.",
        "evidence": "Original complete EN/JA manuscripts and executable finite grid fixtures; no real-language accent, mora or tradition claims.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/nameMeter.md",
        "localizedBodies": {
          "en": "content/en/nameMeter.md",
          "ja": "content/ja/nameMeter.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default Iria aligns once; Iri has no legal alignment and remains visible.",
        "Making fourth position optional admits the short variant in one alignment with cost 1.",
        "Hard conflict excludes, soft conflict costs 3, unknown requested mark costs 2 and remains null.",
        "Pickup/ending licences change surrounding-unit placement but cannot delete a name unit.",
        "24 units in 60 unconstrained optional slots yield exact 36052387482172425 alignments even with witness cap 1.",
        "Both localized initial pages, four actual viewport submissions and actual copy/export/project workflows must be recorded."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:255",
      "profileSource": "data/profiles.json#japanese-writing",
      "specBatch": "batch-15",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Finite alignment DP with independent exact counts, boundary enumeration, minimum witnesses, explicit uncertainty and invalid diagnostic separation."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "nameMeter",
        "engineFiles": [
          "web/name-meter.mjs",
          "web/name-meter-tool.mjs",
          "web/name-meter-view.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/name-meter.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "variants",
          "label": [
            "Name pronunciation variants · JSON",
            "名前の読み案・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"iria\",\n    \"name\": \"Iria\",\n    \"units\": [\n      {\n        \"text\": \"I\",\n        \"stress\": 1\n      },\n      {\n        \"text\": \"ri\",\n        \"stress\": 0\n      },\n      {\n        \"text\": \"a\",\n        \"stress\": 0\n      }\n    ]\n  },\n  {\n    \"id\": \"iri\",\n    \"name\": \"Iri\",\n    \"units\": [\n      {\n        \"text\": \"I\",\n        \"stress\": 1\n      },\n      {\n        \"text\": \"ri\",\n        \"stress\": 0\n      }\n    ]\n  }\n]",
          "help": [
            "1–12 {id,name,units} objects; 1–24 units per name. Each unit is exactly {text,stress}; 0/1 are authored prominence marks and null is unknown. These are not inferred syllables, morae or Japanese accent.",
            "{id,name,units}を1〜12件、名前の単位は1〜24件。単位は{text,stress}のみ。0/1は作者が決める目立ち方、nullは不明です。音節、モーラ、日本語アクセントを推定しません。"
          ],
          "maxLength": 20000
        },
        {
          "key": "before",
          "label": [
            "Units before the name · JSON",
            "名前の前の単位・JSON"
          ],
          "type": "textarea",
          "default": "[{\"text\":\"we\",\"stress\":0}]",
          "help": [
            "0–16 authored units. Only these units may become a licensed pickup outside the grid; no name unit can be removed.",
            "作者指定の0〜16単位。グリッド外の前拍にできるのはこの部分だけで、名前の単位は削れません。"
          ],
          "maxLength": 4000
        },
        {
          "key": "after",
          "label": [
            "Units after the name · JSON",
            "名前の後の単位・JSON"
          ],
          "type": "textarea",
          "default": "[{\"text\":\"stay\",\"stress\":1}]",
          "help": [
            "0–16 units, with the same explicit text/stress contract. Only these may become an external ending.",
            "同じtext/stressの規約で0〜16単位。外側の後置にできるのはこの部分だけです。"
          ],
          "maxLength": 4000
        },
        {
          "key": "pattern",
          "label": [
            "Authored beat slots · JSON",
            "作者指定の拍位置・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"stress\": 0,\n    \"required\": true,\n    \"hard\": true\n  },\n  {\n    \"stress\": 1,\n    \"required\": true,\n    \"hard\": true\n  },\n  {\n    \"stress\": 0,\n    \"required\": true,\n    \"hard\": true\n  },\n  {\n    \"stress\": 0,\n    \"required\": true,\n    \"hard\": true\n  },\n  {\n    \"stress\": 1,\n    \"required\": true,\n    \"hard\": true\n  }\n]",
          "help": [
            "1–60 {stress,required,hard} slots. Stress 0/1 requests that mark; null accepts either. required=false permits an empty slot; hard=false permits a known mismatch at cost 3. This grid is your fiction, not a verse tradition certification.",
            "{stress,required,hard}の位置1〜60件。stressの0/1は要求、nullはどちらでも可。required=falseは空きを許可し、hard=falseは既知の不一致をコスト3で許可します。作者の設定で、詩型の伝統の認定ではありません。"
          ],
          "maxLength": 8000
        },
        {
          "key": "pickup",
          "label": [
            "Licensed pickup units · 0–2",
            "許可する前拍の単位数・0〜2"
          ],
          "type": "number",
          "default": 0,
          "help": null
        },
        {
          "key": "ending",
          "label": [
            "Licensed external ending units · 0–2",
            "許可するグリッド外の後置・0〜2"
          ],
          "type": "number",
          "default": 0,
          "help": null
        },
        {
          "key": "sampleLimit",
          "label": [
            "Minimum-cost witnesses per variant · 1–12",
            "各案の最小コスト表示例・1〜12"
          ],
          "type": "number",
          "default": 4,
          "help": null
        },
        {
          "key": "context",
          "label": [
            "Private scene and intended emphasis",
            "非公開の場面・意図する強調"
          ],
          "type": "textarea",
          "default": "A community chorus must make room for Iria’s chosen form without swallowing the promise on stay.",
          "help": [
            "≤1000 units; preserved in private copies and audits. Association and emotional purpose are author choices.",
            "1000単位以内。非公開コピーと検証に残します。連想や感情の目的は作者の選択です。"
          ],
          "maxLength": 1000
        }
      ]
    },
    {
      "id": "nw-japanese-same-reading-different-writing",
      "slug": "japanese-same-reading-different-writing",
      "name": "Japanese same reading different writing",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-same-reading-different-writing/",
        "ja": "/ja/tools/japanese-same-reading-different-writing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Distinguish character identity from graphic alternatives",
      "task": "Distinguish character identity from graphic alternatives",
      "searchIntent": {
        "primary": "Complete the task: Distinguish character identity from graphic alternatives",
        "queryHypothesis": "japanese same reading different writing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish character identity from graphic alternatives?",
        "When should japanese same reading different writing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish character identity from graphic alternatives",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish character identity from graphic alternatives. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-same-writing-different-reading",
          "score": 0.35,
          "sharedProfile": true,
          "difference": "Distinguish character identity from graphic alternatives versus Require explicit readings and ambiguity disclosures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish character identity from graphic alternatives versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish character identity from graphic alternatives versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish character identity from graphic alternatives",
        "outline": [
          "Explain the specific decision: Distinguish character identity from graphic alternatives",
          "Define the applicable contract and limits for Japanese same reading different writing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish character identity from graphic alternatives; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish character identity from graphic alternatives",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:256",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-same-writing-different-reading",
      "slug": "japanese-same-writing-different-reading",
      "name": "Japanese same writing different reading",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-same-writing-different-reading/",
        "ja": "/ja/tools/japanese-same-writing-different-reading/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Require explicit readings and ambiguity disclosures",
      "task": "Require explicit readings and ambiguity disclosures",
      "searchIntent": {
        "primary": "Complete the task: Require explicit readings and ambiguity disclosures",
        "queryHypothesis": "japanese same writing different reading",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require explicit readings and ambiguity disclosures?",
        "When should japanese same writing different reading be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require explicit readings and ambiguity disclosures",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require explicit readings and ambiguity disclosures. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-same-reading-different-writing",
          "score": 0.35,
          "sharedProfile": true,
          "difference": "Require explicit readings and ambiguity disclosures versus Distinguish character identity from graphic alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.17222222222222222,
          "sharedProfile": true,
          "difference": "Require explicit readings and ambiguity disclosures versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.16499999999999998,
          "sharedProfile": true,
          "difference": "Require explicit readings and ambiguity disclosures versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require explicit readings and ambiguity disclosures",
        "outline": [
          "Explain the specific decision: Require explicit readings and ambiguity disclosures",
          "Define the applicable contract and limits for Japanese same writing different reading",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require explicit readings and ambiguity disclosures; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require explicit readings and ambiguity disclosures",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:257",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-furigana-introduction-plan",
      "slug": "japanese-furigana-introduction-plan",
      "name": "Japanese furigana introduction plan",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-furigana-introduction-plan/",
        "ja": "/ja/tools/japanese-furigana-introduction-plan/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Schedule reading support at first and later appearances",
      "task": "Schedule reading support at first and later appearances",
      "searchIntent": {
        "primary": "Complete the task: Schedule reading support at first and later appearances",
        "queryHypothesis": "japanese furigana introduction plan",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to schedule reading support at first and later appearances?",
        "When should japanese furigana introduction plan be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Schedule reading support at first and later appearances",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Schedule reading support at first and later appearances. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.2844444444444444,
          "sharedProfile": true,
          "difference": "Schedule reading support at first and later appearances versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-dialogue-balloon",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Schedule reading support at first and later appearances versus Preview line breaks and reading support in constrained balloons; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-vertical-comic-name-pacing",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Schedule reading support at first and later appearances versus Schedule first name displays across scrolling episode beats; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Schedule reading support at first and later appearances",
        "outline": [
          "Explain the specific decision: Schedule reading support at first and later appearances",
          "Define the applicable contract and limits for Japanese furigana introduction plan",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Schedule reading support at first and later appearances; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Schedule reading support at first and later appearances",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:258",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-ruby-layout",
      "slug": "japanese-name-ruby-layout",
      "name": "Japanese name ruby layout",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-ruby-layout/",
        "ja": "/ja/tools/japanese-name-ruby-layout/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Comic letterers, fiction layout editors and creators handing author-approved or explicitly fictional name annotations to production.",
      "scenario": "A two-part stage name has one whole-name invented reading. A letterer must decide whether the supplied reading belongs to the whole name or to separately authored base segments; splitting it mechanically would invent a correspondence. A narrow vertical credit also needs a real browser proof rather than a width estimate alone.",
      "task": "Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading.",
      "searchIntent": {
        "primary": "Prepare name ruby annotation markup and inspect exact base-reading associations in a bounded layout.",
        "queryHypothesis": "Japanese name ruby layout",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can a whole-name reading be split automatically across kanji?",
        "Why can the same annotation fit horizontally but overflow a vertical frame?",
        "Does a rendered ruby proof establish the reading or font coverage?"
      ],
      "inputs": [
        {
          "key": "records",
          "use": "Stable record/person IDs, exact base text and ordered segments containing explicit base, annotation and plain/mono/group association. Concatenated segments must reproduce the base literally; null annotations remain unresolved."
        },
        {
          "key": "writingMode",
          "use": "Horizontal or vertical-right proof changes inline/block axes and actual browser placement, not the name or reading."
        },
        {
          "key": "baseSize",
          "use": "Declared base font size for measured proof; never a claim about production print size without the actual process."
        },
        {
          "key": "rubyRatio",
          "use": "Annotation font-size ratio; compare the resulting rendered bounds rather than declaring a universal legibility threshold."
        },
        {
          "key": "frameWidth",
          "use": "Physical CSS-pixel frame width for overflow measurement."
        },
        {
          "key": "frameHeight",
          "use": "Physical CSS-pixel frame height; vertical flow needs a distinct inline extent."
        },
        {
          "key": "fontFamily",
          "use": "Local font stack; actual loaded font and glyph coverage remain distinct issues."
        },
        {
          "key": "lineHeight",
          "use": "Authored base-line spacing in the bounded proof; annotation and frame checks use actual rendered rectangles."
        }
      ],
      "rules": [
        "Require literal ordered segment concatenation to equal the declared base; do not normalize or repair the spelling.",
        "Mono association requires one authored base grapheme; group association can bind several graphemes as a unit. Never divide an annotation to invent a per-character reading.",
        "Plain segments contain no annotation. A declared but missing annotation remains unresolved; do not silently replace it with a guessed reading.",
        "Escape every text node in exported HTML and include readable fallback punctuation; no supplied string becomes executable markup.",
        "Keep person and proof-record identity separate; two forms of one person and equal displays of different people must retain their keys.",
        "Report actual browser overflow only after rendering; an engine-only or initial HTML result must say measurement is pending, not that it fits.",
        "A proof uses a documented browser layout policy, not a claim of complete JLReq/JIS conformance, font coverage or certified print readability.",
        "Grouping changes the annotation contract and break units; do not obtain apparent fit by silently splitting the name or dropping ruby."
      ],
      "requiredData": [
        {
          "description": "Original explicit fictional name/annotation fixtures and deliberately mismatched association examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied approved or explicitly invented readings; no automatic kanji-to-reading source inference",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Require literal ordered segment concatenation to equal the declared base; do not normalize or repair the spelling.",
        "Mono association requires one authored base grapheme; group association can bind several graphemes as a unit. Never divide an annotation to invent a per-character reading.",
        "Plain segments contain no annotation. A declared but missing annotation remains unresolved; do not silently replace it with a guessed reading.",
        "Escape every text node in exported HTML and include readable fallback punctuation; no supplied string becomes executable markup.",
        "Keep person and proof-record identity separate; two forms of one person and equal displays of different people must retain their keys.",
        "Report actual browser overflow only after rendering; an engine-only or initial HTML result must say measurement is pending, not that it fits.",
        "A proof uses a documented browser layout policy, not a claim of complete JLReq/JIS conformance, font coverage or certified print readability.",
        "Grouping changes the annotation contract and break units; do not obtain apparent fit by silently splitting the name or dropping ruby."
      ],
      "outputs": [
        "Exact base/annotation association map with unresolved and conflict reasons",
        "Escaped HTML ruby markup and readable plain-text handoff preserving supplied grouping",
        "Actual current-browser proof dimensions and horizontal/vertical frame overflow, or an explicit pending measurement state",
        "Identity-scoped comparison of two annotation contracts without treating one as a new person"
      ],
      "capabilities": [
        "Validate whole-name versus explicit single-grapheme annotation boundaries without inventing a reading split.",
        "Measure rendered ruby in a bounded horizontal or vertical proof and compare actual block/inline overflow while retaining original associations."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary output is a production annotation contract and safe reusable markup with visible association boundaries. Inputs require exact segment-to-base reconstruction and explicit annotation scope; outputs include association maps and actual layout measurements. The reading ledger records evidence and whole-name alternatives, while the manga lettering proof currently measures horizontal full-name spans. Neither validates segmented ruby markup or measures a vertical annotated frame.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "japanese-character-name-record",
          "difference": "A recorded reading can be an input, but it does not imply per-character reading boundaries. This task consumes explicit segment associations, validates exact reconstruction, preserves unresolved annotations, produces escaped markup and checks current browser geometry. It does not recommend readings, certify orthography or replace the source ledger. Recorded local implementation and browser evidence demonstrate these differences within the disclosed scope."
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-screen-reader-brief",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading. versus Provide author approved reading without relying on glyph guessing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading. versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-full-name-rhythm",
          "score": 0.11482758620689654,
          "sharedProfile": true,
          "difference": "Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading. versus Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "An annotation must stay attached to the text the author actually meant, even when a narrower label would be convenient.",
        "outline": [
          "A name and its annotation are two linked records",
          "An invented performance credit with one whole-name reading",
          "Write explicit boundaries before measuring the frame",
          "Mono and group associations without automatic reading allocation",
          "What a browser proof measures and what it cannot establish",
          "Hand off markup, fallback text and unresolved decisions"
        ],
        "story": "At a small fictional lantern performance, a performer chooses a stage name whose written image differs from its explicitly invented whole-name reading. The program designer proposes splitting the annotation to make a narrow vertical credit fit. A costume maker notices that the split would imply a correspondence the performer never chose. They compare a whole-name ruby credit and an intentionally redesigned two-segment alternative, then change the frame rather than letting the layout silently redefine the stage identity. This is a fictional production scene, not a Japanese etymology or customer case.",
        "storyAnalysis": "Changing the frame preserves the chosen association; changing the association can change how the audience learns and recognizes the stage identity. A fit result cannot decide that creative tradeoff. Explain the counterfactual without attributing a fabricated reading to real cultural tradition.",
        "evidence": "Original complete EN/JA lantern-program guides, explicit source contracts, RUBY tests and observed browser dimensions/copy/download workflows; attributed W3C terminology remains a reference only.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/rubyLayout.md",
        "localizedBodies": {
          "en": "content/en/rubyLayout.md",
          "ja": "content/ja/rubyLayout.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Changing group boundaries changes the association map and generated markup, while citation text and person ID remain fixed.",
        "A nonmatching concatenation is rejected with an explicit reason; no normalization or omitted segment repairs it.",
        "A combining sequence counts as one grapheme for mono validation; multi-grapheme mono is rejected.",
        "Null reading stays unresolved, not an empty rt or invented pronunciation.",
        "Markup-like name strings remain literal text in preview and export; fallback output preserves all supplied text.",
        "Changing writing mode or frame dimensions changes measured layout checks; source-only results never claim browser fit.",
        "Missing font coverage remains unknown unless actually supported by evidence; successful geometry is not coverage certification.",
        "Copy, actual export, project restore, keyboard operation and EN/JA mobile proofs are observed before this candidate is counted."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:259",
      "profileSource": "data/profiles.json#japanese-writing",
      "specBatch": "batch-07",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Exact text/grapheme contracts, safe markup, live layout measurements and bilingual production guidance; no measured effort estimate."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-japanese-name-vertical-setting",
          "input": "Exact proof/person IDs, literal base and ordered plain/mono/group annotations, horizontal/vertical mode, physical frame dimensions, font stack and size/spacing settings.",
          "rule": "Preserve exact base and declared annotation scope; do not infer a reading split, silently shrink, merge identities or certify unknown font coverage. Measure actual browser base/annotation rectangles rather than estimated advances.",
          "output": "Production annotation map, current-browser bounds/overflow or explicit unknown state, complete safe HTML only when annotations are supplied, and private source/measurement handoffs.",
          "acceptance": "Changing writing mode changes actual layout axes; a 70px vertical inline extent exposes overflow while a larger frame repairs it. A 700px mobile frame preserves its size, scrolls locally and opens at the rightmost starting column.",
          "evidence": [
            "RUBY-09",
            "RUBY-10",
            "RUBY-11",
            "RUBY-14",
            "reports/ruby-layout-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-japanese-pen-name-ruby-credit",
          "input": "Exact proof/person IDs, literal base and ordered plain/mono/group annotations, horizontal/vertical mode, physical frame dimensions, font stack and size/spacing settings.",
          "rule": "Preserve exact base and declared annotation scope; do not infer a reading split, silently shrink, merge identities or certify unknown font coverage. Measure actual browser base/annotation rectangles rather than estimated advances.",
          "output": "Production annotation map, current-browser bounds/overflow or explicit unknown state, complete safe HTML only when annotations are supplied, and private source/measurement handoffs.",
          "acceptance": "A fictional byline containing a literal space and whole authored annotation renders in the same measured vertical frame without a separate name-generation engine. Incomplete annotations withhold complete HTML; source and person IDs stay intact.",
          "evidence": [
            "RUBY-09",
            "RUBY-10",
            "RUBY-11",
            "RUBY-14",
            "reports/ruby-layout-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "rubyLayout",
        "engineFiles": [
          "web/ruby-associations.mjs",
          "web/ruby-layout.mjs",
          "web/ruby-tool.mjs",
          "web/ruby-ui.mjs",
          "web/ruby-view.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/ruby-associations.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "records",
          "label": [
            "Name and annotation contracts · JSON",
            "名前と注音の対応・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"program\",\n    \"person\": \"performer\",\n    \"base\": \"羽灯\",\n    \"segments\": [\n      {\n        \"base\": \"羽灯\",\n        \"reading\": \"ほの\",\n        \"kind\": \"group\"\n      }\n    ]\n  },\n  {\n    \"id\": \"split-proposal\",\n    \"person\": \"performer\",\n    \"base\": \"羽灯\",\n    \"segments\": [\n      {\n        \"base\": \"羽\",\n        \"reading\": \"ほ\",\n        \"kind\": \"mono\"\n      },\n      {\n        \"base\": \"灯\",\n        \"reading\": \"の\",\n        \"kind\": \"mono\"\n      }\n    ]\n  },\n  {\n    \"id\": \"unresolved-credit\",\n    \"person\": \"guest\",\n    \"base\": \"星衣\",\n    \"segments\": [\n      {\n        \"base\": \"星衣\",\n        \"reading\": null,\n        \"kind\": \"group\"\n      }\n    ]\n  }\n]",
          "help": [
            "id/person/base/segments. These are invented stage-name annotations, not attested readings. Segments must literally reconstruct base. plain requires reading:null; mono has one grapheme; group binds the supplied segment. null on an annotated segment stays unresolved.",
            "id/person/base/segments。例の芸名と読みは創作で、確認された読みではありません。区分の結合はbaseに完全一致。plainはreading:null、monoは一書記素、groupは指定区分。注音のnullは未解決です。"
          ],
          "maxLength": 150000
        },
        {
          "key": "writingMode",
          "label": [
            "Proof writing mode",
            "プルーフの組方向"
          ],
          "type": "select",
          "default": "horizontal-tb",
          "help": null,
          "options": [
            [
              "horizontal-tb",
              [
                "Horizontal",
                "横組み"
              ]
            ],
            [
              "vertical-rl",
              [
                "Vertical, right to left columns",
                "縦組み・列は右から左"
              ]
            ]
          ]
        },
        {
          "key": "baseSize",
          "label": [
            "Base font size · CSS px",
            "親文字の大きさ・CSS px"
          ],
          "type": "number",
          "default": 32,
          "help": [
            "12–80. Screen dimensions are not a print-process certification.",
            "12〜80。画面の寸法は印刷工程の認証ではありません。"
          ]
        },
        {
          "key": "rubyRatio",
          "label": [
            "Annotation/base size ratio",
            "ルビと親文字の大きさの比"
          ],
          "type": "number",
          "default": 0.5,
          "help": [
            "0.25–1. Decimal values are allowed. This is your layout choice, not a legibility score.",
            "0.25〜1、小数可。作者の組版選択で、読みやすさの点数ではありません。"
          ]
        },
        {
          "key": "frameWidth",
          "label": [
            "Frame width · CSS px",
            "枠の幅・CSS px"
          ],
          "type": "number",
          "default": 140,
          "help": [
            "40–1000 including a 1px border and 12px inner padding. The preview scrolls locally when wider than your screen.",
            "1pxの枠線と12pxの内余白を含む40〜1000。画面より広い枠は局所的にスクロールします。"
          ]
        },
        {
          "key": "frameHeight",
          "label": [
            "Frame height · CSS px",
            "枠の高さ・CSS px"
          ],
          "type": "number",
          "default": 110,
          "help": [
            "40–1000. Both physical dimensions are checked in either writing mode.",
            "40〜1000。どちらの組方向も実際の幅と高さを確認します。"
          ]
        },
        {
          "key": "fontFamily",
          "label": [
            "Local font stack",
            "端末のフォント候補"
          ],
          "type": "select",
          "default": "mincho",
          "help": null,
          "options": [
            [
              "mincho",
              [
                "Mincho / serif fallback",
                "明朝系／serifへ代替"
              ]
            ],
            [
              "gothic",
              [
                "Gothic / sans-serif fallback",
                "ゴシック系／sans-serifへ代替"
              ]
            ],
            [
              "mono",
              [
                "Monospace fallback",
                "等幅系"
              ]
            ]
          ]
        },
        {
          "key": "lineHeight",
          "label": [
            "Base line-height ratio",
            "親文字の行間比率"
          ],
          "type": "number",
          "default": 1.8,
          "help": [
            "1–3, decimals allowed. A wide annotation can affect line geometry; inspect the actual result.",
            "1〜3、小数可。長いルビは組版の寸法に影響し、実際の結果を確認します。"
          ]
        }
      ]
    },
    {
      "id": "nw-japanese-character-name-kanji-evidence",
      "slug": "japanese-character-name-kanji-evidence",
      "name": "Japanese character name kanji evidence",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-character-name-kanji-evidence/",
        "ja": "/ja/tools/japanese-character-name-kanji-evidence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Track dictionary evidence separately from creative symbolism",
      "task": "Track dictionary evidence separately from creative symbolism",
      "searchIntent": {
        "primary": "Complete the task: Track dictionary evidence separately from creative symbolism",
        "queryHypothesis": "japanese character name kanji evidence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track dictionary evidence separately from creative symbolism?",
        "When should japanese character name kanji evidence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track dictionary evidence separately from creative symbolism",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track dictionary evidence separately from creative symbolism. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Track dictionary evidence separately from creative symbolism versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-fictional-legal-name-note",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Track dictionary evidence separately from creative symbolism versus Separate creative choices from real name registration advice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-kanji-resemblance",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Track dictionary evidence separately from creative symbolism versus Review character shape overlap in a selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track dictionary evidence separately from creative symbolism",
        "outline": [
          "Explain the specific decision: Track dictionary evidence separately from creative symbolism",
          "Define the applicable contract and limits for Japanese character name kanji evidence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track dictionary evidence separately from creative symbolism; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track dictionary evidence separately from creative symbolism",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:260",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-surname-given-name-boundary",
      "slug": "japanese-surname-given-name-boundary",
      "name": "Japanese surname given name boundary",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-surname-given-name-boundary/",
        "ja": "/ja/tools/japanese-surname-given-name-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Prevent full name segmentation errors in a cast sheet",
      "task": "Prevent full name segmentation errors in a cast sheet",
      "searchIntent": {
        "primary": "Complete the task: Prevent full name segmentation errors in a cast sheet",
        "queryHypothesis": "japanese surname given name boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent full name segmentation errors in a cast sheet?",
        "When should japanese surname given name boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent full name segmentation errors in a cast sheet",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent full name segmentation errors in a cast sheet. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-given-name-surname-fit",
          "score": 0.19,
          "sharedProfile": false,
          "difference": "Prevent full name segmentation errors in a cast sheet versus Repair an existing full name without replacing its fixed component; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Prevent full name segmentation errors in a cast sheet versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Prevent full name segmentation errors in a cast sheet versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent full name segmentation errors in a cast sheet",
        "outline": [
          "Explain the specific decision: Prevent full name segmentation errors in a cast sheet",
          "Define the applicable contract and limits for Japanese surname given name boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent full name segmentation errors in a cast sheet; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent full name segmentation errors in a cast sheet",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:262",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-order-policy",
      "slug": "japanese-name-order-policy",
      "name": "Japanese name order policy",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-order-policy/",
        "ja": "/ja/tools/japanese-name-order-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Keep display order consistent across narration and credits",
      "task": "Keep display order consistent across narration and credits",
      "searchIntent": {
        "primary": "Complete the task: Keep display order consistent across narration and credits",
        "queryHypothesis": "japanese name order policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep display order consistent across narration and credits?",
        "When should japanese name order policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep display order consistent across narration and credits",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep display order consistent across narration and credits. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-order-style-sheet",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Keep display order consistent across narration and credits versus Record context dependent display order rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-long-vowel-identity",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Keep display order consistent across narration and credits versus Track long vowels across kana, Latin display and search aliases; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-dossier-name-system",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep display order consistent across narration and credits versus Reconcile names across documents, dialogue and narration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep display order consistent across narration and credits",
        "outline": [
          "Explain the specific decision: Keep display order consistent across narration and credits",
          "Define the applicable contract and limits for Japanese name order policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep display order consistent across narration and credits; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep display order consistent across narration and credits",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:263",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-kana-only-character-identity",
      "slug": "japanese-kana-only-character-identity",
      "name": "Japanese kana only character identity",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-kana-only-character-identity/",
        "ja": "/ja/tools/japanese-kana-only-character-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Evaluate a supplied kana name in the story's reference system",
      "task": "Evaluate a supplied kana name in the story's reference system",
      "searchIntent": {
        "primary": "Complete the task: Evaluate a supplied kana name in the story's reference system",
        "queryHypothesis": "japanese kana only character identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to evaluate a supplied kana name in the story's reference system?",
        "When should japanese kana only character identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Evaluate a supplied kana name in the story's reference system",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Evaluate a supplied kana name in the story's reference system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-long-vowel-identity",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Evaluate a supplied kana name in the story's reference system versus Track long vowels across kana, Latin display and search aliases; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Evaluate a supplied kana name in the story's reference system versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hive-member-identity",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Evaluate a supplied kana name in the story's reference system versus Distinguish collective reference from individual agents; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Evaluate a supplied kana name in the story's reference system",
        "outline": [
          "Explain the specific decision: Evaluate a supplied kana name in the story's reference system",
          "Define the applicable contract and limits for Japanese kana only character identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Evaluate a supplied kana name in the story's reference system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Evaluate a supplied kana name in the story's reference system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:264",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-katakana-identity-choice",
      "slug": "japanese-katakana-identity-choice",
      "name": "Japanese katakana identity choice",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-katakana-identity-choice/",
        "ja": "/ja/tools/japanese-katakana-identity-choice/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Explain author selected script effects without claiming universal meaning",
      "task": "Explain author selected script effects without claiming universal meaning",
      "searchIntent": {
        "primary": "Complete the task: Explain author selected script effects without claiming universal meaning",
        "queryHypothesis": "japanese katakana identity choice",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain author selected script effects without claiming universal meaning?",
        "When should japanese katakana identity choice be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain author selected script effects without claiming universal meaning",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain author selected script effects without claiming universal meaning. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.16309523809523807,
          "sharedProfile": true,
          "difference": "Explain author selected script effects without claiming universal meaning versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-surname-locality-check",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Explain author selected script effects without claiming universal meaning versus Record geographic evidence without claiming universal distribution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Explain author selected script effects without claiming universal meaning versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain author selected script effects without claiming universal meaning",
        "outline": [
          "Explain the specific decision: Explain author selected script effects without claiming universal meaning",
          "Define the applicable contract and limits for Japanese katakana identity choice",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain author selected script effects without claiming universal meaning; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain author selected script effects without claiming universal meaning",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:265",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-mixed-script-name-design",
      "slug": "japanese-mixed-script-name-design",
      "name": "Japanese mixed script name design",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-mixed-script-name-design/",
        "ja": "/ja/tools/japanese-mixed-script-name-design/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Check intentional script mixing against a declared world rule",
      "task": "Check intentional script mixing against a declared world rule",
      "searchIntent": {
        "primary": "Complete the task: Check intentional script mixing against a declared world rule",
        "queryHypothesis": "japanese mixed script name design",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check intentional script mixing against a declared world rule?",
        "When should japanese mixed script name design be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check intentional script mixing against a declared world rule",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check intentional script mixing against a declared world rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Check intentional script mixing against a declared world rule versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-generated-biography-name-fit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Check intentional script mixing against a declared world rule versus Check a generated name against explicit biography fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Check intentional script mixing against a declared world rule versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check intentional script mixing against a declared world rule",
        "outline": [
          "Explain the specific decision: Check intentional script mixing against a declared world rule",
          "Define the applicable contract and limits for Japanese mixed script name design",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check intentional script mixing against a declared world rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check intentional script mixing against a declared world rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:266",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-difficult-name-introduction",
      "slug": "japanese-difficult-name-introduction",
      "name": "Japanese difficult name introduction",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-difficult-name-introduction/",
        "ja": "/ja/tools/japanese-difficult-name-introduction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Compare staged reading support against renaming",
      "task": "Compare staged reading support against renaming",
      "searchIntent": {
        "primary": "Complete the task: Compare staged reading support against renaming",
        "queryHypothesis": "japanese difficult name introduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare staged reading support against renaming?",
        "When should japanese difficult name introduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare staged reading support against renaming",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare staged reading support against renaming. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-furigana-introduction-plan",
          "score": 0.2844444444444444,
          "sharedProfile": true,
          "difference": "Compare staged reading support against renaming versus Schedule reading support at first and later appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-dialogue-balloon",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Compare staged reading support against renaming versus Preview line breaks and reading support in constrained balloons; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unnamed-narrator-decision",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare staged reading support against renaming versus Compare pronoun only narration against staged name disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare staged reading support against renaming",
        "outline": [
          "Explain the specific decision: Compare staged reading support against renaming",
          "Define the applicable contract and limits for Japanese difficult name introduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare staged reading support against renaming; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare staged reading support against renaming",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:267",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-cast-reading-collision",
      "slug": "japanese-cast-reading-collision",
      "name": "Japanese cast reading collision",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-cast-reading-collision/",
        "ja": "/ja/tools/japanese-cast-reading-collision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Detect different written names with the same confirmed reading",
      "task": "Detect different written names with the same confirmed reading",
      "searchIntent": {
        "primary": "Complete the task: Detect different written names with the same confirmed reading",
        "queryHypothesis": "japanese cast reading collision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect different written names with the same confirmed reading?",
        "When should japanese cast reading collision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect different written names with the same confirmed reading",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect different written names with the same confirmed reading. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Detect different written names with the same confirmed reading versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Detect different written names with the same confirmed reading versus Store approved kana and romanized credits alongside the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Detect different written names with the same confirmed reading versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect different written names with the same confirmed reading",
        "outline": [
          "Explain the specific decision: Detect different written names with the same confirmed reading",
          "Define the applicable contract and limits for Japanese cast reading collision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect different written names with the same confirmed reading; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect different written names with the same confirmed reading",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:268",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-cast-kanji-resemblance",
      "slug": "japanese-cast-kanji-resemblance",
      "name": "Japanese cast kanji resemblance",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-cast-kanji-resemblance/",
        "ja": "/ja/tools/japanese-cast-kanji-resemblance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Review character shape overlap in a selected font",
      "task": "Review character shape overlap in a selected font",
      "searchIntent": {
        "primary": "Complete the task: Review character shape overlap in a selected font",
        "queryHypothesis": "japanese cast kanji resemblance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to review character shape overlap in a selected font?",
        "When should japanese cast kanji resemblance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Review character shape overlap in a selected font",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Review character shape overlap in a selected font. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-font-coverage-test",
          "score": 0.2125,
          "sharedProfile": true,
          "difference": "Review character shape overlap in a selected font versus Detect missing glyphs in the actual selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Review character shape overlap in a selected font versus Track dictionary evidence separately from creative symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-name-relationship-heatmap",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Review character shape overlap in a selected font versus Combine scene proximity with similarity for targeted review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Review character shape overlap in a selected font",
        "outline": [
          "Explain the specific decision: Review character shape overlap in a selected font",
          "Define the applicable contract and limits for Japanese cast kanji resemblance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Review character shape overlap in a selected font; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Review character shape overlap in a selected font",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:269",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-nickname-derivation",
      "slug": "japanese-nickname-derivation",
      "name": "Japanese nickname derivation",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-nickname-derivation/",
        "ja": "/ja/tools/japanese-nickname-derivation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Generate only transformations allowed by an author approved rule set",
      "task": "Generate only transformations allowed by an author approved rule set",
      "searchIntent": {
        "primary": "Complete the task: Generate only transformations allowed by an author approved rule set",
        "queryHypothesis": "japanese nickname derivation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate only transformations allowed by an author approved rule set?",
        "When should japanese nickname derivation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate only transformations allowed by an author approved rule set",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate only transformations allowed by an author approved rule set. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Generate only transformations allowed by an author approved rule set versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-honorific-transition-map",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Generate only transformations allowed by an author approved rule set versus Model author specified changes with contextual review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-screen-reader-brief",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Generate only transformations allowed by an author approved rule set versus Provide author approved reading without relying on glyph guessing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate only transformations allowed by an author approved rule set",
        "outline": [
          "Explain the specific decision: Generate only transformations allowed by an author approved rule set",
          "Define the applicable contract and limits for Japanese nickname derivation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate only transformations allowed by an author approved rule set; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate only transformations allowed by an author approved rule set",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:270",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-surname-address-map",
      "slug": "japanese-surname-address-map",
      "name": "Japanese surname address map",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-surname-address-map/",
        "ja": "/ja/tools/japanese-surname-address-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Track surname usage by relationship and speaker",
      "task": "Track surname usage by relationship and speaker",
      "searchIntent": {
        "primary": "Complete the task: Track surname usage by relationship and speaker",
        "queryHypothesis": "japanese surname address map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track surname usage by relationship and speaker?",
        "When should japanese surname address map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track surname usage by relationship and speaker",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track surname usage by relationship and speaker. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.38333333333333336,
          "sharedProfile": false,
          "difference": "Track surname usage by relationship and speaker versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-workplace-ensemble-name-map",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Track surname usage by relationship and speaker versus Model surname, title and first name use by colleague relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.19444444444444442,
          "sharedProfile": false,
          "difference": "Track surname usage by relationship and speaker versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track surname usage by relationship and speaker",
        "outline": [
          "Explain the specific decision: Track surname usage by relationship and speaker",
          "Define the applicable contract and limits for Japanese surname address map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track surname usage by relationship and speaker; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track surname usage by relationship and speaker",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:271",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-honorific-transition-map",
      "slug": "japanese-honorific-transition-map",
      "name": "Japanese honorific transition map",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-honorific-transition-map/",
        "ja": "/ja/tools/japanese-honorific-transition-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Model author specified changes with contextual review",
      "task": "Model author specified changes with contextual review",
      "searchIntent": {
        "primary": "Complete the task: Model author specified changes with contextual review",
        "queryHypothesis": "japanese honorific transition map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model author specified changes with contextual review?",
        "When should japanese honorific transition map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model author specified changes with contextual review",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model author specified changes with contextual review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-bookstore-ambiguity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model author specified changes with contextual review versus Distinguish an author from similarly named authors in a manual review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-romanization-source-map",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Model author specified changes with contextual review versus Store the chosen system and exception evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Model author specified changes with contextual review versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model author specified changes with contextual review",
        "outline": [
          "Explain the specific decision: Model author specified changes with contextual review",
          "Define the applicable contract and limits for Japanese honorific transition map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model author specified changes with contextual review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model author specified changes with contextual review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:272",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-dialogue-balloon",
      "slug": "japanese-name-dialogue-balloon",
      "name": "Japanese name dialogue balloon",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-dialogue-balloon/",
        "ja": "/ja/tools/japanese-name-dialogue-balloon/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Preview line breaks and reading support in constrained balloons",
      "task": "Preview line breaks and reading support in constrained balloons",
      "searchIntent": {
        "primary": "Complete the task: Preview line breaks and reading support in constrained balloons",
        "queryHypothesis": "japanese name dialogue balloon",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preview line breaks and reading support in constrained balloons?",
        "When should japanese name dialogue balloon be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preview line breaks and reading support in constrained balloons",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preview line breaks and reading support in constrained balloons. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Preview line breaks and reading support in constrained balloons versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-furigana-introduction-plan",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Preview line breaks and reading support in constrained balloons versus Schedule reading support at first and later appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-handwritten-prop",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Preview line breaks and reading support in constrained balloons versus Keep prop spelling, reading and plot knowledge synchronized; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preview line breaks and reading support in constrained balloons",
        "outline": [
          "Explain the specific decision: Preview line breaks and reading support in constrained balloons",
          "Define the applicable contract and limits for Japanese name dialogue balloon",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preview line breaks and reading support in constrained balloons; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preview line breaks and reading support in constrained balloons",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:275",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-handwritten-prop",
      "slug": "japanese-name-handwritten-prop",
      "name": "Japanese name handwritten prop",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-handwritten-prop/",
        "ja": "/ja/tools/japanese-name-handwritten-prop/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Keep prop spelling, reading and plot knowledge synchronized",
      "task": "Keep prop spelling, reading and plot knowledge synchronized",
      "searchIntent": {
        "primary": "Complete the task: Keep prop spelling, reading and plot knowledge synchronized",
        "queryHypothesis": "japanese name handwritten prop",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep prop spelling, reading and plot knowledge synchronized?",
        "When should japanese name handwritten prop be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep prop spelling, reading and plot knowledge synchronized",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep prop spelling, reading and plot knowledge synchronized. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-handwritten-name-ambiguity",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Keep prop spelling, reading and plot knowledge synchronized versus Define visible alternatives with an actual prop example; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Keep prop spelling, reading and plot knowledge synchronized versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-sibling-name-distinction",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Keep prop spelling, reading and plot knowledge synchronized versus Compare reading and graphic separation within one household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep prop spelling, reading and plot knowledge synchronized",
        "outline": [
          "Explain the specific decision: Keep prop spelling, reading and plot knowledge synchronized",
          "Define the applicable contract and limits for Japanese name handwritten prop",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep prop spelling, reading and plot knowledge synchronized; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep prop spelling, reading and plot knowledge synchronized",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:276",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-mistaken-reading-plot",
      "slug": "japanese-name-mistaken-reading-plot",
      "name": "Japanese name mistaken reading plot",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-mistaken-reading-plot/",
        "ja": "/ja/tools/japanese-name-mistaken-reading-plot/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Design a fair clue using verified alternative readings",
      "task": "Design a fair clue using verified alternative readings",
      "searchIntent": {
        "primary": "Complete the task: Design a fair clue using verified alternative readings",
        "queryHypothesis": "japanese name mistaken reading plot",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a fair clue using verified alternative readings?",
        "When should japanese name mistaken reading plot be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a fair clue using verified alternative readings",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a fair clue using verified alternative readings. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.17083333333333334,
          "sharedProfile": true,
          "difference": "Design a fair clue using verified alternative readings versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-mistaken-identity-encounter",
          "score": 0.16818181818181818,
          "sharedProfile": false,
          "difference": "Design a fair clue using verified alternative readings versus Design fair recoverable name confusion for a live session; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-same-writing-different-reading",
          "score": 0.16499999999999998,
          "sharedProfile": true,
          "difference": "Design a fair clue using verified alternative readings versus Require explicit readings and ambiguity disclosures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a fair clue using verified alternative readings",
        "outline": [
          "Explain the specific decision: Design a fair clue using verified alternative readings",
          "Define the applicable contract and limits for Japanese name mistaken reading plot",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a fair clue using verified alternative readings; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a fair clue using verified alternative readings",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:277",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-miswritten-clue",
      "slug": "japanese-name-miswritten-clue",
      "name": "Japanese name miswritten clue",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-miswritten-clue/",
        "ja": "/ja/tools/japanese-name-miswritten-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Separate plausible graphic confusion from arbitrary substitutions",
      "task": "Separate plausible graphic confusion from arbitrary substitutions",
      "searchIntent": {
        "primary": "Complete the task: Separate plausible graphic confusion from arbitrary substitutions",
        "queryHypothesis": "japanese name miswritten clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate plausible graphic confusion from arbitrary substitutions?",
        "When should japanese name miswritten clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate plausible graphic confusion from arbitrary substitutions",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate plausible graphic confusion from arbitrary substitutions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Separate plausible graphic confusion from arbitrary substitutions versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-sibling-name-distinction",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Separate plausible graphic confusion from arbitrary substitutions versus Compare reading and graphic separation within one household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-same-reading-different-writing",
          "score": 0.13125,
          "sharedProfile": true,
          "difference": "Separate plausible graphic confusion from arbitrary substitutions versus Distinguish character identity from graphic alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate plausible graphic confusion from arbitrary substitutions",
        "outline": [
          "Explain the specific decision: Separate plausible graphic confusion from arbitrary substitutions",
          "Define the applicable contract and limits for Japanese name miswritten clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate plausible graphic confusion from arbitrary substitutions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate plausible graphic confusion from arbitrary substitutions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:278",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-family-repeated-kanji",
      "slug": "japanese-family-repeated-kanji",
      "name": "Japanese family repeated kanji",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-family-repeated-kanji/",
        "ja": "/ja/tools/japanese-family-repeated-kanji/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Track shared characters without assuming universal family practice",
      "task": "Track shared characters without assuming universal family practice",
      "searchIntent": {
        "primary": "Complete the task: Track shared characters without assuming universal family practice",
        "queryHypothesis": "japanese family repeated kanji",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track shared characters without assuming universal family practice?",
        "When should japanese family repeated kanji be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track shared characters without assuming universal family practice",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track shared characters without assuming universal family practice. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-multigenerational-family-names",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Track shared characters without assuming universal family practice versus Allocate names over a dated family tree without accidental recycling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Track shared characters without assuming universal family practice versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nomadic-fictional-naming",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Track shared characters without assuming universal family practice versus Model travel group membership without assuming one universal nomadic custom; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track shared characters without assuming universal family practice",
        "outline": [
          "Explain the specific decision: Track shared characters without assuming universal family practice",
          "Define the applicable contract and limits for Japanese family repeated kanji",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track shared characters without assuming universal family practice; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track shared characters without assuming universal family practice",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:279",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-sibling-name-distinction",
      "slug": "japanese-sibling-name-distinction",
      "name": "Japanese sibling name distinction",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-sibling-name-distinction/",
        "ja": "/ja/tools/japanese-sibling-name-distinction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Compare reading and graphic separation within one household",
      "task": "Compare reading and graphic separation within one household",
      "searchIntent": {
        "primary": "Complete the task: Compare reading and graphic separation within one household",
        "queryHypothesis": "japanese sibling name distinction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reading and graphic separation within one household?",
        "When should japanese sibling name distinction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reading and graphic separation within one household",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reading and graphic separation within one household. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare reading and graphic separation within one household versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-full-name-rhythm",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare reading and graphic separation within one household versus Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-miswritten-clue",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare reading and graphic separation within one household versus Separate plausible graphic confusion from arbitrary substitutions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reading and graphic separation within one household",
        "outline": [
          "Explain the specific decision: Compare reading and graphic separation within one household",
          "Define the applicable contract and limits for Japanese sibling name distinction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reading and graphic separation within one household; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reading and graphic separation within one household",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:280",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-historical-name-research-brief",
      "slug": "japanese-historical-name-research-brief",
      "name": "Japanese historical name research brief",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-historical-name-research-brief/",
        "ja": "/ja/tools/japanese-historical-name-research-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Specify period, locality and sources before candidate generation",
      "task": "Specify period, locality and sources before candidate generation",
      "searchIntent": {
        "primary": "Complete the task: Specify period, locality and sources before candidate generation",
        "queryHypothesis": "japanese historical name research brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to specify period, locality and sources before candidate generation?",
        "When should japanese historical name research brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Specify period, locality and sources before candidate generation",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Specify period, locality and sources before candidate generation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.3375,
          "sharedProfile": false,
          "difference": "Specify period, locality and sources before candidate generation versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.19416666666666665,
          "sharedProfile": false,
          "difference": "Specify period, locality and sources before candidate generation versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Specify period, locality and sources before candidate generation versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Specify period, locality and sources before candidate generation",
        "outline": [
          "Explain the specific decision: Specify period, locality and sources before candidate generation",
          "Define the applicable contract and limits for Japanese historical name research brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Specify period, locality and sources before candidate generation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Specify period, locality and sources before candidate generation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:281",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-era-mismatch-review",
      "slug": "japanese-era-mismatch-review",
      "name": "Japanese era mismatch review",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-era-mismatch-review/",
        "ja": "/ja/tools/japanese-era-mismatch-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Flag unsupported period claims for a specialist review",
      "task": "Flag unsupported period claims for a specialist review",
      "searchIntent": {
        "primary": "Complete the task: Flag unsupported period claims for a specialist review",
        "queryHypothesis": "japanese era mismatch review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag unsupported period claims for a specialist review?",
        "When should japanese era mismatch review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag unsupported period claims for a specialist review",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag unsupported period claims for a specialist review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-naming-sensitivity-review",
          "score": 0.2581818181818182,
          "sharedProfile": true,
          "difference": "Flag unsupported period claims for a specialist review versus Require context and native language review for cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Flag unsupported period claims for a specialist review versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-naming-anachronism-review",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Flag unsupported period claims for a specialist review versus Flag unsupported forms rather than manufacture certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag unsupported period claims for a specialist review",
        "outline": [
          "Explain the specific decision: Flag unsupported period claims for a specialist review",
          "Define the applicable contract and limits for Japanese era mismatch review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag unsupported period claims for a specialist review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag unsupported period claims for a specialist review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:282",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-fictional-legal-name-note",
      "slug": "japanese-fictional-legal-name-note",
      "name": "Japanese fictional legal name note",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-fictional-legal-name-note/",
        "ja": "/ja/tools/japanese-fictional-legal-name-note/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Separate creative choices from real name registration advice",
      "task": "Separate creative choices from real name registration advice",
      "searchIntent": {
        "primary": "Complete the task: Separate creative choices from real name registration advice",
        "queryHypothesis": "japanese fictional legal name note",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate creative choices from real name registration advice?",
        "When should japanese fictional legal name note be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate creative choices from real name registration advice",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate creative choices from real name registration advice. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Separate creative choices from real name registration advice versus Track dictionary evidence separately from creative symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Separate creative choices from real name registration advice versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-real-person-name-boundary",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate creative choices from real name registration advice versus Separate a fictional character from a real person's biography; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate creative choices from real name registration advice",
        "outline": [
          "Explain the specific decision: Separate creative choices from real name registration advice",
          "Define the applicable contract and limits for Japanese fictional legal name note",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate creative choices from real name registration advice; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate creative choices from real name registration advice",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:283",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-romanization-source-map",
      "slug": "japanese-name-romanization-source-map",
      "name": "Japanese name romanization source map",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-romanization-source-map/",
        "ja": "/ja/tools/japanese-name-romanization-source-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Store the chosen system and exception evidence",
      "task": "Store the chosen system and exception evidence",
      "searchIntent": {
        "primary": "Complete the task: Store the chosen system and exception evidence",
        "queryHypothesis": "japanese name romanization source map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to store the chosen system and exception evidence?",
        "When should japanese name romanization source map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Store the chosen system and exception evidence",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Store the chosen system and exception evidence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-consent-map",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Store the chosen system and exception evidence versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Store the chosen system and exception evidence versus Track dictionary evidence separately from creative symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Store the chosen system and exception evidence versus Store approved kana and romanized credits alongside the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Store the chosen system and exception evidence",
        "outline": [
          "Explain the specific decision: Store the chosen system and exception evidence",
          "Define the applicable contract and limits for Japanese name romanization source map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Store the chosen system and exception evidence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Store the chosen system and exception evidence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:284",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-long-vowel-identity",
      "slug": "japanese-long-vowel-identity",
      "name": "Japanese long vowel identity",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-long-vowel-identity/",
        "ja": "/ja/tools/japanese-long-vowel-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Track long vowels across kana, Latin display and search aliases",
      "task": "Track long vowels across kana, Latin display and search aliases",
      "searchIntent": {
        "primary": "Complete the task: Track long vowels across kana, Latin display and search aliases",
        "queryHypothesis": "japanese long vowel identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track long vowels across kana, Latin display and search aliases?",
        "When should japanese long vowel identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track long vowels across kana, Latin display and search aliases",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track long vowels across kana, Latin display and search aliases. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-kana-only-character-identity",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Track long vowels across kana, Latin display and search aliases versus Evaluate a supplied kana name in the story's reference system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-order-policy",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Track long vowels across kana, Latin display and search aliases versus Keep display order consistent across narration and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Track long vowels across kana, Latin display and search aliases versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track long vowels across kana, Latin display and search aliases",
        "outline": [
          "Explain the specific decision: Track long vowels across kana, Latin display and search aliases",
          "Define the applicable contract and limits for Japanese long vowel identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track long vowels across kana, Latin display and search aliases; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track long vowels across kana, Latin display and search aliases",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:285",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-syllable-misconception-audit",
      "slug": "japanese-name-syllable-misconception-audit",
      "name": "Japanese name syllable misconception audit",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-syllable-misconception-audit/",
        "ja": "/ja/tools/japanese-name-syllable-misconception-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Distinguish mora based analysis from English syllable estimates",
      "task": "Distinguish mora based analysis from English syllable estimates",
      "searchIntent": {
        "primary": "Complete the task: Distinguish mora based analysis from English syllable estimates",
        "queryHypothesis": "japanese name syllable misconception audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish mora based analysis from English syllable estimates?",
        "When should japanese name syllable misconception audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish mora based analysis from English syllable estimates",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish mora based analysis from English syllable estimates. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-servant-master-voice-audit",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Distinguish mora based analysis from English syllable estimates versus Distinguish hierarchy conventions from narrator assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-same-reading-different-writing",
          "score": 0.10875,
          "sharedProfile": true,
          "difference": "Distinguish mora based analysis from English syllable estimates versus Distinguish character identity from graphic alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Distinguish mora based analysis from English syllable estimates versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish mora based analysis from English syllable estimates",
        "outline": [
          "Explain the specific decision: Distinguish mora based analysis from English syllable estimates",
          "Define the applicable contract and limits for Japanese name syllable misconception audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish mora based analysis from English syllable estimates; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish mora based analysis from English syllable estimates",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:286",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-voicing-variation-ledger",
      "slug": "japanese-name-voicing-variation-ledger",
      "name": "Japanese name voicing variation ledger",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-voicing-variation-ledger/",
        "ja": "/ja/tools/japanese-name-voicing-variation-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Store documented variants without inventing alternation rules",
      "task": "Store documented variants without inventing alternation rules",
      "searchIntent": {
        "primary": "Complete the task: Store documented variants without inventing alternation rules",
        "queryHypothesis": "japanese name voicing variation ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to store documented variants without inventing alternation rules?",
        "When should japanese name voicing variation ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Store documented variants without inventing alternation rules",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Store documented variants without inventing alternation rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-migration-name-records",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Store documented variants without inventing alternation rules versus Trace documented variants without assuming identity from similarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-full-name-rhythm",
          "score": 0.15583333333333332,
          "sharedProfile": true,
          "difference": "Store documented variants without inventing alternation rules versus Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Store documented variants without inventing alternation rules versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Store documented variants without inventing alternation rules",
        "outline": [
          "Explain the specific decision: Store documented variants without inventing alternation rules",
          "Define the applicable contract and limits for Japanese name voicing variation ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Store documented variants without inventing alternation rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Store documented variants without inventing alternation rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:288",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-glyph-variant-continuity",
      "slug": "japanese-name-glyph-variant-continuity",
      "name": "Japanese name glyph variant continuity",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-glyph-variant-continuity/",
        "ja": "/ja/tools/japanese-name-glyph-variant-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Link selected variants to one character ID",
      "task": "Link selected variants to one character ID",
      "searchIntent": {
        "primary": "Complete the task: Link selected variants to one character ID",
        "queryHypothesis": "japanese name glyph variant continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link selected variants to one character ID?",
        "When should japanese name glyph variant continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "forms",
          "use": "Original glyph sequence, Unicode sequence and author-designated identity ID."
        },
        {
          "key": "assets",
          "use": "Font coverage and occurrences in art or text, with supplied proof rather than guessed visual equivalence."
        },
        {
          "key": "replacements",
          "use": "Explicit proposed fallback, evidence and approval scope per asset."
        }
      ],
      "rules": [
        "Never normalize away the original display form.",
        "A glyph similarity or Unicode relationship does not prove that two people are one identity.",
        "Reject fallback cycles and conflicting same-asset approvals.",
        "Select only an approved fallback for the chosen asset; otherwise report unresolved.",
        "Preserve original glyph, evidence and explicit fallback separately"
      ],
      "requiredData": [
        {
          "description": "User-supplied asset occurrence manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Claim-specific glyph evidence with license notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Never normalize away the original display form.",
        "A glyph similarity or Unicode relationship does not prove that two people are one identity.",
        "Reject fallback cycles and conflicting same-asset approvals.",
        "Select only an approved fallback for the chosen asset; otherwise report unresolved."
      ],
      "outputs": [
        "Original and asset-specific approved forms",
        "Unresolved occurrences",
        "Decision history and font-proof status",
        "Versioned glyph decision"
      ],
      "capabilities": [
        "Trace a fallback across all affected props without overwriting the source form.",
        "Compare an asset before and after a font change while preserving identity."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Resolve a chain of written forms and fallback approvals across art and text assets; this task does not choose a pronunciation or generate another person.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "japanese-character-name-record",
          "difference": "The record stores one identity's written form and reading; this workflow resolves multiple asset-specific glyph representations with evidence and approval histories."
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-sibling-name-distinction",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Link selected variants to one character ID versus Compare reading and graphic separation within one household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-variant-audit",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Link selected variants to one character ID versus Find spelling variants for human identity confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-cast-kanji-resemblance",
          "score": 0.1222222222222222,
          "sharedProfile": true,
          "difference": "Link selected variants to one character ID versus Review character shape overlap in a selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A readable substitute is an editorial decision, not permission to erase the original form.",
        "outline": [
          "Record the original before testing fonts",
          "Separate encoding, visible glyph and identity",
          "A name stamp and a paperback font disagree",
          "Approve replacements at the asset boundary",
          "Send evidence to a Japanese editor"
        ],
        "story": "Fictional example: a comic's historical family stamp uses a form missing from its caption font. The team keeps the stamp artwork, approves a caption fallback and documents why both refer to one authored character.",
        "storyAnalysis": "A global text replacement would destroy the prop clue. Compare retaining the original, substituting everywhere and providing a scoped reading note.",
        "evidence": "Original asset fixtures and approved mappings required; no glyph-specific cultural equivalence asserted without sources.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/glyph.md",
        "localizedBodies": {
          "en": "content/en/glyph.md",
          "ja": "content/ja/glyph.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A missing glyph with no approved fallback stays unresolved.",
        "A fallback cycle is rejected with its path.",
        "The same normalized string does not automatically merge two IDs.",
        "A proof approved for one font does not approve a different font.",
        "Unapproved replacement is held for review"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:290",
      "profileSource": "data/profiles.json#japanese-writing",
      "absorbedModules": [
        {
          "sourceId": "nw-japanese-name-uncommon-character-fallback",
          "input": "glyphEvidence; approvedFallback",
          "rule": "Preserve original glyph, evidence and explicit fallback separately",
          "output": "Versioned glyph decision",
          "acceptance": "Unapproved replacement is held for review",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "redesign": {
        "required": true,
        "sourceId": "nw-japanese-name-uncommon-character-fallback",
        "mainTask": "Uncommon glyph handling and historical variants may overlap. Redesign one evidence-backed glyph continuity workflow before considering independent pages.",
        "status": "contract-refined-awaiting-prototype"
      },
      "specBatch": "batch-01",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "glyph",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/editorial-engines.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/editorial.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "forms",
          "label": [
            "Exact variants and identities",
            "正確な表記と人物"
          ],
          "type": "textarea",
          "default": "v1 | a | 髙瀬\nv2 | a | 高瀬\nv3 | b | 高瀬",
          "help": [
            "Variant ID | person ID | exact written form. The two forms for a are an authored fictional decision, not a claim that glyphs are interchangeable in real names.",
            "表記ID | 人物ID | 正確な表記。aの二表記は架空の編集設定です。実在の名前で字形を交換できると主張しません。"
          ]
        },
        {
          "key": "assets",
          "label": [
            "Asset and proof versions",
            "素材と確認版"
          ],
          "type": "textarea",
          "default": "stamp | ink-art-v1 | ink-art-v2\ncaption | caption-font-v1 | caption-font-v2",
          "help": [
            "Asset ID | current font/art proof version | comparison version, optional. Version labels must identify the actual production context.",
            "素材ID | 現在の書体・絵の確認版 | 比較版・任意。版は実際の制作条件を識別するラベルです。"
          ]
        },
        {
          "key": "occurrences",
          "label": [
            "Original occurrences",
            "元の使用箇所"
          ],
          "type": "textarea",
          "default": "seal-01 | stamp | v1\ncaption-01 | caption | v1\nother-01 | caption | v3",
          "help": [
            "Occurrence ID | asset ID | original variant ID. Separate people remain separate even with the same written form.",
            "使用箇所ID | 素材ID | 元の表記ID。同じ表記でも別人のIDを維持します。"
          ]
        },
        {
          "key": "proofs",
          "label": [
            "Supplied glyph observations",
            "入力する字形の確認"
          ],
          "type": "textarea",
          "default": "stamp | ink-art-v1 | v1 | supported | Reviewed original stamp drawing\nstamp | ink-art-v2 | v1 | supported | Revised stamp drawing reviewed\ncaption | caption-font-v1 | v1 | missing | Caption proof shows missing glyph\ncaption | caption-font-v1 | v2 | supported | Caption fallback proof reviewed\ncaption | caption-font-v1 | v3 | supported | Second person caption reviewed\ncaption | caption-font-v2 | v1 | unknown | New proof not reviewed\ncaption | caption-font-v2 | v3 | unknown | New proof not reviewed",
          "help": [
            "Asset | version | variant ID | supported/missing/unknown | evidence note. Observations are supplied by you; no automatic installed-font test.",
            "素材 | 版 | 表記ID | supported/missing/unknown | 根拠メモ。観察は利用者が入力し、インストール済み書体を自動検査しません。"
          ]
        },
        {
          "key": "approvals",
          "label": [
            "Scoped fallback approvals",
            "範囲を限定した代替の承認"
          ],
          "type": "textarea",
          "default": "caption | caption-font-v1 | v1 | v2 | Author approves caption-only alternate for fictional person a; original seal kept",
          "help": [
            "Asset | version | from variant | to variant | editorial reason. Same-person variants only. Cycles and duplicate approvals are rejected.",
            "素材 | 版 | 元の表記ID | 代替の表記ID | 編集上の理由。同じ人物のみ。循環と重複はエラーです。"
          ]
        }
      ]
    },
    {
      "id": "nw-japanese-name-font-coverage-test",
      "slug": "japanese-name-font-coverage-test",
      "name": "Japanese name font coverage test",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-font-coverage-test/",
        "ja": "/ja/tools/japanese-name-font-coverage-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Detect missing glyphs in the actual selected font",
      "task": "Detect missing glyphs in the actual selected font",
      "searchIntent": {
        "primary": "Complete the task: Detect missing glyphs in the actual selected font",
        "queryHypothesis": "japanese name font coverage test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect missing glyphs in the actual selected font?",
        "When should japanese name font coverage test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect missing glyphs in the actual selected font",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect missing glyphs in the actual selected font. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-cast-kanji-resemblance",
          "score": 0.2125,
          "sharedProfile": true,
          "difference": "Detect missing glyphs in the actual selected font versus Review character shape overlap in a selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-font-glyph-audit",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Detect missing glyphs in the actual selected font versus Verify approved name characters against actual font coverage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Detect missing glyphs in the actual selected font versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect missing glyphs in the actual selected font",
        "outline": [
          "Explain the specific decision: Detect missing glyphs in the actual selected font",
          "Define the applicable contract and limits for Japanese name font coverage test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect missing glyphs in the actual selected font; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect missing glyphs in the actual selected font",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:291",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-name-screen-reader-brief",
      "slug": "japanese-name-screen-reader-brief",
      "name": "Japanese name screen reader brief",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-screen-reader-brief/",
        "ja": "/ja/tools/japanese-name-screen-reader-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Provide author approved reading without relying on glyph guessing",
      "task": "Provide author approved reading without relying on glyph guessing",
      "searchIntent": {
        "primary": "Complete the task: Provide author approved reading without relying on glyph guessing",
        "queryHypothesis": "japanese name screen reader brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide author approved reading without relying on glyph guessing?",
        "When should japanese name screen reader brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide author approved reading without relying on glyph guessing",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide author approved reading without relying on glyph guessing. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Provide author approved reading without relying on glyph guessing versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-screen-reader-character-names",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Provide author approved reading without relying on glyph guessing versus Keep accessible display consistent with visible identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-reading-choice",
          "score": 0.16818181818181818,
          "sharedProfile": true,
          "difference": "Provide author approved reading without relying on glyph guessing versus Compare sourced readings without guessing from individual kanji; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide author approved reading without relying on glyph guessing",
        "outline": [
          "Explain the specific decision: Provide author approved reading without relying on glyph guessing",
          "Define the applicable contract and limits for Japanese name screen reader brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide author approved reading without relying on glyph guessing; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide author approved reading without relying on glyph guessing",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:293",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-localization-name-bible",
      "slug": "japanese-localization-name-bible",
      "name": "Japanese localization name bible",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-localization-name-bible/",
        "ja": "/ja/tools/japanese-localization-name-bible/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Maintain approved forms for editors and translators",
      "task": "Maintain approved forms for editors and translators",
      "searchIntent": {
        "primary": "Complete the task: Maintain approved forms for editors and translators",
        "queryHypothesis": "japanese localization name bible",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain approved forms for editors and translators?",
        "When should japanese localization name bible be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain approved forms for editors and translators",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain approved forms for editors and translators. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-localization-name-map",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Maintain approved forms for editors and translators versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Maintain approved forms for editors and translators versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Maintain approved forms for editors and translators versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain approved forms for editors and translators",
        "outline": [
          "Explain the specific decision: Maintain approved forms for editors and translators",
          "Define the applicable contract and limits for Japanese localization name bible",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain approved forms for editors and translators; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain approved forms for editors and translators",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:294",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-japanese-character-naming-sensitivity-review",
      "slug": "japanese-character-naming-sensitivity-review",
      "name": "Japanese character naming sensitivity review",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-character-naming-sensitivity-review/",
        "ja": "/ja/tools/japanese-character-naming-sensitivity-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Require context and native language review for cultural claims",
      "task": "Require context and native language review for cultural claims",
      "searchIntent": {
        "primary": "Complete the task: Require context and native language review for cultural claims",
        "queryHypothesis": "japanese character naming sensitivity review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require context and native language review for cultural claims?",
        "When should japanese character naming sensitivity review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require context and native language review for cultural claims",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require context and native language review for cultural claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-era-mismatch-review",
          "score": 0.2581818181818182,
          "sharedProfile": true,
          "difference": "Require context and native language review for cultural claims versus Flag unsupported period claims for a specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-offensive-association-review",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Require context and native language review for cultural claims versus Route context dependent issues to human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mystery-naming-sensitivity-review",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Require context and native language review for cultural claims versus Avoid treating ethnicity inferred from a name as evidence of guilt; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require context and native language review for cultural claims",
        "outline": [
          "Explain the specific decision: Require context and native language review for cultural claims",
          "Define the applicable contract and limits for Japanese character naming sensitivity review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require context and native language review for cultural claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require context and native language review for cultural claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:295",
      "profileSource": "data/profiles.json#japanese-writing"
    },
    {
      "id": "nw-character-localization-name-map",
      "slug": "character-localization-name-map",
      "name": "Character localization name map",
      "category": "localization",
      "urls": {
        "en": "/en/tools/character-localization-name-map/",
        "ja": "/ja/tools/character-localization-name-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Maintain stable character IDs across English and Japanese forms",
      "task": "Maintain stable character IDs across English and Japanese forms",
      "searchIntent": {
        "primary": "Complete the task: Maintain stable character IDs across English and Japanese forms",
        "queryHypothesis": "character localization name map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain stable character IDs across English and Japanese forms?",
        "When should character localization name map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "sourceIdentities",
          "use": "Stable person IDs with source forms and approved readings."
        },
        {
          "key": "targetCandidates",
          "use": "Alternative target forms with translator notes."
        },
        {
          "key": "dependencies",
          "use": "Identify puns, initials, reveals and prop spellings that depend on names."
        },
        {
          "key": "localeFixtures",
          "use": "Test actual English and Japanese credit or dialogue surfaces."
        }
      ],
      "rules": [
        "Never use display strings as identity keys.",
        "Check whether distinct source identities converge to one target form.",
        "For every clue record preserved, changed or unresolved function.",
        "Only approved complete locales receive language-alternate links in public builds.",
        "Resolve credits by stable creator or character ID",
        "Treat layout evidence as a locale-specific review",
        "Preserve prior mappings in a reversible change log"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Never use display strings as identity keys.",
        "Check whether distinct source identities converge to one target form.",
        "For every clue record preserved, changed or unresolved function.",
        "Only approved complete locales receive language-alternate links in public builds.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "stable-ID bilingual map",
        "decision and tradeoff notes",
        "clue regression list",
        "art and audio edits required",
        "review status per locale",
        "Locale keyed credit list",
        "Width proof linked to mapping",
        "Before-after locale mapping"
      ],
      "capabilities": [
        "Compare name based clue behavior across two languages.",
        "Trace one localized change through props, dialogue and credits."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The work creates an editorial identity correspondence across languages, including ambiguity and clue regressions; it is not a language toggle on generation.",
        "proposedDifferenceAxes": [
          "data",
          "inputs",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-localization-name-bible",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Maintain stable character IDs across English and Japanese forms versus Maintain approved forms for editors and translators; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Maintain stable character IDs across English and Japanese forms versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Maintain stable character IDs across English and Japanese forms versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Localize the naming decision and story function, not just the letters.",
        "outline": [
          "Freeze identity before discussing spelling",
          "Write down what a clue must preserve",
          "Three options when initials no longer work",
          "The translated cast program that accidentally exposes a disguise",
          "Hand off losses as well as decisions"
        ],
        "story": "Fictional example: a theater program uses a localized stage name that accidentally matches the concealed civilian identity. The editor changes the program credit and explicitly records a new clue path.",
        "storyAnalysis": "The fix must update a prop, not only a dialogue string. Compare retention, transliteration and functional adaptation without declaring one universally best.",
        "evidence": "Ren'Py translation documentation confirms distinct dialogue, interface, image and style translation surfaces; specific English-Japanese choices require translator review.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/localization.md",
        "localizedBodies": {
          "en": "content/en/localization.md",
          "ja": "content/ja/localization.md"
        }
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Two source characters mapped to the same target nickname produce a collision.",
        "An unresolved target article is excluded from hreflang and public sitemap.",
        "Changing a display spelling preserves the character ID.",
        "A source initials clue with incompatible target initials is marked unresolved.",
        "Spelling revision changes display without changing ID",
        "Missing proof is not labeled passed",
        "Restoring version preserves character ID"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:299",
      "profileSource": "data/profiles.json#localization",
      "absorbedModules": [
        {
          "sourceId": "nw-localized-name-credits-reconciliation",
          "input": "creditSurfaces",
          "rule": "Resolve credits by stable creator or character ID",
          "output": "Locale keyed credit list",
          "acceptance": "Spelling revision changes display without changing ID",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-localized-name-typography-proof",
          "input": "targetSurface",
          "rule": "Treat layout evidence as a locale-specific review",
          "output": "Width proof linked to mapping",
          "acceptance": "Missing proof is not labeled passed",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-localized-name-version-migration",
          "input": "mappingVersion",
          "rule": "Preserve prior mappings in a reversible change log",
          "output": "Before-after locale mapping",
          "acceptance": "Restoring version preserves character ID",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "localization",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "mapping",
          "label": [
            "Source and target forms",
            "原文と対象言語の表記"
          ],
          "type": "textarea",
          "default": "a | Aven Reed | エイヴン・リード | draft\nb | Arden Reed | エイヴン・リード | draft\nc | Sela Morrow | | draft",
          "help": [
            "ID | source name | target name | review status. These are supplied editorial proposals, not machine translations.",
            "ID | 原文の名前 | 対象言語の名前 | 確認状況。入力例は編集上の案で、自動翻訳の結果ではありません。"
          ]
        },
        {
          "key": "clues",
          "label": [
            "Name-dependent clue tokens",
            "名前に依存する手掛かり"
          ],
          "type": "textarea",
          "default": "a | AR | ER",
          "help": [
            "ID | source clue token | target clue token. Unequal or missing tokens require an explicit redesign.",
            "ID | 原文の手掛かり | 対象言語の手掛かり。不一致や欠落は再設計が必要です。"
          ]
        },
        {
          "key": "mappingVersion",
          "label": [
            "Mapping version",
            "対応表の版"
          ],
          "type": "text",
          "default": "1",
          "help": null
        },
        {
          "key": "previousMapping",
          "label": [
            "Previous approved mapping",
            "以前の対応表"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | source form | previous target form",
            "ID | 原文表記 | 以前の訳名"
          ]
        },
        {
          "key": "assets",
          "label": [
            "Dependent production assets",
            "依存する制作素材"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "asset ID | character ID | prop/dialogue/credit/audio | current target form",
            "素材ID | 人物ID | prop/dialogue/credit/audio | 現在の表記"
          ]
        },
        {
          "key": "targetSurfaces",
          "label": [
            "Target edition typography surfaces",
            "訳名を置く制作面"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "character ID | label | inner width px | font size px | local font family",
            "人物ID | ラベル | 内側の幅px | 文字サイズpx | ローカル書体"
          ]
        }
      ]
    },
    {
      "id": "nw-transliteration-decision-log",
      "slug": "transliteration-decision-log",
      "name": "Transliteration decision log",
      "category": "localization",
      "urls": {
        "en": "/en/tools/transliteration-decision-log/",
        "ja": "/ja/tools/transliteration-decision-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Authors inventing symbol systems for names on maps, props and identity clues.",
      "scenario": "Two invented stations share a sign because a whole-name mapping and overlapping smaller rules also permit a second name.",
      "task": "Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs.",
      "searchIntent": {
        "primary": "Inspect ambiguity and reversibility in an authored name code.",
        "queryHypothesis": "invented script name encoder decoder ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can several segmentations still identify one name?",
        "Why does one displayed inscription decode to two names?",
        "What does an exact round-trip proof cover?"
      ],
      "inputs": [
        {
          "key": "rules",
          "type": "textarea",
          "purpose": "1–80 objects, exactly id/plain/encoded. Each side is 1–8 code points, ≤16 UTF-16 units, without control characters. IDs are unique ASCII-letter-led labels ≤40. Identical pairs are rejected; shared sides and prefix overlap remain visible. These symbols are fictional rules, not a real script."
        },
        {
          "key": "direction",
          "type": "select",
          "purpose": "Choose the direction of the authored correspondence."
        },
        {
          "key": "input",
          "type": "textarea",
          "purpose": "Nonblank, at most 80 code points and 160 UTF-16 units. Exact comparison only: no Unicode normalization, case folding, inferred pronunciation or silent unknown-character deletion."
        },
        {
          "key": "sampleLimit",
          "type": "number",
          "purpose": "Caps presentation, not the exact derivation count. Several derivations may share one displayed output. Complete inverse-return counts are proved separately for each displayed output."
        },
        {
          "key": "context",
          "type": "textarea",
          "purpose": "≤1000 UTF-16 units, kept in copying, favorites and exports. Creative associations are yours; the workbench does not establish etymology or cultural authenticity."
        }
      ],
      "rules": [
        "Author supplies 1–80 exact nonempty variable-length mappings; each side 1–8 Unicode code points and ≤16 UTF-16 units. Reject duplicate pairs, malformed Unicode, controls and unsupported fields. No normalization or inferred phonology.",
        "Build the entire finite parse DAG over ≤80 source code points. Count all complete derivations with BigInt independently of the 1–12 displayed witnesses. Group only displayed outputs and disclose uninspected alternatives.",
        "For each displayed output, count every inverse derivation and exactly how many reconstruct the original input. Produce a concrete different-name witness when any inverse does not return. Several segmentations can still return one name.",
        "Decode ambiguity remains unresolved when distinct output names exist even if each inverse returns the same source inscription. A complete result for one input is not an alphabet-wide bijection certificate.",
        "Unknown suffixes stop complete parsing, retain the unmatched portion and explain the farthest reachable prefix; no silent pass-through. Opposite-direction UI checks current rules/input/direction/cap/context before applying the selected output.",
        "Private copies, favorites and audits preserve authored rules, exact source, counterexamples and creative context. Symbols and associations are fictional, with no actual-script or etymological claim."
      ],
      "requiredData": [
        {
          "description": "Original fictional Varen/Vali station sign and authored abstract symbol mappings.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied plain/encoded units; no attested script or personal-name dictionary is asserted.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Author supplies 1–80 exact nonempty variable-length mappings; each side 1–8 Unicode code points and ≤16 UTF-16 units. Reject duplicate pairs, malformed Unicode, controls and unsupported fields. No normalization or inferred phonology.",
        "Build the entire finite parse DAG over ≤80 source code points. Count all complete derivations with BigInt independently of the 1–12 displayed witnesses. Group only displayed outputs and disclose uninspected alternatives.",
        "For each displayed output, count every inverse derivation and exactly how many reconstruct the original input. Produce a concrete different-name witness when any inverse does not return. Several segmentations can still return one name.",
        "Decode ambiguity remains unresolved when distinct output names exist even if each inverse returns the same source inscription. A complete result for one input is not an alphabet-wide bijection certificate.",
        "Unknown suffixes stop complete parsing, retain the unmatched portion and explain the farthest reachable prefix; no silent pass-through. Opposite-direction UI checks current rules/input/direction/cap/context before applying the selected output.",
        "Private copies, favorites and audits preserve authored rules, exact source, counterexamples and creative context. Symbols and associations are fictional, with no actual-script or etymological claim."
      ],
      "outputs": [
        "Exact forward derivation count and displayed-output scope.",
        "Code-point spans and mapping IDs for each displayed derivation.",
        "Complete inverse and original-return counts, concrete counterexamples and shared-side warnings.",
        "Guarded opposite-direction inspection and private source-bound audit."
      ],
      "capabilities": [
        "Exact all-derivation count on a finite variable-length parse lattice, independent of sample cap.",
        "Complete inverse-return counting with actual different-output witness; distinguish segmentation redundancy from name ambiguity.",
        "Source-guarded opposite-direction handoff that changes actual parsing behavior."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Real-language localization compares approved identity forms and fictional sound history applies ordered changes. This task constructs an exact parse lattice from a user-authored bidirectional code, counts competing derivations and supplies inverse counterexamples. Neither approved translations nor ordered sound rules establish reversible tokenization.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "fictional-language-sound-change",
          "difference": "Ordered sound changes transform successive historical forms; a variable-length code needs alternative tokenizations, derivation counts and complete inverse-return proofs, with no claim of historical or phonetic change."
        }
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-name-edit-decision-log",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs. versus Preserve reasons, reviewers and affected passages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-transliteration-provenance",
          "score": 0.1025,
          "sharedProfile": false,
          "difference": "Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs. versus Record the system and manual exceptions for each form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs. versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "An attractive inscription may conceal a second name; distinguish visible symbols, segmentation paths and identity readings before using ambiguity as a plot device.",
        "outline": [
          "A station sign with two readings",
          "Exact mapping contract",
          "Complete segmentation instead of greedy matching",
          "Derivations versus names",
          "Complete inverse-return proof",
          "Changing the story by changing one symbol",
          "Private audit and editorial handoff"
        ],
        "story": "A model railway uses a station inscription for Varen. Another maker reads Vali through a shared symbol. Their disagreement concerns the sign, not either maker’s honesty, and repairing one unit changes the planned invitation.",
        "storyAnalysis": "Changing li from □ to ● preserves two Varen segmentations but removes the unintended Vali reading. Keeping the collision can support a deliberate clue, but the algorithm cannot establish reader fairness or narrative quality.",
        "evidence": "Original EN/JA manuscripts, executable fictional mapping fixtures and recorded browser checks; no real-language transliteration facts.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/scriptCodec.md",
        "localizedBodies": {
          "en": "content/en/scriptCodec.md",
          "ja": "content/ja/scriptCodec.md"
        }
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default varen has two forward derivations and one inscription; three inverse derivations include two returns and the different name vali.",
        "Changing only li’s symbol to ● removes the different-name reading while preserving two equivalent segmentations.",
        "Decoding △□ yields two different names and remains partial even if both can encode back.",
        "A cap of one never changes exact totals; unknown suffixes and greedy dead ends behave according to full parse rules.",
        "Malformed input clears old proof; private copies/exports and actual UI reverse controls retain source context.",
        "Both localized pages must pass desktop/mobile checks, article budgets, original-scene and counterfactual checks."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:300",
      "profileSource": "data/profiles.json#localization",
      "specBatch": "batch-14",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Variable-length parse DAG, exact BigInt counts, constrained inverse counting and constructive counterexample recovery."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "scriptCodec",
        "engineFiles": [
          "web/script-codec.mjs",
          "web/script-codec-tool.mjs",
          "web/script-codec-view.mjs",
          "web/script-codec-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/script-codec.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "rules",
          "label": [
            "Authored mapping rules · JSON",
            "作者の対応規則・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"va\",\n    \"plain\": \"va\",\n    \"encoded\": \"△\"\n  },\n  {\n    \"id\": \"ren\",\n    \"plain\": \"ren\",\n    \"encoded\": \"□\"\n  },\n  {\n    \"id\": \"whole\",\n    \"plain\": \"varen\",\n    \"encoded\": \"△□\"\n  },\n  {\n    \"id\": \"li\",\n    \"plain\": \"li\",\n    \"encoded\": \"□\"\n  }\n]",
          "help": [
            "1–80 objects, exactly id/plain/encoded. Each side is 1–8 code points, ≤16 UTF-16 units, without control characters. IDs are unique ASCII-letter-led labels ≤40. Identical pairs are rejected; shared sides and prefix overlap remain visible. These symbols are fictional rules, not a real script.",
            "id/plain/encodedだけの1〜80件。各側は1〜8コードポイント、16 UTF-16単位以内で制御文字不可。idは英字始まりの固有ラベル40以内。同じ組は拒否し、片側の共有や先頭の重なりは明示します。実在文字でなく架空の規則です。"
          ],
          "maxLength": 60000
        },
        {
          "key": "direction",
          "label": [
            "Direction",
            "変換方向"
          ],
          "type": "select",
          "default": "encode",
          "help": null,
          "options": [
            [
              "encode",
              [
                "Plain units → authored symbols",
                "元の単位 → 作者の記号"
              ]
            ],
            [
              "decode",
              [
                "Authored symbols → plain units",
                "作者の記号 → 元の単位"
              ]
            ]
          ]
        },
        {
          "key": "input",
          "label": [
            "Exact name or inscription",
            "正確な名前・刻印"
          ],
          "type": "textarea",
          "default": "varen",
          "help": [
            "Nonblank, at most 80 code points and 160 UTF-16 units. Exact comparison only: no Unicode normalization, case folding, inferred pronunciation or silent unknown-character deletion.",
            "空でない80コードポイントかつ160 UTF-16単位以内。完全一致のみで、Unicode正規化、大小文字同一視、発音推測、不明文字の削除はしません。"
          ],
          "maxLength": 160
        },
        {
          "key": "sampleLimit",
          "label": [
            "Displayed derivations · 1–12",
            "表示する導出・1〜12"
          ],
          "type": "number",
          "default": 8,
          "help": [
            "Caps presentation, not the exact derivation count. Several derivations may share one displayed output. Complete inverse-return counts are proved separately for each displayed output.",
            "表示だけの上限で、全導出数を減らしません。複数の導出が一つの出力を共有することもあります。表示した各出力の逆帰還数は別に全件を検証します。"
          ]
        },
        {
          "key": "context",
          "label": [
            "Private story context · optional",
            "非公開の物語文脈・任意"
          ],
          "type": "textarea",
          "default": "An invented station sign can encode varen through one whole-name rule or two smaller units. Shared □ also permits vali, so the author must decide whether to distinguish the labels.",
          "help": [
            "≤1000 UTF-16 units, kept in copying, favorites and exports. Creative associations are yours; the workbench does not establish etymology or cultural authenticity.",
            "1000 UTF-16単位以内。コピー、保存候補、書き出しに残します。連想は作者の設定で、語源や文化的な真正性を認定するものではありません。"
          ],
          "maxLength": 1000
        }
      ]
    },
    {
      "id": "nw-name-translation-versus-retention",
      "slug": "name-translation-versus-retention",
      "name": "Name translation versus retention",
      "category": "localization",
      "urls": {
        "en": "/en/tools/name-translation-versus-retention/",
        "ja": "/ja/tools/name-translation-versus-retention/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Record why a meaningful name is translated or retained",
      "task": "Record why a meaningful name is translated or retained",
      "searchIntent": {
        "primary": "Complete the task: Record why a meaningful name is translated or retained",
        "queryHypothesis": "name translation versus retention",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record why a meaningful name is translated or retained?",
        "When should name translation versus retention be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record why a meaningful name is translated or retained",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record why a meaningful name is translated or retained. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-honorific-policy",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Record why a meaningful name is translated or retained versus Compare retained, translated and omitted forms with scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-title-translation-ambiguity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Record why a meaningful name is translated or retained versus Preserve office function when a target language term is imperfect; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-red-herring-control",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Record why a meaningful name is translated or retained versus Show why a false association is plausible but not proof; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record why a meaningful name is translated or retained",
        "outline": [
          "Explain the specific decision: Record why a meaningful name is translated or retained",
          "Define the applicable contract and limits for Name translation versus retention",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record why a meaningful name is translated or retained; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record why a meaningful name is translated or retained",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:301",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-bilingual-cast-collision-audit",
      "slug": "bilingual-cast-collision-audit",
      "name": "Bilingual cast collision audit",
      "category": "localization",
      "urls": {
        "en": "/en/tools/bilingual-cast-collision-audit/",
        "ja": "/ja/tools/bilingual-cast-collision-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Check whether distinct source names merge in the target language",
      "task": "Check whether distinct source names merge in the target language",
      "searchIntent": {
        "primary": "Complete the task: Check whether distinct source names merge in the target language",
        "queryHypothesis": "bilingual cast collision audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check whether distinct source names merge in the target language?",
        "When should bilingual cast collision audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check whether distinct source names merge in the target language",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check whether distinct source names merge in the target language. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Check whether distinct source names merge in the target language versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-gender-assumption-audit",
          "score": 0.15833333333333333,
          "sharedProfile": true,
          "difference": "Check whether distinct source names merge in the target language versus Flag unintended target language signals for human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-trade-language-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Check whether distinct source names merge in the target language versus Create contact forms distinct from native language names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check whether distinct source names merge in the target language",
        "outline": [
          "Explain the specific decision: Check whether distinct source names merge in the target language",
          "Define the applicable contract and limits for Bilingual cast collision audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check whether distinct source names merge in the target language; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check whether distinct source names merge in the target language",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:302",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-nickname-relationship",
      "slug": "localized-nickname-relationship",
      "name": "Localized nickname relationship",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-nickname-relationship/",
        "ja": "/ja/tools/localized-nickname-relationship/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Preserve who may use each nickname across languages",
      "task": "Preserve who may use each nickname across languages",
      "searchIntent": {
        "primary": "Complete the task: Preserve who may use each nickname across languages",
        "queryHypothesis": "localized nickname relationship",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve who may use each nickname across languages?",
        "When should localized nickname relationship be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve who may use each nickname across languages",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve who may use each nickname across languages. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-consent-map",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Preserve who may use each nickname across languages versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shared-campaign-naming-authority",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Preserve who may use each nickname across languages versus Record who may introduce or revise each naming rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reclaimed-insult-name",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Preserve who may use each nickname across languages versus Trace who may use a reclaimed label and when; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve who may use each nickname across languages",
        "outline": [
          "Explain the specific decision: Preserve who may use each nickname across languages",
          "Define the applicable contract and limits for Localized nickname relationship",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve who may use each nickname across languages; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve who may use each nickname across languages",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:303",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-title-identity-map",
      "slug": "localized-title-identity-map",
      "name": "Localized title identity map",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-title-identity-map/",
        "ja": "/ja/tools/localized-title-identity-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Separate translated titles from stable personal identity",
      "task": "Separate translated titles from stable personal identity",
      "searchIntent": {
        "primary": "Complete the task: Separate translated titles from stable personal identity",
        "queryHypothesis": "localized title identity map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate translated titles from stable personal identity?",
        "When should localized title identity map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate translated titles from stable personal identity",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate translated titles from stable personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-detective-notebook-identity-map",
          "score": 0.2095238095238095,
          "sharedProfile": false,
          "difference": "Separate translated titles from stable personal identity versus Separate hypothesis, testimony and corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-terminology-drift-audit",
          "score": 0.19444444444444442,
          "sharedProfile": true,
          "difference": "Separate translated titles from stable personal identity versus Detect one identity translated inconsistently across episodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate translated titles from stable personal identity versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate translated titles from stable personal identity",
        "outline": [
          "Explain the specific decision: Separate translated titles from stable personal identity",
          "Define the applicable contract and limits for Localized title identity map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate translated titles from stable personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate translated titles from stable personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:304",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-alias-reveal-parity",
      "slug": "localized-alias-reveal-parity",
      "name": "Localized alias reveal parity",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-alias-reveal-parity/",
        "ja": "/ja/tools/localized-alias-reveal-parity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Keep clue timing comparable across language editions",
      "task": "Keep clue timing comparable across language editions",
      "searchIntent": {
        "primary": "Complete the task: Keep clue timing comparable across language editions",
        "queryHypothesis": "localized alias reveal parity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep clue timing comparable across language editions?",
        "When should localized alias reveal parity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep clue timing comparable across language editions",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep clue timing comparable across language editions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-signature-consistency",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Keep clue timing comparable across language editions versus Keep a drawn signature recognizable across localized editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-scene-exercise",
          "score": 0.17575757575757575,
          "sharedProfile": false,
          "difference": "Keep clue timing comparable across language editions versus Compare fair clue placement before a controlled reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-comprehension",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Keep clue timing comparable across language editions versus Test whether readers understand an identity connection at the intended moment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep clue timing comparable across language editions",
        "outline": [
          "Explain the specific decision: Keep clue timing comparable across language editions",
          "Define the applicable contract and limits for Localized alias reveal parity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep clue timing comparable across language editions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep clue timing comparable across language editions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:305",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-pun-name-tradeoff",
      "slug": "localized-pun-name-tradeoff",
      "name": "Localized pun name tradeoff",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-pun-name-tradeoff/",
        "ja": "/ja/tools/localized-pun-name-tradeoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Compare sound, meaning and story function with explicit losses",
      "task": "Compare sound, meaning and story function with explicit losses",
      "searchIntent": {
        "primary": "Complete the task: Compare sound, meaning and story function with explicit losses",
        "queryHypothesis": "localized pun name tradeoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare sound, meaning and story function with explicit losses?",
        "When should localized pun name tradeoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare sound, meaning and story function with explicit losses",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare sound, meaning and story function with explicit losses. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare sound, meaning and story function with explicit losses versus Remove overdetermined motifs while preserving relevant story function; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-loan-adaptation",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare sound, meaning and story function with explicit losses versus Apply explicit sound substitutions to borrowed names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Compare sound, meaning and story function with explicit losses versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare sound, meaning and story function with explicit losses",
        "outline": [
          "Explain the specific decision: Compare sound, meaning and story function with explicit losses",
          "Define the applicable contract and limits for Localized pun name tradeoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare sound, meaning and story function with explicit losses; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare sound, meaning and story function with explicit losses",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:306",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-anagram-clue",
      "slug": "localized-anagram-clue",
      "name": "Localized anagram clue",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-anagram-clue/",
        "ja": "/ja/tools/localized-anagram-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Rebuild a name puzzle with solvability evidence in each language",
      "task": "Rebuild a name puzzle with solvability evidence in each language",
      "searchIntent": {
        "primary": "Complete the task: Rebuild a name puzzle with solvability evidence in each language",
        "queryHypothesis": "localized anagram clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to rebuild a name puzzle with solvability evidence in each language?",
        "When should localized anagram clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Rebuild a name puzzle with solvability evidence in each language",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Rebuild a name puzzle with solvability evidence in each language. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-translated-name-clue",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Rebuild a name puzzle with solvability evidence in each language versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-formal-informal-contrast",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Rebuild a name puzzle with solvability evidence in each language versus Rebuild relationship distance through approved language choices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Rebuild a name puzzle with solvability evidence in each language versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Rebuild a name puzzle with solvability evidence in each language",
        "outline": [
          "Explain the specific decision: Rebuild a name puzzle with solvability evidence in each language",
          "Define the applicable contract and limits for Localized anagram clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Rebuild a name puzzle with solvability evidence in each language; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Rebuild a name puzzle with solvability evidence in each language",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:307",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-acrostic-name-clue",
      "slug": "localized-acrostic-name-clue",
      "name": "Localized acrostic name clue",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-acrostic-name-clue/",
        "ja": "/ja/tools/localized-acrostic-name-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Reconcile translated names with an acrostic used in the plot",
      "task": "Reconcile translated names with an acrostic used in the plot",
      "searchIntent": {
        "primary": "Complete the task: Reconcile translated names with an acrostic used in the plot",
        "queryHypothesis": "localized acrostic name clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile translated names with an acrostic used in the plot?",
        "When should localized acrostic name clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile translated names with an acrostic used in the plot",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile translated names with an acrostic used in the plot. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.23249999999999998,
          "sharedProfile": true,
          "difference": "Reconcile translated names with an acrostic used in the plot versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Reconcile translated names with an acrostic used in the plot versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-initials-clue",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Reconcile translated names with an acrostic used in the plot versus Repair initials dependent reveals without changing unrelated character facts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile translated names with an acrostic used in the plot",
        "outline": [
          "Explain the specific decision: Reconcile translated names with an acrostic used in the plot",
          "Define the applicable contract and limits for Localized acrostic name clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile translated names with an acrostic used in the plot; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile translated names with an acrostic used in the plot",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:308",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-initials-clue",
      "slug": "localized-initials-clue",
      "name": "Localized initials clue",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-initials-clue/",
        "ja": "/ja/tools/localized-initials-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Repair initials dependent reveals without changing unrelated character facts",
      "task": "Repair initials dependent reveals without changing unrelated character facts",
      "searchIntent": {
        "primary": "Complete the task: Repair initials dependent reveals without changing unrelated character facts",
        "queryHypothesis": "localized initials clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to repair initials dependent reveals without changing unrelated character facts?",
        "When should localized initials clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Repair initials dependent reveals without changing unrelated character facts",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Repair initials dependent reveals without changing unrelated character facts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-initials-clue-fairness",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Repair initials dependent reveals without changing unrelated character facts versus Check all plausible suspects rather than only the intended solution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Repair initials dependent reveals without changing unrelated character facts versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Repair initials dependent reveals without changing unrelated character facts versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Repair initials dependent reveals without changing unrelated character facts",
        "outline": [
          "Explain the specific decision: Repair initials dependent reveals without changing unrelated character facts",
          "Define the applicable contract and limits for Localized initials clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Repair initials dependent reveals without changing unrelated character facts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Repair initials dependent reveals without changing unrelated character facts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:309",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-length-budget",
      "slug": "localized-name-length-budget",
      "name": "Localized name length budget",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-length-budget/",
        "ja": "/ja/tools/localized-name-length-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Fit approved forms to actual UI or balloon constraints",
      "task": "Fit approved forms to actual UI or balloon constraints",
      "searchIntent": {
        "primary": "Complete the task: Fit approved forms to actual UI or balloon constraints",
        "queryHypothesis": "localized name length budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to fit approved forms to actual UI or balloon constraints?",
        "When should localized name length budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Fit approved forms to actual UI or balloon constraints",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Fit approved forms to actual UI or balloon constraints. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-ambiguity-budget",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Fit approved forms to actual UI or balloon constraints versus Track newly introduced collisions and intentional ambiguity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-hud-budget",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Fit approved forms to actual UI or balloon constraints versus Fit approved names to actual rendered HUD dimensions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dub-name-length-tradeoff",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Fit approved forms to actual UI or balloon constraints versus Compare lip timing constraints with identity continuity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Fit approved forms to actual UI or balloon constraints",
        "outline": [
          "Explain the specific decision: Fit approved forms to actual UI or balloon constraints",
          "Define the applicable contract and limits for Localized name length budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Fit approved forms to actual UI or balloon constraints; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Fit approved forms to actual UI or balloon constraints",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:310",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-pronunciation-notes",
      "slug": "localized-name-pronunciation-notes",
      "name": "Localized name pronunciation notes",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-pronunciation-notes/",
        "ja": "/ja/tools/localized-name-pronunciation-notes/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Provide recording references approved by the creator",
      "task": "Provide recording references approved by the creator",
      "searchIntent": {
        "primary": "Complete the task: Provide recording references approved by the creator",
        "queryHypothesis": "localized name pronunciation notes",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide recording references approved by the creator?",
        "When should localized name pronunciation notes be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide recording references approved by the creator",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide recording references approved by the creator. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-voice-pronunciation-parity",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Provide recording references approved by the creator versus Align creator approved forms across recording languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-that-cannot-be-spoken",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Provide recording references approved by the creator versus Provide alternative references with explicit fictional consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Provide recording references approved by the creator versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide recording references approved by the creator",
        "outline": [
          "Explain the specific decision: Provide recording references approved by the creator",
          "Define the applicable contract and limits for Localized name pronunciation notes",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide recording references approved by the creator; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide recording references approved by the creator",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:311",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-order-style-sheet",
      "slug": "localized-name-order-style-sheet",
      "name": "Localized name order style sheet",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-order-style-sheet/",
        "ja": "/ja/tools/localized-name-order-style-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Record context dependent display order rules",
      "task": "Record context dependent display order rules",
      "searchIntent": {
        "primary": "Complete the task: Record context dependent display order rules",
        "queryHypothesis": "localized name order style sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record context dependent display order rules?",
        "When should localized name order style sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record context dependent display order rules",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record context dependent display order rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-order-policy",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Record context dependent display order rules versus Keep display order consistent across narration and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-offensive-association-review",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Record context dependent display order rules versus Route context dependent issues to human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-order-initiation-names",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Record context dependent display order rules versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record context dependent display order rules",
        "outline": [
          "Explain the specific decision: Record context dependent display order rules",
          "Define the applicable contract and limits for Localized name order style sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record context dependent display order rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record context dependent display order rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:312",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-honorific-policy",
      "slug": "localized-honorific-policy",
      "name": "Localized honorific policy",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-honorific-policy/",
        "ja": "/ja/tools/localized-honorific-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Compare retained, translated and omitted forms with scene consequences",
      "task": "Compare retained, translated and omitted forms with scene consequences",
      "searchIntent": {
        "primary": "Complete the task: Compare retained, translated and omitted forms with scene consequences",
        "queryHypothesis": "localized honorific policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare retained, translated and omitted forms with scene consequences?",
        "When should localized honorific policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare retained, translated and omitted forms with scene consequences",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare retained, translated and omitted forms with scene consequences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-honorific-policy-for-fiction",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Compare retained, translated and omitted forms with scene consequences versus Define a consistent policy using sourced language guidance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare retained, translated and omitted forms with scene consequences versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-translation-versus-retention",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Compare retained, translated and omitted forms with scene consequences versus Record why a meaningful name is translated or retained; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare retained, translated and omitted forms with scene consequences",
        "outline": [
          "Explain the specific decision: Compare retained, translated and omitted forms with scene consequences",
          "Define the applicable contract and limits for Localized honorific policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare retained, translated and omitted forms with scene consequences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare retained, translated and omitted forms with scene consequences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:313",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-kinship-address-policy",
      "slug": "localized-kinship-address-policy",
      "name": "Localized kinship address policy",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-kinship-address-policy/",
        "ja": "/ja/tools/localized-kinship-address-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Preserve relationship information when terms do not align",
      "task": "Preserve relationship information when terms do not align",
      "searchIntent": {
        "primary": "Complete the task: Preserve relationship information when terms do not align",
        "queryHypothesis": "localized kinship address policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve relationship information when terms do not align?",
        "When should localized kinship address policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve relationship information when terms do not align",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve relationship information when terms do not align. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-found-family-address-system",
          "score": 0.15,
          "sharedProfile": false,
          "difference": "Preserve relationship information when terms do not align versus Design elective kinship terms without implying blood relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-reveal-regression-test",
          "score": 0.14285714285714285,
          "sharedProfile": true,
          "difference": "Preserve relationship information when terms do not align versus Verify that revised names do not expose hidden identities early; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-honorific-policy",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Preserve relationship information when terms do not align versus Compare retained, translated and omitted forms with scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve relationship information when terms do not align",
        "outline": [
          "Explain the specific decision: Preserve relationship information when terms do not align",
          "Define the applicable contract and limits for Localized kinship address policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve relationship information when terms do not align; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve relationship information when terms do not align",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:314",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-formal-informal-contrast",
      "slug": "localized-formal-informal-contrast",
      "name": "Localized formal informal contrast",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-formal-informal-contrast/",
        "ja": "/ja/tools/localized-formal-informal-contrast/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Rebuild relationship distance through approved language choices",
      "task": "Rebuild relationship distance through approved language choices",
      "searchIntent": {
        "primary": "Complete the task: Rebuild relationship distance through approved language choices",
        "queryHypothesis": "localized formal informal contrast",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to rebuild relationship distance through approved language choices?",
        "When should localized formal informal contrast be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Rebuild relationship distance through approved language choices",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Rebuild relationship distance through approved language choices. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Rebuild relationship distance through approved language choices versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-multilingual-address-switching",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Rebuild relationship distance through approved language choices versus Track language and relationship triggers independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estrangement-address-reversal",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Rebuild relationship distance through approved language choices versus Restore distance through deliberate naming changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Rebuild relationship distance through approved language choices",
        "outline": [
          "Explain the specific decision: Rebuild relationship distance through approved language choices",
          "Define the applicable contract and limits for Localized formal informal contrast",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Rebuild relationship distance through approved language choices; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Rebuild relationship distance through approved language choices",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:315",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-gender-assumption-audit",
      "slug": "localized-gender-assumption-audit",
      "name": "Localized gender assumption audit",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-gender-assumption-audit/",
        "ja": "/ja/tools/localized-gender-assumption-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Flag unintended target language signals for human review",
      "task": "Flag unintended target language signals for human review",
      "searchIntent": {
        "primary": "Complete the task: Flag unintended target language signals for human review",
        "queryHypothesis": "localized gender assumption audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag unintended target language signals for human review?",
        "When should localized gender assumption audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag unintended target language signals for human review",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag unintended target language signals for human review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-cast-collision-audit",
          "score": 0.15833333333333333,
          "sharedProfile": true,
          "difference": "Flag unintended target language signals for human review versus Check whether distinct source names merge in the target language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-negative-association-review",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Flag unintended target language signals for human review versus Structure human checks for unintended associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-era-mismatch-review",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Flag unintended target language signals for human review versus Flag unsupported period claims for a specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag unintended target language signals for human review",
        "outline": [
          "Explain the specific decision: Flag unintended target language signals for human review",
          "Define the applicable contract and limits for Localized gender assumption audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag unintended target language signals for human review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag unintended target language signals for human review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:316",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-ambiguity-budget",
      "slug": "localized-name-ambiguity-budget",
      "name": "Localized name ambiguity budget",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-ambiguity-budget/",
        "ja": "/ja/tools/localized-name-ambiguity-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Track newly introduced collisions and intentional ambiguity",
      "task": "Track newly introduced collisions and intentional ambiguity",
      "searchIntent": {
        "primary": "Complete the task: Track newly introduced collisions and intentional ambiguity",
        "queryHypothesis": "localized name ambiguity budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track newly introduced collisions and intentional ambiguity?",
        "When should localized name ambiguity budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track newly introduced collisions and intentional ambiguity",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track newly introduced collisions and intentional ambiguity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.2924242424242424,
          "sharedProfile": false,
          "difference": "Track newly introduced collisions and intentional ambiguity versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-length-budget",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Track newly introduced collisions and intentional ambiguity versus Fit approved forms to actual UI or balloon constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-cultural-explanation-budget",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Track newly introduced collisions and intentional ambiguity versus Decide when context is needed and where it belongs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track newly introduced collisions and intentional ambiguity",
        "outline": [
          "Explain the specific decision: Track newly introduced collisions and intentional ambiguity",
          "Define the applicable contract and limits for Localized name ambiguity budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track newly introduced collisions and intentional ambiguity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track newly introduced collisions and intentional ambiguity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:317",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-spoiler-safe-glossary",
      "slug": "localized-spoiler-safe-glossary",
      "name": "Localized spoiler safe glossary",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-spoiler-safe-glossary/",
        "ja": "/ja/tools/localized-spoiler-safe-glossary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Export entries only after the reader reaches the relevant reveal",
      "task": "Export entries only after the reader reaches the relevant reveal",
      "searchIntent": {
        "primary": "Complete the task: Export entries only after the reader reaches the relevant reveal",
        "queryHypothesis": "localized spoiler safe glossary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export entries only after the reader reaches the relevant reveal?",
        "When should localized spoiler safe glossary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export entries only after the reader reaches the relevant reveal",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export entries only after the reader reaches the relevant reveal. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.22499999999999998,
          "sharedProfile": false,
          "difference": "Export entries only after the reader reaches the relevant reveal versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-alias-spoiler-boundary",
          "score": 0.18,
          "sharedProfile": false,
          "difference": "Export entries only after the reader reaches the relevant reveal versus Export reader facing names by installment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-glossary-synchronization",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Export entries only after the reader reaches the relevant reveal versus Compare entries with the approved character ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export entries only after the reader reaches the relevant reveal",
        "outline": [
          "Explain the specific decision: Export entries only after the reader reaches the relevant reveal",
          "Define the applicable contract and limits for Localized spoiler safe glossary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export entries only after the reader reaches the relevant reveal; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export entries only after the reader reaches the relevant reveal",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:318",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-change-impact",
      "slug": "localized-name-change-impact",
      "name": "Localized name change impact",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-change-impact/",
        "ja": "/ja/tools/localized-name-change-impact/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Trace edits through dialogue, art props and credits",
      "task": "Trace edits through dialogue, art props and credits",
      "searchIntent": {
        "primary": "Complete the task: Trace edits through dialogue, art props and credits",
        "queryHypothesis": "localized name change impact",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace edits through dialogue, art props and credits?",
        "When should localized name change impact be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace edits through dialogue, art props and credits",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace edits through dialogue, art props and credits. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.22916666666666666,
          "sharedProfile": false,
          "difference": "Trace edits through dialogue, art props and credits versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-revision-prop-checklist",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace edits through dialogue, art props and credits versus Trace a rename through signs, letters and background art; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Trace edits through dialogue, art props and credits versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace edits through dialogue, art props and credits",
        "outline": [
          "Explain the specific decision: Trace edits through dialogue, art props and credits",
          "Define the applicable contract and limits for Localized name change impact",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace edits through dialogue, art props and credits; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace edits through dialogue, art props and credits",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:319",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-prop-name-continuity",
      "slug": "localized-prop-name-continuity",
      "name": "Localized prop name continuity",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-prop-name-continuity/",
        "ja": "/ja/tools/localized-prop-name-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Reconcile signs and letters with translated dialogue",
      "task": "Reconcile signs and letters with translated dialogue",
      "searchIntent": {
        "primary": "Complete the task: Reconcile signs and letters with translated dialogue",
        "queryHypothesis": "localized prop name continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile signs and letters with translated dialogue?",
        "When should localized prop name continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile signs and letters with translated dialogue",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile signs and letters with translated dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.23249999999999998,
          "sharedProfile": true,
          "difference": "Reconcile signs and letters with translated dialogue versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-revision-prop-checklist",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Reconcile signs and letters with translated dialogue versus Trace a rename through signs, letters and background art; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-dossier-name-system",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile signs and letters with translated dialogue versus Reconcile names across documents, dialogue and narration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile signs and letters with translated dialogue",
        "outline": [
          "Explain the specific decision: Reconcile signs and letters with translated dialogue",
          "Define the applicable contract and limits for Localized prop name continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile signs and letters with translated dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile signs and letters with translated dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:320",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-signature-consistency",
      "slug": "localized-signature-consistency",
      "name": "Localized signature consistency",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-signature-consistency/",
        "ja": "/ja/tools/localized-signature-consistency/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Keep a drawn signature recognizable across localized editions",
      "task": "Keep a drawn signature recognizable across localized editions",
      "searchIntent": {
        "primary": "Complete the task: Keep a drawn signature recognizable across localized editions",
        "queryHypothesis": "localized signature consistency",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep a drawn signature recognizable across localized editions?",
        "When should localized signature consistency be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep a drawn signature recognizable across localized editions",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep a drawn signature recognizable across localized editions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-alias-reveal-parity",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Keep a drawn signature recognizable across localized editions versus Keep clue timing comparable across language editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-ending-signature",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Keep a drawn signature recognizable across localized editions versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-translation-brief",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep a drawn signature recognizable across localized editions versus Preserve author intent across localized bylines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep a drawn signature recognizable across localized editions",
        "outline": [
          "Explain the specific decision: Keep a drawn signature recognizable across localized editions",
          "Define the applicable contract and limits for Localized signature consistency",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep a drawn signature recognizable across localized editions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep a drawn signature recognizable across localized editions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:321",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-text-to-speech-test",
      "slug": "localized-name-text-to-speech-test",
      "name": "Localized name text to speech test",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-text-to-speech-test/",
        "ja": "/ja/tools/localized-name-text-to-speech-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Collect recorded or reviewed pronunciations without accuracy claims",
      "task": "Collect recorded or reviewed pronunciations without accuracy claims",
      "searchIntent": {
        "primary": "Complete the task: Collect recorded or reviewed pronunciations without accuracy claims",
        "queryHypothesis": "localized name text to speech test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect recorded or reviewed pronunciations without accuracy claims?",
        "When should localized name text to speech test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect recorded or reviewed pronunciations without accuracy claims",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect recorded or reviewed pronunciations without accuracy claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.16818181818181818,
          "sharedProfile": true,
          "difference": "Collect recorded or reviewed pronunciations without accuracy claims versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-shortlist-blind-test",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Collect recorded or reviewed pronunciations without accuracy claims versus Collect unaided impressions without showing author explanations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Collect recorded or reviewed pronunciations without accuracy claims versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect recorded or reviewed pronunciations without accuracy claims",
        "outline": [
          "Explain the specific decision: Collect recorded or reviewed pronunciations without accuracy claims",
          "Define the applicable contract and limits for Localized name text to speech test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect recorded or reviewed pronunciations without accuracy claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect recorded or reviewed pronunciations without accuracy claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:323",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-audio-subtitle-identity",
      "slug": "localized-audio-subtitle-identity",
      "name": "Localized audio subtitle identity",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-audio-subtitle-identity/",
        "ja": "/ja/tools/localized-audio-subtitle-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Align spoken names with subtitle display names",
      "task": "Align spoken names with subtitle display names",
      "searchIntent": {
        "primary": "Complete the task: Align spoken names with subtitle display names",
        "queryHypothesis": "localized audio subtitle identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to align spoken names with subtitle display names?",
        "When should localized audio subtitle identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Align spoken names with subtitle display names",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Align spoken names with subtitle display names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-android-cover-identity",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Align spoken names with subtitle display names versus Keep social display separate from production metadata; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-audio-introduction",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Align spoken names with subtitle display names versus Test host introductions and spoken acknowledgments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-subtitle-speaker-name-fit",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Align spoken names with subtitle display names versus Test names in speaker labels at supplied subtitle widths; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Align spoken names with subtitle display names",
        "outline": [
          "Explain the specific decision: Align spoken names with subtitle display names",
          "Define the applicable contract and limits for Localized audio subtitle identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Align spoken names with subtitle display names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Align spoken names with subtitle display names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:324",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-search-alias-map",
      "slug": "localized-name-search-alias-map",
      "name": "Localized name search alias map",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-search-alias-map/",
        "ja": "/ja/tools/localized-name-search-alias-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Record accepted spelling variants without publishing duplicate pages",
      "task": "Record accepted spelling variants without publishing duplicate pages",
      "searchIntent": {
        "primary": "Complete the task: Record accepted spelling variants without publishing duplicate pages",
        "queryHypothesis": "localized name search alias map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record accepted spelling variants without publishing duplicate pages?",
        "When should localized name search alias map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record accepted spelling variants without publishing duplicate pages",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record accepted spelling variants without publishing duplicate pages. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-name-variant-audit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Record accepted spelling variants without publishing duplicate pages versus Find spelling variants for human identity confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-alias-reveal-parity",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Record accepted spelling variants without publishing duplicate pages versus Keep clue timing comparable across language editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Record accepted spelling variants without publishing duplicate pages versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record accepted spelling variants without publishing duplicate pages",
        "outline": [
          "Explain the specific decision: Record accepted spelling variants without publishing duplicate pages",
          "Define the applicable contract and limits for Localized name search alias map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record accepted spelling variants without publishing duplicate pages; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record accepted spelling variants without publishing duplicate pages",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:325",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-cultural-explanation-budget",
      "slug": "localized-cultural-explanation-budget",
      "name": "Localized cultural explanation budget",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-cultural-explanation-budget/",
        "ja": "/ja/tools/localized-cultural-explanation-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Decide when context is needed and where it belongs",
      "task": "Decide when context is needed and where it belongs",
      "searchIntent": {
        "primary": "Complete the task: Decide when context is needed and where it belongs",
        "queryHypothesis": "localized cultural explanation budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide when context is needed and where it belongs?",
        "When should localized cultural explanation budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide when context is needed and where it belongs",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide when context is needed and where it belongs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-ambiguity-budget",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Decide when context is needed and where it belongs versus Track newly introduced collisions and intentional ambiguity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-length-budget",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Decide when context is needed and where it belongs versus Fit approved forms to actual UI or balloon constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Decide when context is needed and where it belongs versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide when context is needed and where it belongs",
        "outline": [
          "Explain the specific decision: Decide when context is needed and where it belongs",
          "Define the applicable contract and limits for Localized cultural explanation budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide when context is needed and where it belongs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide when context is needed and where it belongs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:327",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-historical-name-evidence",
      "slug": "localized-historical-name-evidence",
      "name": "Localized historical name evidence",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-historical-name-evidence/",
        "ja": "/ja/tools/localized-historical-name-evidence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Track sources separately for each locale",
      "task": "Track sources separately for each locale",
      "searchIntent": {
        "primary": "Complete the task: Track sources separately for each locale",
        "queryHypothesis": "localized historical name evidence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track sources separately for each locale?",
        "When should localized historical name evidence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track sources separately for each locale",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track sources separately for each locale. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.25625,
          "sharedProfile": false,
          "difference": "Track sources separately for each locale versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pseudonym-evidence",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Track sources separately for each locale versus Distinguish documented pseudonyms from author invented analogues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Track sources separately for each locale versus Track dictionary evidence separately from creative symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track sources separately for each locale",
        "outline": [
          "Explain the specific decision: Track sources separately for each locale",
          "Define the applicable contract and limits for Localized historical name evidence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track sources separately for each locale; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track sources separately for each locale",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:328",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-invented-language-names",
      "slug": "localized-invented-language-names",
      "name": "Localized invented language names",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-invented-language-names/",
        "ja": "/ja/tools/localized-invented-language-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Preserve fictional grammar while adapting script",
      "task": "Preserve fictional grammar while adapting script",
      "searchIntent": {
        "primary": "Complete the task: Preserve fictional grammar while adapting script",
        "queryHypothesis": "localized invented language names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve fictional grammar while adapting script?",
        "When should localized invented language names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve fictional grammar while adapting script",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve fictional grammar while adapting script. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-trade-language-names",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Preserve fictional grammar while adapting script versus Create contact forms distinct from native language names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Preserve fictional grammar while adapting script versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Preserve fictional grammar while adapting script versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve fictional grammar while adapting script",
        "outline": [
          "Explain the specific decision: Preserve fictional grammar while adapting script",
          "Define the applicable contract and limits for Localized invented language names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve fictional grammar while adapting script; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve fictional grammar while adapting script",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:329",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-nonhuman-speaker-names",
      "slug": "localized-nonhuman-speaker-names",
      "name": "Localized nonhuman speaker names",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-nonhuman-speaker-names/",
        "ja": "/ja/tools/localized-nonhuman-speaker-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Adapt names to a declared perception or speech system",
      "task": "Adapt names to a declared perception or speech system",
      "searchIntent": {
        "primary": "Complete the task: Adapt names to a declared perception or speech system",
        "queryHypothesis": "localized nonhuman speaker names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to adapt names to a declared perception or speech system?",
        "When should localized nonhuman speaker names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Adapt names to a declared perception or speech system",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Adapt names to a declared perception or speech system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nonhuman-identity-translation",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Adapt names to a declared perception or speech system versus Convert an authored sensory identity system into readable labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Adapt names to a declared perception or speech system versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-romanization-source-map",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Adapt names to a declared perception or speech system versus Store the chosen system and exception evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Adapt names to a declared perception or speech system",
        "outline": [
          "Explain the specific decision: Adapt names to a declared perception or speech system",
          "Define the applicable contract and limits for Localized nonhuman speaker names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Adapt names to a declared perception or speech system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Adapt names to a declared perception or speech system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:330",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-trademark-check-log",
      "slug": "localized-name-trademark-check-log",
      "name": "Localized name trademark check log",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-trademark-check-log/",
        "ja": "/ja/tools/localized-name-trademark-check-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Record the scope of external checks without clearance claims",
      "task": "Record the scope of external checks without clearance claims",
      "searchIntent": {
        "primary": "Complete the task: Record the scope of external checks without clearance claims",
        "queryHypothesis": "localized name trademark check log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record the scope of external checks without clearance claims?",
        "When should localized name trademark check log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record the scope of external checks without clearance claims",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record the scope of external checks without clearance claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-public-figure-collision",
          "score": 0.28888888888888886,
          "sharedProfile": false,
          "difference": "Record the scope of external checks without clearance claims versus Structure external checks without claiming uniqueness or clearance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-search-collision-log",
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Record the scope of external checks without clearance claims versus Record dated external checks without claiming exclusivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-text-to-speech-test",
          "score": 0.16818181818181818,
          "sharedProfile": true,
          "difference": "Record the scope of external checks without clearance claims versus Collect recorded or reviewed pronunciations without accuracy claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record the scope of external checks without clearance claims",
        "outline": [
          "Explain the specific decision: Record the scope of external checks without clearance claims",
          "Define the applicable contract and limits for Localized name trademark check log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record the scope of external checks without clearance claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record the scope of external checks without clearance claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:331",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-character-id-export",
      "slug": "localized-character-id-export",
      "name": "Localized character ID export",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-character-id-export/",
        "ja": "/ja/tools/localized-character-id-export/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Produce stable keys and display strings for production pipelines",
      "task": "Produce stable keys and display strings for production pipelines",
      "searchIntent": {
        "primary": "Complete the task: Produce stable keys and display strings for production pipelines",
        "queryHypothesis": "localized character id export",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce stable keys and display strings for production pipelines?",
        "When should localized character id export be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce stable keys and display strings for production pipelines",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce stable keys and display strings for production pipelines. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Produce stable keys and display strings for production pipelines versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Produce stable keys and display strings for production pipelines versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-engine-name-key-migration",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Produce stable keys and display strings for production pipelines versus Keep resource keys stable during display name revisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce stable keys and display strings for production pipelines",
        "outline": [
          "Explain the specific decision: Produce stable keys and display strings for production pipelines",
          "Define the applicable contract and limits for Localized character ID export",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce stable keys and display strings for production pipelines; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce stable keys and display strings for production pipelines",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:332",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-review-handoff",
      "slug": "localized-name-review-handoff",
      "name": "Localized name review handoff",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-review-handoff/",
        "ja": "/ja/tools/localized-name-review-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Package unresolved choices and evidence for a human translator",
      "task": "Package unresolved choices and evidence for a human translator",
      "searchIntent": {
        "primary": "Complete the task: Package unresolved choices and evidence for a human translator",
        "queryHypothesis": "localized name review handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package unresolved choices and evidence for a human translator?",
        "When should localized name review handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package unresolved choices and evidence for a human translator",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package unresolved choices and evidence for a human translator. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-specialist-handoff",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Package unresolved choices and evidence for a human translator versus Package exact questions and candidate evidence for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-translator-handoff",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Package unresolved choices and evidence for a human translator versus Export stable IDs, evidence and unresolved localization decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cultural-reviewer-queue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Package unresolved choices and evidence for a human translator versus Package uncertain claims for named human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package unresolved choices and evidence for a human translator",
        "outline": [
          "Explain the specific decision: Package unresolved choices and evidence for a human translator",
          "Define the applicable contract and limits for Localized name review handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package unresolved choices and evidence for a human translator; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package unresolved choices and evidence for a human translator",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:333",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-terminology-drift-audit",
      "slug": "localized-terminology-drift-audit",
      "name": "Localized terminology drift audit",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-terminology-drift-audit/",
        "ja": "/ja/tools/localized-terminology-drift-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Detect one identity translated inconsistently across episodes",
      "task": "Detect one identity translated inconsistently across episodes",
      "searchIntent": {
        "primary": "Complete the task: Detect one identity translated inconsistently across episodes",
        "queryHypothesis": "localized terminology drift audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect one identity translated inconsistently across episodes?",
        "When should localized terminology drift audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect one identity translated inconsistently across episodes",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect one identity translated inconsistently across episodes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-localization-drift",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Detect one identity translated inconsistently across episodes versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.19444444444444442,
          "sharedProfile": true,
          "difference": "Detect one identity translated inconsistently across episodes versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Detect one identity translated inconsistently across episodes versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect one identity translated inconsistently across episodes",
        "outline": [
          "Explain the specific decision: Detect one identity translated inconsistently across episodes",
          "Define the applicable contract and limits for Localized terminology drift audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect one identity translated inconsistently across episodes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect one identity translated inconsistently across episodes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:334",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-name-memory-test",
      "slug": "localized-name-memory-test",
      "name": "Localized name memory test",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-memory-test/",
        "ja": "/ja/tools/localized-name-memory-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Compare reader recall using language specific test prompts",
      "task": "Compare reader recall using language specific test prompts",
      "searchIntent": {
        "primary": "Complete the task: Compare reader recall using language specific test prompts",
        "queryHypothesis": "localized name memory test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reader recall using language specific test prompts?",
        "When should localized name memory test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reader recall using language specific test prompts",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reader recall using language specific test prompts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-beta-reader-test",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Compare reader recall using language specific test prompts versus Generate blind comparison prompts and record reader confusion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-system-reader-load",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Compare reader recall using language specific test prompts versus Test grammar complexity against reader recall exercises; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-delayed-recall-test",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Compare reader recall using language specific test prompts versus Test recall after a defined reading passage and delay; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reader recall using language specific test prompts",
        "outline": [
          "Explain the specific decision: Compare reader recall using language specific test prompts",
          "Define the applicable contract and limits for Localized name memory test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reader recall using language specific test prompts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reader recall using language specific test prompts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:335",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-localized-reveal-regression-test",
      "slug": "localized-reveal-regression-test",
      "name": "Localized reveal regression test",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-reveal-regression-test/",
        "ja": "/ja/tools/localized-reveal-regression-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Verify that revised names do not expose hidden identities early",
      "task": "Verify that revised names do not expose hidden identities early",
      "searchIntent": {
        "primary": "Complete the task: Verify that revised names do not expose hidden identities early",
        "queryHypothesis": "localized reveal regression test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to verify that revised names do not expose hidden identities early?",
        "When should localized reveal regression test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Verify that revised names do not expose hidden identities early",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Verify that revised names do not expose hidden identities early. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-kinship-address-policy",
          "score": 0.14285714285714285,
          "sharedProfile": true,
          "difference": "Verify that revised names do not expose hidden identities early versus Preserve relationship information when terms do not align; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Verify that revised names do not expose hidden identities early versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-mishearing",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Verify that revised names do not expose hidden identities early versus Design recoverable mishearings that do not depend on false phonetics; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Verify that revised names do not expose hidden identities early",
        "outline": [
          "Explain the specific decision: Verify that revised names do not expose hidden identities early",
          "Define the applicable contract and limits for Localized reveal regression test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Verify that revised names do not expose hidden identities early; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Verify that revised names do not expose hidden identities early",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:337",
      "profileSource": "data/profiles.json#localization"
    },
    {
      "id": "nw-manga-cast-lettering-proof",
      "slug": "manga-cast-lettering-proof",
      "name": "Manga cast lettering proof",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/manga-cast-lettering-proof/",
        "ja": "/ja/tools/manga-cast-lettering-proof/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Preview a cast's names in realistic balloons and captions",
      "task": "Preview a cast's names in realistic balloons and captions",
      "searchIntent": {
        "primary": "Complete the task: Preview a cast's names in realistic balloons and captions",
        "queryHypothesis": "manga cast lettering proof",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preview a cast's names in realistic balloons and captions?",
        "When should manga cast lettering proof be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "approvedNames",
          "use": "Use exact written forms, readings and short forms."
        },
        {
          "key": "panelFixtures",
          "use": "Supply balloon boxes, writing direction and caption locations."
        },
        {
          "key": "font",
          "use": "Measure actual glyph coverage and rendered bounds."
        },
        {
          "key": "readerState",
          "use": "Hide names that are not yet introduced."
        }
      ],
      "rules": [
        "Do not approximate all glyph widths by character count.",
        "A clipped proof remains a failed proof even if its string is valid.",
        "Keep production annotations outside reader-visible lettering.",
        "Do not auto shrink text below a declared readable minimum.",
        "Reflow proof at the requested width rather than rename automatically",
        "Wrap text within measured or explicitly estimated bounds"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Do not approximate all glyph widths by character count.",
        "A clipped proof remains a failed proof even if its string is valid.",
        "Keep production annotations outside reader-visible lettering.",
        "Do not auto shrink text below a declared readable minimum.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "panel linked proofs",
        "overflow and missing glyph issues",
        "reading support alternatives",
        "rename affected prop checklist",
        "Mobile proof and overflow",
        "Wrapped lines and fit status"
      ],
      "capabilities": [
        "Compare ruby and inline reading support at the same panel size.",
        "Track an approved rename into handwritten props and name cards."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The output is a spatial proof of approved names in panels, using actual font metrics and reading order rather than another list of names.",
        "proposedDifferenceAxes": [
          "inputs",
          "evaluation",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.1222222222222222,
          "sharedProfile": true,
          "difference": "Preview a cast's names in realistic balloons and captions versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-dialogue-balloon",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Preview a cast's names in realistic balloons and captions versus Preview line breaks and reading support in constrained balloons; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-new-cast-collision",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Preview a cast's names in realistic balloons and captions versus Compare a proposed cast against previous installments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A good name must survive the panel where readers meet it.",
        "outline": [
          "Use the actual production font",
          "First appearance needs more than a character count",
          "One crowded club roster panel",
          "Choose between shorter reference and larger balloon",
          "Keep script identity separate from lettering"
        ],
        "story": "Fictional example: a club roster panel wraps two surnames into what looks like one person. The letterer changes layout and introduction order while keeping the approved names.",
        "storyAnalysis": "The problem belongs to spatial grouping; a random shorter name would disguise the layout fault and disrupt continuity.",
        "evidence": "Original panel fixtures, actual measured font metrics in phase two and WCAG-derived general accessibility checks; no completed font measurements yet.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/lettering.md",
        "localizedBodies": {
          "en": "content/en/lettering.md",
          "ja": "content/ja/lettering.md"
        }
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Reducing balloon width produces overflow for a deliberately long fixture.",
        "A missing glyph is surfaced, not silently replaced with an empty box.",
        "A minimum font size is honored even when content overflows.",
        "The no-JavaScript example still explains which proof is illustrative.",
        "Narrow fixture flags overflow without silent text shrink",
        "Unbreakable overflow remains visible"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:341",
      "profileSource": "data/profiles.json#manga-production",
      "absorbedModules": [
        {
          "sourceId": "nw-comic-mobile-name-legibility",
          "input": "viewportWidth",
          "rule": "Reflow proof at the requested width rather than rename automatically",
          "output": "Mobile proof and overflow",
          "acceptance": "Narrow fixture flags overflow without silent text shrink",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-speech-balloon-name-wrapping",
          "input": "balloonWidth",
          "rule": "Wrap text within measured or explicitly estimated bounds",
          "output": "Wrapped lines and fit status",
          "acceptance": "Unbreakable overflow remains visible",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "lettering",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "names",
          "label": [
            "Approved text",
            "確認する文字"
          ],
          "type": "textarea",
          "default": "a | Aven Morrow | ay-ven\nb | 空織 | あおり",
          "help": [
            "ID | written form | optional reading. Japanese example reading is explicitly an invented story choice.",
            "ID | 表記 | 読み・任意。日本語例の読みは創作上の設定です。"
          ]
        },
        {
          "key": "width",
          "label": [
            "Balloon inner width · px",
            "枠の内側の幅 · px"
          ],
          "type": "number",
          "default": 120,
          "help": null
        },
        {
          "key": "fontSize",
          "label": [
            "Main text size · px, minimum 12",
            "本文サイズ · px、最小12"
          ],
          "type": "number",
          "default": 22,
          "help": null
        },
        {
          "key": "fontFamily",
          "label": [
            "Local production font",
            "制作に使うローカル書体"
          ],
          "type": "text",
          "default": "Georgia",
          "help": null
        },
        {
          "key": "supportedCharacters",
          "label": [
            "Font coverage manifest · optional",
            "書体の収録文字表・任意"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Paste characters actually verified in the production font. Empty means unverified, not passed.",
            "制作書体で確認した文字を入力。空欄は未検証で、合格ではありません。"
          ]
        },
        {
          "key": "introductions",
          "label": [
            "First public introduction",
            "読者への初紹介"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "character ID | first chapter introduced",
            "人物ID | 初紹介の章"
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Scene chapter",
            "場面の章"
          ],
          "type": "number",
          "default": 1,
          "help": null
        },
        {
          "key": "props",
          "label": [
            "Name-bearing props",
            "名前が入る小道具"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "asset ID | character ID | current artwork text",
            "素材ID | 人物ID | 画像にある現在の文字"
          ]
        }
      ]
    },
    {
      "id": "nw-vertical-comic-name-pacing",
      "slug": "vertical-comic-name-pacing",
      "name": "Vertical comic name pacing",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/vertical-comic-name-pacing/",
        "ja": "/ja/tools/vertical-comic-name-pacing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Schedule first name displays across scrolling episode beats",
      "task": "Schedule first name displays across scrolling episode beats",
      "searchIntent": {
        "primary": "Complete the task: Schedule first name displays across scrolling episode beats",
        "queryHypothesis": "vertical comic name pacing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to schedule first name displays across scrolling episode beats?",
        "When should vertical comic name pacing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Schedule first name displays across scrolling episode beats",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Schedule first name displays across scrolling episode beats. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-school-uniform-name-patch",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Schedule first name displays across scrolling episode beats versus Track prop name changes across character transfers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-author-rebrand-timeline",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Schedule first name displays across scrolling episode beats versus Schedule name changes across a backlist and active series; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-furigana-introduction-plan",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Schedule first name displays across scrolling episode beats versus Schedule reading support at first and later appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Schedule first name displays across scrolling episode beats",
        "outline": [
          "Explain the specific decision: Schedule first name displays across scrolling episode beats",
          "Define the applicable contract and limits for Vertical comic name pacing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Schedule first name displays across scrolling episode beats; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Schedule first name displays across scrolling episode beats",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:342",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-manga-character-name-card",
      "slug": "manga-character-name-card",
      "name": "Manga character name card",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/manga-character-name-card/",
        "ja": "/ja/tools/manga-character-name-card/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Produce identity, reading and role cards for the production team",
      "task": "Produce identity, reading and role cards for the production team",
      "searchIntent": {
        "primary": "Complete the task: Produce identity, reading and role cards for the production team",
        "queryHypothesis": "manga character name card",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce identity, reading and role cards for the production team?",
        "When should manga character name card be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Print is a surface of the approved card artifact"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce identity, reading and role cards for the production team",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings",
        "Print reference with version"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce identity, reading and role cards for the production team. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manga-creator-signature",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Produce identity, reading and role cards for the production team versus Coordinate a pen name with a compact production credit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-occupation-name-separation",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Produce identity, reading and role cards for the production team versus Keep role titles from replacing individual identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-vertical-manga-ruby-crowding",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Produce identity, reading and role cards for the production team versus Review name and reading collisions with adjacent art; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce identity, reading and role cards for the production team",
        "outline": [
          "Explain the specific decision: Produce identity, reading and role cards for the production team",
          "Define the applicable contract and limits for Manga character name card",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce identity, reading and role cards for the production team; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce identity, reading and role cards for the production team",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Printing does not introduce a new identity record"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:343",
      "profileSource": "data/profiles.json#manga-production",
      "absorbedModules": [
        {
          "sourceId": "nw-comic-printable-cast-reference",
          "input": "printProfile",
          "rule": "Print is a surface of the approved card artifact",
          "output": "Print reference with version",
          "acceptance": "Printing does not introduce a new identity record",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-comic-chapter-recap-names",
      "slug": "comic-chapter-recap-names",
      "name": "Comic chapter recap names",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-chapter-recap-names/",
        "ja": "/ja/tools/comic-chapter-recap-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Select spoiler safe short references for returning readers",
      "task": "Select spoiler safe short references for returning readers",
      "searchIntent": {
        "primary": "Complete the task: Select spoiler safe short references for returning readers",
        "queryHypothesis": "comic chapter recap names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to select spoiler safe short references for returning readers?",
        "When should comic chapter recap names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Select spoiler safe short references for returning readers",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Select spoiler safe short references for returning readers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-chapter-title-name-spoiler",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Select spoiler safe short references for returning readers versus Evaluate a title against the reader's current identity knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-recap-alias-continuity",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Select spoiler safe short references for returning readers versus Keep recap wording within current reader knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-motion-comic-recap-audio-names",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Select spoiler safe short references for returning readers versus Reintroduce names without narrating hidden identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Select spoiler safe short references for returning readers",
        "outline": [
          "Explain the specific decision: Select spoiler safe short references for returning readers",
          "Define the applicable contract and limits for Comic chapter recap names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Select spoiler safe short references for returning readers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Select spoiler safe short references for returning readers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:344",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-recap-alias-continuity",
      "slug": "comic-recap-alias-continuity",
      "name": "Comic recap alias continuity",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-recap-alias-continuity/",
        "ja": "/ja/tools/comic-recap-alias-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Keep recap wording within current reader knowledge",
      "task": "Keep recap wording within current reader knowledge",
      "searchIntent": {
        "primary": "Complete the task: Keep recap wording within current reader knowledge",
        "queryHypothesis": "comic recap alias continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep recap wording within current reader knowledge?",
        "When should comic recap alias continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep recap wording within current reader knowledge",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep recap wording within current reader knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-chapter-title-name-spoiler",
          "score": 0.22727272727272727,
          "sharedProfile": true,
          "difference": "Keep recap wording within current reader knowledge versus Evaluate a title against the reader's current identity knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-serial-episode-name-recap",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Keep recap wording within current reader knowledge versus Choose reminder forms from publication gap and reader knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-chapter-recap-names",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Keep recap wording within current reader knowledge versus Select spoiler safe short references for returning readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep recap wording within current reader knowledge",
        "outline": [
          "Explain the specific decision: Keep recap wording within current reader knowledge",
          "Define the applicable contract and limits for Comic recap alias continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep recap wording within current reader knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep recap wording within current reader knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:345",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-vertical-manga-ruby-crowding",
      "slug": "vertical-manga-ruby-crowding",
      "name": "Vertical manga ruby crowding",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/vertical-manga-ruby-crowding/",
        "ja": "/ja/tools/vertical-manga-ruby-crowding/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Review name and reading collisions with adjacent art",
      "task": "Review name and reading collisions with adjacent art",
      "searchIntent": {
        "primary": "Complete the task: Review name and reading collisions with adjacent art",
        "queryHypothesis": "vertical manga ruby crowding",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to review name and reading collisions with adjacent art?",
        "When should vertical manga ruby crowding be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Review name and reading collisions with adjacent art",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Review name and reading collisions with adjacent art. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manga-character-name-card",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Review name and reading collisions with adjacent art versus Produce identity, reading and role cards for the production team; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-ruby-layout",
          "score": 0.0925438596491228,
          "sharedProfile": false,
          "difference": "Review name and reading collisions with adjacent art versus Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-cast-registry",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Review name and reading collisions with adjacent art versus Prevent collisions across sessions and locations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Review name and reading collisions with adjacent art",
        "outline": [
          "Explain the specific decision: Review name and reading collisions with adjacent art",
          "Define the applicable contract and limits for Vertical manga ruby crowding",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Review name and reading collisions with adjacent art; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Review name and reading collisions with adjacent art",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:347",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-sound-effect-name-clash",
      "slug": "comic-sound-effect-name-clash",
      "name": "Comic sound effect name clash",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-sound-effect-name-clash/",
        "ja": "/ja/tools/comic-sound-effect-name-clash/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Flag character names that overlap with recurring effects in a script",
      "task": "Flag character names that overlap with recurring effects in a script",
      "searchIntent": {
        "primary": "Complete the task: Flag character names that overlap with recurring effects in a script",
        "queryHypothesis": "comic sound effect name clash",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag character names that overlap with recurring effects in a script?",
        "When should comic sound effect name clash be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag character names that overlap with recurring effects in a script",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag character names that overlap with recurring effects in a script. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-episodic-name-reintroduction",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Flag character names that overlap with recurring effects in a script versus Reintroduce a recurring character after publication gaps; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.1222222222222222,
          "sharedProfile": true,
          "difference": "Flag character names that overlap with recurring effects in a script versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-gloss-placement",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Flag character names that overlap with recurring effects in a script versus Choose reading notes that preserve panel reading order; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag character names that overlap with recurring effects in a script",
        "outline": [
          "Explain the specific decision: Flag character names that overlap with recurring effects in a script",
          "Define the applicable contract and limits for Comic sound effect name clash",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag character names that overlap with recurring effects in a script; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag character names that overlap with recurring effects in a script",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:348",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-cast-silhouette-labels",
      "slug": "comic-cast-silhouette-labels",
      "name": "Comic cast silhouette labels",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-cast-silhouette-labels/",
        "ja": "/ja/tools/comic-cast-silhouette-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Keep production labels distinct from final in story names",
      "task": "Keep production labels distinct from final in story names",
      "searchIntent": {
        "primary": "Complete the task: Keep production labels distinct from final in story names",
        "queryHypothesis": "comic cast silhouette labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep production labels distinct from final in story names?",
        "When should comic cast silhouette labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep production labels distinct from final in story names",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep production labels distinct from final in story names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.19791666666666666,
          "sharedProfile": true,
          "difference": "Keep production labels distinct from final in story names versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-photo-mode-labels",
          "score": 0.19444444444444442,
          "sharedProfile": false,
          "difference": "Keep production labels distinct from final in story names versus Keep optional labels consistent with story spoiler settings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-apartment-cast-door-labels",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Keep production labels distinct from final in story names versus Match visible labels to residents and concealed occupants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep production labels distinct from final in story names",
        "outline": [
          "Explain the specific decision: Keep production labels distinct from final in story names",
          "Define the applicable contract and limits for Comic cast silhouette labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep production labels distinct from final in story names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep production labels distinct from final in story names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:349",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-colorist-character-keys",
      "slug": "comic-colorist-character-keys",
      "name": "Comic colorist character keys",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-colorist-character-keys/",
        "ja": "/ja/tools/comic-colorist-character-keys/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Map stable IDs to visual references without relying on names alone",
      "task": "Map stable IDs to visual references without relying on names alone",
      "searchIntent": {
        "primary": "Complete the task: Map stable IDs to visual references without relying on names alone",
        "queryHypothesis": "comic colorist character keys",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map stable IDs to visual references without relying on names alone?",
        "When should comic colorist character keys be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map stable IDs to visual references without relying on names alone",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map stable IDs to visual references without relying on names alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-nickname-lettering-contrast",
          "score": 0.22083333333333333,
          "sharedProfile": true,
          "difference": "Map stable IDs to visual references without relying on names alone versus Show an intimate form without relying on color alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-only-identity-introduction",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Map stable IDs to visual references without relying on names alone versus Introduce characters without relying on visual name cards; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-student-council-office-names",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Map stable IDs to visual references without relying on names alone versus Update office references after elections without replacing character IDs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map stable IDs to visual references without relying on names alone",
        "outline": [
          "Explain the specific decision: Map stable IDs to visual references without relying on names alone",
          "Define the applicable contract and limits for Comic colorist character keys",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map stable IDs to visual references without relying on names alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map stable IDs to visual references without relying on names alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:350",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-letterer-handoff-names",
      "slug": "comic-letterer-handoff-names",
      "name": "Comic letterer handoff names",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-letterer-handoff-names/",
        "ja": "/ja/tools/comic-letterer-handoff-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Export approved spellings, pronunciations and forbidden variants",
      "task": "Export approved spellings, pronunciations and forbidden variants",
      "searchIntent": {
        "primary": "Complete the task: Export approved spellings, pronunciations and forbidden variants",
        "queryHypothesis": "comic letterer handoff names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export approved spellings, pronunciations and forbidden variants?",
        "When should comic letterer handoff names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export approved spellings, pronunciations and forbidden variants",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export approved spellings, pronunciations and forbidden variants. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-contributor-name-handoff",
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Export approved spellings, pronunciations and forbidden variants versus Package approved forms and forbidden variants for guest writers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-pronunciation-metadata",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Export approved spellings, pronunciations and forbidden variants versus Export approved pronunciations with dialogue assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Export approved spellings, pronunciations and forbidden variants versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export approved spellings, pronunciations and forbidden variants",
        "outline": [
          "Explain the specific decision: Export approved spellings, pronunciations and forbidden variants",
          "Define the applicable contract and limits for Comic letterer handoff names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export approved spellings, pronunciations and forbidden variants; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export approved spellings, pronunciations and forbidden variants",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:351",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-editor-name-correction-sheet",
      "slug": "comic-editor-name-correction-sheet",
      "name": "Comic editor name correction sheet",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-editor-name-correction-sheet/",
        "ja": "/ja/tools/comic-editor-name-correction-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Track corrections with page and panel references",
      "task": "Track corrections with page and panel references",
      "searchIntent": {
        "primary": "Complete the task: Track corrections with page and panel references",
        "queryHypothesis": "comic editor name correction sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track corrections with page and panel references?",
        "When should comic editor name correction sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track corrections with page and panel references",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track corrections with page and panel references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-correction-dialogue",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Track corrections with page and panel references versus Draft corrections that fit the character and scene stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-gm-secret-identity-sheet",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Track corrections with page and panel references versus Separate private true names from player facing references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-gloss-placement",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Track corrections with page and panel references versus Choose reading notes that preserve panel reading order; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track corrections with page and panel references",
        "outline": [
          "Explain the specific decision: Track corrections with page and panel references",
          "Define the applicable contract and limits for Comic editor name correction sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track corrections with page and panel references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track corrections with page and panel references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:352",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-name-reveal-splash",
      "slug": "comic-name-reveal-splash",
      "name": "Comic name reveal splash",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-name-reveal-splash/",
        "ja": "/ja/tools/comic-name-reveal-splash/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Compare reveal text hierarchy with prior identity clues",
      "task": "Compare reveal text hierarchy with prior identity clues",
      "searchIntent": {
        "primary": "Complete the task: Compare reveal text hierarchy with prior identity clues",
        "queryHypothesis": "comic name reveal splash",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reveal text hierarchy with prior identity clues?",
        "When should comic name reveal splash be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reveal text hierarchy with prior identity clues",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reveal text hierarchy with prior identity clues. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-badge-continuity",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Compare reveal text hierarchy with prior identity clues versus Match art badge text to timeline and identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-motion-comic-name-reveal-timing",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Compare reveal text hierarchy with prior identity clues versus Synchronize audio, captions and visible name props; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-fake-document-name",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare reveal text hierarchy with prior identity clues versus Reconcile a fictional document with cover identity constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reveal text hierarchy with prior identity clues",
        "outline": [
          "Explain the specific decision: Compare reveal text hierarchy with prior identity clues",
          "Define the applicable contract and limits for Comic name reveal splash",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reveal text hierarchy with prior identity clues; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reveal text hierarchy with prior identity clues",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:353",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-masked-speaker-labels",
      "slug": "comic-masked-speaker-labels",
      "name": "Comic masked speaker labels",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-masked-speaker-labels/",
        "ja": "/ja/tools/comic-masked-speaker-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Preserve concealed identity in production and reader facing versions",
      "task": "Preserve concealed identity in production and reader facing versions",
      "searchIntent": {
        "primary": "Complete the task: Preserve concealed identity in production and reader facing versions",
        "queryHypothesis": "comic masked speaker labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve concealed identity in production and reader facing versions?",
        "When should comic masked speaker labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve concealed identity in production and reader facing versions",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve concealed identity in production and reader facing versions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.245,
          "sharedProfile": false,
          "difference": "Preserve concealed identity in production and reader facing versions versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Preserve concealed identity in production and reader facing versions versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-ensemble-spread-labels",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Preserve concealed identity in production and reader facing versions versus Position names on a large cast spread with explicit identity anchors; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve concealed identity in production and reader facing versions",
        "outline": [
          "Explain the specific decision: Preserve concealed identity in production and reader facing versions",
          "Define the applicable contract and limits for Comic masked speaker labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve concealed identity in production and reader facing versions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve concealed identity in production and reader facing versions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:354",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-off-panel-name-reference",
      "slug": "comic-off-panel-name-reference",
      "name": "Comic off panel name reference",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-off-panel-name-reference/",
        "ja": "/ja/tools/comic-off-panel-name-reference/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Maintain clarity when a speaker or listener is unseen",
      "task": "Maintain clarity when a speaker or listener is unseen",
      "searchIntent": {
        "primary": "Complete the task: Maintain clarity when a speaker or listener is unseen",
        "queryHypothesis": "comic off panel name reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain clarity when a speaker or listener is unseen?",
        "When should comic off panel name reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain clarity when a speaker or listener is unseen",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain clarity when a speaker or listener is unseen. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Maintain clarity when a speaker or listener is unseen versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mononym-character-design",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Maintain clarity when a speaker or listener is unseen versus Maintain referential clarity for a character with one public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-locale-fallback-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Maintain clarity when a speaker or listener is unseen versus Define a reviewed fallback when a locale is incomplete; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain clarity when a speaker or listener is unseen",
        "outline": [
          "Explain the specific decision: Maintain clarity when a speaker or listener is unseen",
          "Define the applicable contract and limits for Comic off panel name reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain clarity when a speaker or listener is unseen; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain clarity when a speaker or listener is unseen",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:355",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-identical-character-labels",
      "slug": "comic-identical-character-labels",
      "name": "Comic identical character labels",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-identical-character-labels/",
        "ja": "/ja/tools/comic-identical-character-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Distinguish lookalikes in scripts without leaking to readers",
      "task": "Distinguish lookalikes in scripts without leaking to readers",
      "searchIntent": {
        "primary": "Complete the task: Distinguish lookalikes in scripts without leaking to readers",
        "queryHypothesis": "comic identical character labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish lookalikes in scripts without leaking to readers?",
        "When should comic identical character labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish lookalikes in scripts without leaking to readers",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish lookalikes in scripts without leaking to readers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Distinguish lookalikes in scripts without leaking to readers versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-ensemble-spread-labels",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Distinguish lookalikes in scripts without leaking to readers versus Position names on a large cast spread with explicit identity anchors; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Distinguish lookalikes in scripts without leaking to readers versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish lookalikes in scripts without leaking to readers",
        "outline": [
          "Explain the specific decision: Distinguish lookalikes in scripts without leaking to readers",
          "Define the applicable contract and limits for Comic identical character labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish lookalikes in scripts without leaking to readers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish lookalikes in scripts without leaking to readers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:356",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-background-name-density",
      "slug": "comic-background-name-density",
      "name": "Comic background name density",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-background-name-density/",
        "ja": "/ja/tools/comic-background-name-density/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Decide which names deserve visible labels in crowd scenes",
      "task": "Decide which names deserve visible labels in crowd scenes",
      "searchIntent": {
        "primary": "Complete the task: Decide which names deserve visible labels in crowd scenes",
        "queryHypothesis": "comic background name density",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide which names deserve visible labels in crowd scenes?",
        "When should comic background name density be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide which names deserve visible labels in crowd scenes",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide which names deserve visible labels in crowd scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.26,
          "sharedProfile": false,
          "difference": "Decide which names deserve visible labels in crowd scenes versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Decide which names deserve visible labels in crowd scenes versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Decide which names deserve visible labels in crowd scenes versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide which names deserve visible labels in crowd scenes",
        "outline": [
          "Explain the specific decision: Decide which names deserve visible labels in crowd scenes",
          "Define the applicable contract and limits for Comic background name density",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide which names deserve visible labels in crowd scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide which names deserve visible labels in crowd scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:357",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-school-desk-labels",
      "slug": "comic-school-desk-labels",
      "name": "Comic school desk labels",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-school-desk-labels/",
        "ja": "/ja/tools/comic-school-desk-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Coordinate seat maps, names and classroom scenes",
      "task": "Coordinate seat maps, names and classroom scenes",
      "searchIntent": {
        "primary": "Complete the task: Coordinate seat maps, names and classroom scenes",
        "queryHypothesis": "comic school desk labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate seat maps, names and classroom scenes?",
        "When should comic school desk labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate seat maps, names and classroom scenes",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate seat maps, names and classroom scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-identical-character-labels",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Coordinate seat maps, names and classroom scenes versus Distinguish lookalikes in scripts without leaking to readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sibling-rival-ensemble",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Coordinate seat maps, names and classroom scenes versus Coordinate kinship cues and rival identities across scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-background-name-density",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Coordinate seat maps, names and classroom scenes versus Decide which names deserve visible labels in crowd scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate seat maps, names and classroom scenes",
        "outline": [
          "Explain the specific decision: Coordinate seat maps, names and classroom scenes",
          "Define the applicable contract and limits for Comic school desk labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate seat maps, names and classroom scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate seat maps, names and classroom scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:358",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-tournament-introduction-cards",
      "slug": "comic-tournament-introduction-cards",
      "name": "Comic tournament introduction cards",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-tournament-introduction-cards/",
        "ja": "/ja/tools/comic-tournament-introduction-cards/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Fit name, reading and affiliation to a repeated card layout",
      "task": "Fit name, reading and affiliation to a repeated card layout",
      "searchIntent": {
        "primary": "Complete the task: Fit name, reading and affiliation to a repeated card layout",
        "queryHypothesis": "comic tournament introduction cards",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to fit name, reading and affiliation to a repeated card layout?",
        "When should comic tournament introduction cards be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Fit name, reading and affiliation to a repeated card layout",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Fit name, reading and affiliation to a repeated card layout. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-difficult-name-introduction",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Fit name, reading and affiliation to a repeated card layout versus Compare staged reading support against renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-gloss-placement",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Fit name, reading and affiliation to a repeated card layout versus Choose reading notes that preserve panel reading order; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-furigana-introduction-plan",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Fit name, reading and affiliation to a repeated card layout versus Schedule reading support at first and later appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Fit name, reading and affiliation to a repeated card layout",
        "outline": [
          "Explain the specific decision: Fit name, reading and affiliation to a repeated card layout",
          "Define the applicable contract and limits for Comic tournament introduction cards",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Fit name, reading and affiliation to a repeated card layout; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Fit name, reading and affiliation to a repeated card layout",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:359",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-ensemble-spread-labels",
      "slug": "comic-ensemble-spread-labels",
      "name": "Comic ensemble spread labels",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-ensemble-spread-labels/",
        "ja": "/ja/tools/comic-ensemble-spread-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Position names on a large cast spread with explicit identity anchors",
      "task": "Position names on a large cast spread with explicit identity anchors",
      "searchIntent": {
        "primary": "Complete the task: Position names on a large cast spread with explicit identity anchors",
        "queryHypothesis": "comic ensemble spread labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to position names on a large cast spread with explicit identity anchors?",
        "When should comic ensemble spread labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Position names on a large cast spread with explicit identity anchors",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Position names on a large cast spread with explicit identity anchors. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Position names on a large cast spread with explicit identity anchors versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-identical-character-labels",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Position names on a large cast spread with explicit identity anchors versus Distinguish lookalikes in scripts without leaking to readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Position names on a large cast spread with explicit identity anchors versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Position names on a large cast spread with explicit identity anchors",
        "outline": [
          "Explain the specific decision: Position names on a large cast spread with explicit identity anchors",
          "Define the applicable contract and limits for Comic ensemble spread labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Position names on a large cast spread with explicit identity anchors; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Position names on a large cast spread with explicit identity anchors",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:360",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-relationship-diagram-names",
      "slug": "comic-relationship-diagram-names",
      "name": "Comic relationship diagram names",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-relationship-diagram-names/",
        "ja": "/ja/tools/comic-relationship-diagram-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Use compact forms that remain unambiguous in a relationship chart",
      "task": "Use compact forms that remain unambiguous in a relationship chart",
      "searchIntent": {
        "primary": "Complete the task: Use compact forms that remain unambiguous in a relationship chart",
        "queryHypothesis": "comic relationship diagram names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to use compact forms that remain unambiguous in a relationship chart?",
        "When should comic relationship diagram names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Use compact forms that remain unambiguous in a relationship chart",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Use compact forms that remain unambiguous in a relationship chart. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-gloss-placement",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Use compact forms that remain unambiguous in a relationship chart versus Choose reading notes that preserve panel reading order; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Use compact forms that remain unambiguous in a relationship chart versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Use compact forms that remain unambiguous in a relationship chart versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Use compact forms that remain unambiguous in a relationship chart",
        "outline": [
          "Explain the specific decision: Use compact forms that remain unambiguous in a relationship chart",
          "Define the applicable contract and limits for Comic relationship diagram names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Use compact forms that remain unambiguous in a relationship chart; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Use compact forms that remain unambiguous in a relationship chart",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:361",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-volume-cast-page",
      "slug": "comic-volume-cast-page",
      "name": "Comic volume cast page",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-volume-cast-page/",
        "ja": "/ja/tools/comic-volume-cast-page/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Generate spoiler bounded entries by volume",
      "task": "Generate spoiler bounded entries by volume",
      "searchIntent": {
        "primary": "Complete the task: Generate spoiler bounded entries by volume",
        "queryHypothesis": "comic volume cast page",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate spoiler bounded entries by volume?",
        "When should comic volume cast page be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate spoiler bounded entries by volume",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate spoiler bounded entries by volume. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-chapter-recap-names",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Generate spoiler bounded entries by volume versus Select spoiler safe short references for returning readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Generate spoiler bounded entries by volume versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Generate spoiler bounded entries by volume versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate spoiler bounded entries by volume",
        "outline": [
          "Explain the specific decision: Generate spoiler bounded entries by volume",
          "Define the applicable contract and limits for Comic volume cast page",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate spoiler bounded entries by volume; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate spoiler bounded entries by volume",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:362",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-cover-character-credit",
      "slug": "comic-cover-character-credit",
      "name": "Comic cover character credit",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-cover-character-credit/",
        "ja": "/ja/tools/comic-cover-character-credit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Separate character names from creator and actor credits",
      "task": "Separate character names from creator and actor credits",
      "searchIntent": {
        "primary": "Complete the task: Separate character names from creator and actor credits",
        "queryHypothesis": "comic cover character credit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate character names from creator and actor credits?",
        "When should comic cover character credit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate character names from creator and actor credits",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate character names from creator and actor credits. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Separate character names from creator and actor credits versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-combat-log-actor-clarity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate character names from creator and actor credits versus Keep similar actor names distinguishable in fast logs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate character names from creator and actor credits versus Store approved kana and romanized credits alongside the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate character names from creator and actor credits",
        "outline": [
          "Explain the specific decision: Separate character names from creator and actor credits",
          "Define the applicable contract and limits for Comic cover character credit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate character names from creator and actor credits; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate character names from creator and actor credits",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:363",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-chapter-title-name-spoiler",
      "slug": "comic-chapter-title-name-spoiler",
      "name": "Comic chapter title name spoiler",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-chapter-title-name-spoiler/",
        "ja": "/ja/tools/comic-chapter-title-name-spoiler/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Evaluate a title against the reader's current identity knowledge",
      "task": "Evaluate a title against the reader's current identity knowledge",
      "searchIntent": {
        "primary": "Complete the task: Evaluate a title against the reader's current identity knowledge",
        "queryHypothesis": "comic chapter title name spoiler",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to evaluate a title against the reader's current identity knowledge?",
        "When should comic chapter title name spoiler be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Evaluate a title against the reader's current identity knowledge",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Evaluate a title against the reader's current identity knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.22727272727272727,
          "sharedProfile": false,
          "difference": "Evaluate a title against the reader's current identity knowledge versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-recap-alias-continuity",
          "score": 0.22727272727272727,
          "sharedProfile": true,
          "difference": "Evaluate a title against the reader's current identity knowledge versus Keep recap wording within current reader knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Evaluate a title against the reader's current identity knowledge versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Evaluate a title against the reader's current identity knowledge",
        "outline": [
          "Explain the specific decision: Evaluate a title against the reader's current identity knowledge",
          "Define the applicable contract and limits for Comic chapter title name spoiler",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Evaluate a title against the reader's current identity knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Evaluate a title against the reader's current identity knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:364",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-handwritten-note-clue",
      "slug": "comic-handwritten-note-clue",
      "name": "Comic handwritten note clue",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-handwritten-note-clue/",
        "ja": "/ja/tools/comic-handwritten-note-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Make a name based clue visible and linguistically reviewed",
      "task": "Make a name based clue visible and linguistically reviewed",
      "searchIntent": {
        "primary": "Complete the task: Make a name based clue visible and linguistically reviewed",
        "queryHypothesis": "comic handwritten note clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make a name based clue visible and linguistically reviewed?",
        "When should comic handwritten note clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make a name based clue visible and linguistically reviewed",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make a name based clue visible and linguistically reviewed. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-handwritten-name-ambiguity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Make a name based clue visible and linguistically reviewed versus Define visible alternatives with an actual prop example; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wrong-honorific-clue",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Make a name based clue visible and linguistically reviewed versus Ground the clue in an established in story convention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-letter-salutation-clue",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Make a name based clue visible and linguistically reviewed versus Make an address form reveal a specific relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make a name based clue visible and linguistically reviewed",
        "outline": [
          "Explain the specific decision: Make a name based clue visible and linguistically reviewed",
          "Define the applicable contract and limits for Comic handwritten note clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make a name based clue visible and linguistically reviewed; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make a name based clue visible and linguistically reviewed",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:365",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-name-badge-continuity",
      "slug": "comic-name-badge-continuity",
      "name": "Comic name badge continuity",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-name-badge-continuity/",
        "ja": "/ja/tools/comic-name-badge-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Match art badge text to timeline and identity state",
      "task": "Match art badge text to timeline and identity state",
      "searchIntent": {
        "primary": "Complete the task: Match art badge text to timeline and identity state",
        "queryHypothesis": "comic name badge continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match art badge text to timeline and identity state?",
        "When should comic name badge continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Match art badge text to timeline and identity state",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Match art badge text to timeline and identity state. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-reveal-splash",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Match art badge text to timeline and identity state versus Compare reveal text hierarchy with prior identity clues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-swarm-character-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Match art badge text to timeline and identity state versus Preserve identity when constituent members change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-recap-alias-continuity",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Match art badge text to timeline and identity state versus Keep recap wording within current reader knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Match art badge text to timeline and identity state",
        "outline": [
          "Explain the specific decision: Match art badge text to timeline and identity state",
          "Define the applicable contract and limits for Comic name badge continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Match art badge text to timeline and identity state; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Match art badge text to timeline and identity state",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:366",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-school-uniform-name-patch",
      "slug": "comic-school-uniform-name-patch",
      "name": "Comic school uniform name patch",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-school-uniform-name-patch/",
        "ja": "/ja/tools/comic-school-uniform-name-patch/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Track prop name changes across character transfers",
      "task": "Track prop name changes across character transfers",
      "searchIntent": {
        "primary": "Complete the task: Track prop name changes across character transfers",
        "queryHypothesis": "comic school uniform name patch",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track prop name changes across character transfers?",
        "When should comic school uniform name patch be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track prop name changes across character transfers",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track prop name changes across character transfers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-author-rebrand-timeline",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track prop name changes across character transfers versus Schedule name changes across a backlist and active series; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track prop name changes across character transfers versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-vertical-comic-name-pacing",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Track prop name changes across character transfers versus Schedule first name displays across scrolling episode beats; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track prop name changes across character transfers",
        "outline": [
          "Explain the specific decision: Track prop name changes across character transfers",
          "Define the applicable contract and limits for Comic school uniform name patch",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track prop name changes across character transfers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track prop name changes across character transfers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:367",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-fake-document-name",
      "slug": "comic-fake-document-name",
      "name": "Comic fake document name",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-fake-document-name/",
        "ja": "/ja/tools/comic-fake-document-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Reconcile a fictional document with cover identity constraints",
      "task": "Reconcile a fictional document with cover identity constraints",
      "searchIntent": {
        "primary": "Complete the task: Reconcile a fictional document with cover identity constraints",
        "queryHypothesis": "comic fake document name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile a fictional document with cover identity constraints?",
        "When should comic fake document name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile a fictional document with cover identity constraints",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile a fictional document with cover identity constraints. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dub-name-length-tradeoff",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile a fictional document with cover identity constraints versus Compare lip timing constraints with identity continuity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undercover-relationship-address",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile a fictional document with cover identity constraints versus Keep intimate speech from contradicting a cover identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-quest-marker-name-labels",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile a fictional document with cover identity constraints versus Preserve discovered identity under map space constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile a fictional document with cover identity constraints",
        "outline": [
          "Explain the specific decision: Reconcile a fictional document with cover identity constraints",
          "Define the applicable contract and limits for Comic fake document name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile a fictional document with cover identity constraints; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile a fictional document with cover identity constraints",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:368",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-translated-redraw-name",
      "slug": "comic-translated-redraw-name",
      "name": "Comic translated redraw name",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-translated-redraw-name/",
        "ja": "/ja/tools/comic-translated-redraw-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "List art edits required by a localization decision",
      "task": "List art edits required by a localization decision",
      "searchIntent": {
        "primary": "Complete the task: List art edits required by a localization decision",
        "queryHypothesis": "comic translated redraw name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to list art edits required by a localization decision?",
        "When should comic translated redraw name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: List art edits required by a localization decision",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: List art edits required by a localization decision. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-badge-continuity",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "List art edits required by a localization decision versus Match art badge text to timeline and identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-change-impact",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "List art edits required by a localization decision versus Trace edits through dialogue, art props and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-revision-prop-checklist",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "List art edits required by a localization decision versus Trace a rename through signs, letters and background art; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "List art edits required by a localization decision",
        "outline": [
          "Explain the specific decision: List art edits required by a localization decision",
          "Define the applicable contract and limits for Comic translated redraw name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for List art edits required by a localization decision; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: List art edits required by a localization decision",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:369",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-social-preview-name-card",
      "slug": "comic-social-preview-name-card",
      "name": "Comic social preview name card",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-social-preview-name-card/",
        "ja": "/ja/tools/comic-social-preview-name-card/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Avoid spoilers when extracting a character introduction for promotion",
      "task": "Avoid spoilers when extracting a character introduction for promotion",
      "searchIntent": {
        "primary": "Complete the task: Avoid spoilers when extracting a character introduction for promotion",
        "queryHypothesis": "comic social preview name card",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid spoilers when extracting a character introduction for promotion?",
        "When should comic social preview name card be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid spoilers when extracting a character introduction for promotion",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid spoilers when extracting a character introduction for promotion. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-off-panel-name-reference",
          "score": 0.10416666666666666,
          "sharedProfile": true,
          "difference": "Avoid spoilers when extracting a character introduction for promotion versus Maintain clarity when a speaker or listener is unseen; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-social-register-naming",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Avoid spoilers when extracting a character introduction for promotion versus Compare public formality with private address without stereotyping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manga-character-name-card",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Avoid spoilers when extracting a character introduction for promotion versus Produce identity, reading and role cards for the production team; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid spoilers when extracting a character introduction for promotion",
        "outline": [
          "Explain the specific decision: Avoid spoilers when extracting a character introduction for promotion",
          "Define the applicable contract and limits for Comic social preview name card",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid spoilers when extracting a character introduction for promotion; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid spoilers when extracting a character introduction for promotion",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:371",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-episodic-name-reintroduction",
      "slug": "comic-episodic-name-reintroduction",
      "name": "Comic episodic name reintroduction",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-episodic-name-reintroduction/",
        "ja": "/ja/tools/comic-episodic-name-reintroduction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Reintroduce a recurring character after publication gaps",
      "task": "Reintroduce a recurring character after publication gaps",
      "searchIntent": {
        "primary": "Complete the task: Reintroduce a recurring character after publication gaps",
        "queryHypothesis": "comic episodic name reintroduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reintroduce a recurring character after publication gaps?",
        "When should comic episodic name reintroduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reintroduce a recurring character after publication gaps",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reintroduce a recurring character after publication gaps. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-departure-return-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reintroduce a recurring character after publication gaps versus Reintroduce a returning character after a long narrative absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-motion-comic-recap-audio-names",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Reintroduce a recurring character after publication gaps versus Reintroduce names without narrating hidden identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-sound-effect-name-clash",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Reintroduce a recurring character after publication gaps versus Flag character names that overlap with recurring effects in a script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reintroduce a recurring character after publication gaps",
        "outline": [
          "Explain the specific decision: Reintroduce a recurring character after publication gaps",
          "Define the applicable contract and limits for Comic episodic name reintroduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reintroduce a recurring character after publication gaps; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reintroduce a recurring character after publication gaps",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:372",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-revision-prop-checklist",
      "slug": "comic-revision-prop-checklist",
      "name": "Comic revision prop checklist",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-revision-prop-checklist/",
        "ja": "/ja/tools/comic-revision-prop-checklist/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Trace a rename through signs, letters and background art",
      "task": "Trace a rename through signs, letters and background art",
      "searchIntent": {
        "primary": "Complete the task: Trace a rename through signs, letters and background art",
        "queryHypothesis": "comic revision prop checklist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace a rename through signs, letters and background art?",
        "When should comic revision prop checklist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace a rename through signs, letters and background art",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace a rename through signs, letters and background art. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Trace a rename through signs, letters and background art versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-change-impact",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace a rename through signs, letters and background art versus Trace edits through dialogue, art props and credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Trace a rename through signs, letters and background art versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace a rename through signs, letters and background art",
        "outline": [
          "Explain the specific decision: Trace a rename through signs, letters and background art",
          "Define the applicable contract and limits for Comic revision prop checklist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace a rename through signs, letters and background art; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace a rename through signs, letters and background art",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:373",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-script-cast-synchronization",
      "slug": "comic-script-cast-synchronization",
      "name": "Comic script cast synchronization",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-script-cast-synchronization/",
        "ja": "/ja/tools/comic-script-cast-synchronization/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Compare script labels with the approved cast bible",
      "task": "Compare script labels with the approved cast bible",
      "searchIntent": {
        "primary": "Complete the task: Compare script labels with the approved cast bible",
        "queryHypothesis": "comic script cast synchronization",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare script labels with the approved cast bible?",
        "When should comic script cast synchronization be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare script labels with the approved cast bible",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare script labels with the approved cast bible. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.19791666666666666,
          "sharedProfile": true,
          "difference": "Compare script labels with the approved cast bible versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-dialogue-tag-rename",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Compare script labels with the approved cast bible versus Distinguish script labels from spoken name text; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.14285714285714285,
          "sharedProfile": true,
          "difference": "Compare script labels with the approved cast bible versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare script labels with the approved cast bible",
        "outline": [
          "Explain the specific decision: Compare script labels with the approved cast bible",
          "Define the applicable contract and limits for Comic script cast synchronization",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare script labels with the approved cast bible; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare script labels with the approved cast bible",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:374",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-title-versus-name-caption",
      "slug": "comic-title-versus-name-caption",
      "name": "Comic title versus name caption",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-title-versus-name-caption/",
        "ja": "/ja/tools/comic-title-versus-name-caption/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Distinguish role labels from a character's actual name",
      "task": "Distinguish role labels from a character's actual name",
      "searchIntent": {
        "primary": "Complete the task: Distinguish role labels from a character's actual name",
        "queryHypothesis": "comic title versus name caption",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish role labels from a character's actual name?",
        "When should comic title versus name caption be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish role labels from a character's actual name",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish role labels from a character's actual name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.24404761904761904,
          "sharedProfile": false,
          "difference": "Distinguish role labels from a character's actual name versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prophecy-title-spoiler",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Distinguish role labels from a character's actual name versus Avoid exposing the future role in early character labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish role labels from a character's actual name versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish role labels from a character's actual name",
        "outline": [
          "Explain the specific decision: Distinguish role labels from a character's actual name",
          "Define the applicable contract and limits for Comic title versus name caption",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish role labels from a character's actual name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish role labels from a character's actual name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:375",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-nickname-lettering-contrast",
      "slug": "comic-nickname-lettering-contrast",
      "name": "Comic nickname lettering contrast",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-nickname-lettering-contrast/",
        "ja": "/ja/tools/comic-nickname-lettering-contrast/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Show an intimate form without relying on color alone",
      "task": "Show an intimate form without relying on color alone",
      "searchIntent": {
        "primary": "Complete the task: Show an intimate form without relying on color alone",
        "queryHypothesis": "comic nickname lettering contrast",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show an intimate form without relying on color alone?",
        "When should comic nickname lettering contrast be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show an intimate form without relying on color alone",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show an intimate form without relying on color alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-colorist-character-keys",
          "score": 0.22083333333333333,
          "sharedProfile": true,
          "difference": "Show an intimate form without relying on color alone versus Map stable IDs to visual references without relying on names alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-only-identity-introduction",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Show an intimate form without relying on color alone versus Introduce characters without relying on visual name cards; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-identical-character-labels",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Show an intimate form without relying on color alone versus Distinguish lookalikes in scripts without leaking to readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show an intimate form without relying on color alone",
        "outline": [
          "Explain the specific decision: Show an intimate form without relying on color alone",
          "Define the applicable contract and limits for Comic nickname lettering contrast",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show an intimate form without relying on color alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show an intimate form without relying on color alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:376",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-comic-name-gloss-placement",
      "slug": "comic-name-gloss-placement",
      "name": "Comic name gloss placement",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-name-gloss-placement/",
        "ja": "/ja/tools/comic-name-gloss-placement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Choose reading notes that preserve panel reading order",
      "task": "Choose reading notes that preserve panel reading order",
      "searchIntent": {
        "primary": "Complete the task: Choose reading notes that preserve panel reading order",
        "queryHypothesis": "comic name gloss placement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to choose reading notes that preserve panel reading order?",
        "When should comic name gloss placement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Choose reading notes that preserve panel reading order",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Choose reading notes that preserve panel reading order. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-pronunciation-handoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Choose reading notes that preserve panel reading order versus Export approved reading notes with uncertainty markers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-editor-name-correction-sheet",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Choose reading notes that preserve panel reading order versus Track corrections with page and panel references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-relationship-diagram-names",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Choose reading notes that preserve panel reading order versus Use compact forms that remain unambiguous in a relationship chart; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Choose reading notes that preserve panel reading order",
        "outline": [
          "Explain the specific decision: Choose reading notes that preserve panel reading order",
          "Define the applicable contract and limits for Comic name gloss placement",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Choose reading notes that preserve panel reading order; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Choose reading notes that preserve panel reading order",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:377",
      "profileSource": "data/profiles.json#manga-production"
    },
    {
      "id": "nw-motion-comic-spoken-cast-separation",
      "slug": "motion-comic-spoken-cast-separation",
      "name": "Motion comic spoken cast separation",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/motion-comic-spoken-cast-separation/",
        "ja": "/ja/tools/motion-comic-spoken-cast-separation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Compare approved pronunciations under rapid dialogue",
      "task": "Compare approved pronunciations under rapid dialogue",
      "searchIntent": {
        "primary": "Complete the task: Compare approved pronunciations under rapid dialogue",
        "queryHypothesis": "motion comic spoken cast separation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare approved pronunciations under rapid dialogue?",
        "When should motion comic spoken cast separation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "pronunciations",
          "use": "Creator-approved readings with uncertainty markers."
        },
        {
          "key": "recordings",
          "use": "Optional consented rehearsal clips for real timing and listening tests."
        },
        {
          "key": "sceneSequence",
          "use": "Establish who speaks and which identities the listener knows."
        },
        {
          "key": "cuePolicy",
          "use": "Distinguish actor cue labels from audible names."
        }
      ],
      "rules": [
        "Do not report measured intelligibility without an actual listener test.",
        "Mark unrecorded duration estimates as estimates.",
        "Sound warnings require confirmed readings or explicit human observations.",
        "Audio cue names may reveal private identity to the team but not subtitles.",
        "Label kana-derived duration as an estimate",
        "A delivery condition changes rehearsal context, not legal identity",
        "Keep performance observations attributed to the tested clip"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Do not report measured intelligibility without an actual listener test.",
        "Mark unrecorded duration estimates as estimates.",
        "Sound warnings require confirmed readings or explicit human observations.",
        "Audio cue names may reveal private identity to the team but not subtitles.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "approved pronunciation sheet",
        "spoken form collision candidates",
        "timing estimate or measured clip duration",
        "production-only and audience label variants",
        "Estimate with assumptions",
        "Listening worksheet",
        "Rehearsal note"
      ],
      "capabilities": [
        "Compare a rapid exchange using full and approved short forms.",
        "Export performer and audience sheets from different knowledge scopes."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The decision uses approved spoken forms, timing and listener exposure; written edit distance alone cannot establish audio clarity.",
        "proposedDifferenceAxes": [
          "data",
          "inputs",
          "evaluation",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-pronunciation-metadata",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Compare approved pronunciations under rapid dialogue versus Export approved pronunciations with dialogue assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-letterer-handoff-names",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Compare approved pronunciations under rapid dialogue versus Export approved spellings, pronunciations and forbidden variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rebel-cell-identity-separation",
          "score": 0.10875,
          "sharedProfile": false,
          "difference": "Compare approved pronunciations under rapid dialogue versus Avoid accidental leakage between cells in story dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "The name readers distinguish on a page may merge in performance.",
        "outline": [
          "Start with approved readings",
          "A rehearsal observation is not a universal listener score",
          "A warehouse exchange with two similar short forms",
          "Choose a spoken reference before renaming a character",
          "Make the performer handoff spoiler aware"
        ],
        "story": "Fictional example: a courier hears two short names over a warehouse intercom and delivers a harmless stage prop to the wrong rehearsal room. The production tests surname references using actual rehearsal clips.",
        "storyAnalysis": "The revised line changes audible distinction. The page spelling remains the same, so the example demonstrates the limit of visual-only audits.",
        "evidence": "Original cue-state fixtures; real audio and listener results are not yet available and must not be fabricated.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/audio.md",
        "localizedBodies": {
          "en": "content/en/audio.md",
          "ja": "content/ja/audio.md"
        }
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "No recordings produces no measured audio test result.",
        "A hidden true name is absent from audience subtitle exports.",
        "Removing pronunciation approval marks phonetic comparison unavailable.",
        "Changing clip duration updates the timing report independently of name generation.",
        "No recording means no measured duration claim",
        "No listener data produces no clarity percentage",
        "Changing condition does not create an invented measurement"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:381",
      "profileSource": "data/profiles.json#audio-drama",
      "absorbedModules": [
        {
          "sourceId": "nw-japanese-name-mora-timing",
          "input": "confirmedKana; timingModel",
          "rule": "Label kana-derived duration as an estimate",
          "output": "Estimate with assumptions",
          "acceptance": "No recording means no measured duration claim",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-whispered-name-scene",
          "input": "performanceCondition=whisper",
          "rule": "A delivery condition changes rehearsal context, not legal identity",
          "output": "Listening worksheet",
          "acceptance": "No listener data produces no clarity percentage",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-shouted-name-action-scene",
          "input": "performanceCondition=shout",
          "rule": "Keep performance observations attributed to the tested clip",
          "output": "Rehearsal note",
          "acceptance": "Changing condition does not create an invented measurement",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "audio",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "names",
          "label": [
            "Cast pronunciation notes",
            "人物の読みと時間"
          ],
          "type": "textarea",
          "default": "a | Aven | ay-ven | 0.8\nb | Arden | ar-den | 0.9\nc | Sela | |",
          "help": [
            "ID | display name | approved pronunciation | reported seconds, optional. No audio recognition or intelligibility measurement.",
            "ID | 表示名 | 確認済みの読み | 入力した秒数・任意。音声認識や聞き取りやすさの測定は行いません。"
          ]
        },
        {
          "key": "budget",
          "label": [
            "Name-call duration budget · seconds",
            "名前を呼ぶ時間の目安 · 秒"
          ],
          "type": "number",
          "default": 1,
          "help": null
        },
        {
          "key": "outputScope",
          "label": [
            "Export audience",
            "資料を渡す相手"
          ],
          "type": "select",
          "default": "audience",
          "help": null,
          "options": [
            [
              "audience",
              [
                "Audience-safe",
                "観客向け"
              ]
            ],
            [
              "production",
              [
                "Private production team",
                "非公開の制作チーム"
              ]
            ]
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Audience chapter",
            "観客が到達した章"
          ],
          "type": "number",
          "default": 1,
          "help": null
        },
        {
          "key": "secretNames",
          "label": [
            "Private identity cue layers",
            "正体を含む非公開キュー"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "character ID | private cue name | reveal chapter",
            "人物ID | 非公開のキュー名 | 開示章"
          ]
        },
        {
          "key": "alternativeForms",
          "label": [
            "Full and short rehearsal forms",
            "フルネームと短称のリハーサル"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "character ID | approved full spoken form | approved short spoken form",
            "人物ID | 確認済みのフルネーム | 確認済みの短称"
          ]
        },
        {
          "key": "clipCharacterId",
          "label": [
            "Local clip belongs to ID",
            "ローカル音声の人物ID"
          ],
          "type": "text",
          "default": "a",
          "help": null
        },
        {
          "key": "performanceCondition",
          "label": [
            "Rehearsal delivery condition",
            "リハーサルの発声条件"
          ],
          "type": "select",
          "default": "neutral",
          "help": null,
          "options": [
            [
              "neutral",
              [
                "Ordinary delivery",
                "通常"
              ]
            ],
            [
              "whisper",
              [
                "Whisper",
                "ささやき"
              ]
            ],
            [
              "shout",
              [
                "Shout",
                "叫び"
              ]
            ]
          ]
        },
        {
          "key": "moraRate",
          "label": [
            "Illustrative kana units per second",
            "仮の仮名単位数・毎秒"
          ],
          "type": "number",
          "default": 5,
          "help": null
        },
        {
          "key": "listeningNotes",
          "label": [
            "Actual listening observations",
            "実際の聞き取りの観察"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "character ID | clip or session label | observation. No invented listening scores.",
            "人物ID | 録音や回のラベル | 観察内容。聞き取り点数は捏造しません。"
          ]
        }
      ]
    },
    {
      "id": "nw-voice-cast-name-pronunciation-sheet",
      "slug": "voice-cast-name-pronunciation-sheet",
      "name": "Voice cast name pronunciation sheet",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/voice-cast-name-pronunciation-sheet/",
        "ja": "/ja/tools/voice-cast-name-pronunciation-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Package author readings and uncertainty for performers",
      "task": "Package author readings and uncertainty for performers",
      "searchIntent": {
        "primary": "Complete the task: Package author readings and uncertainty for performers",
        "queryHypothesis": "voice cast name pronunciation sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package author readings and uncertainty for performers?",
        "When should voice cast name pronunciation sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Store explicit author pronunciation metadata"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package author readings and uncertainty for performers",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes",
        "Performer pronunciation note"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package author readings and uncertainty for performers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-voice-director-alias-sheet",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Package author readings and uncertainty for performers versus Tell performers which identity a speaker believes they are addressing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Package author readings and uncertainty for performers versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Package author readings and uncertainty for performers versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package author readings and uncertainty for performers",
        "outline": [
          "Explain the specific decision: Package author readings and uncertainty for performers",
          "Define the applicable contract and limits for Voice cast name pronunciation sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package author readings and uncertainty for performers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package author readings and uncertainty for performers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Missing stress stays unknown"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:382",
      "profileSource": "data/profiles.json#audio-drama",
      "absorbedModules": [
        {
          "sourceId": "nw-english-name-stress-brief",
          "input": "approvedStress",
          "rule": "Store explicit author pronunciation metadata",
          "output": "Performer pronunciation note",
          "acceptance": "Missing stress stays unknown",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-character-cue-name-system",
      "slug": "character-cue-name-system",
      "name": "Character cue name system",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/character-cue-name-system/",
        "ja": "/ja/tools/character-cue-name-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Keep production cues distinct from spoken identities",
      "task": "Keep production cues distinct from spoken identities",
      "searchIntent": {
        "primary": "Complete the task: Keep production cues distinct from spoken identities",
        "queryHypothesis": "character cue name system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep production cues distinct from spoken identities?",
        "When should character cue name system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep production cues distinct from spoken identities",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep production cues distinct from spoken identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-passes-on-title",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep production cues distinct from spoken identities versus Preserve the outgoing and incoming holders' distinct identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep production cues distinct from spoken identities versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep production cues distinct from spoken identities versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep production cues distinct from spoken identities",
        "outline": [
          "Explain the specific decision: Keep production cues distinct from spoken identities",
          "Define the applicable contract and limits for Character cue name system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep production cues distinct from spoken identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep production cues distinct from spoken identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:383",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-subtitle-speaker-name-fit",
      "slug": "subtitle-speaker-name-fit",
      "name": "Subtitle speaker name fit",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/subtitle-speaker-name-fit/",
        "ja": "/ja/tools/subtitle-speaker-name-fit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Test names in speaker labels at supplied subtitle widths",
      "task": "Test names in speaker labels at supplied subtitle widths",
      "searchIntent": {
        "primary": "Complete the task: Test names in speaker labels at supplied subtitle widths",
        "queryHypothesis": "subtitle speaker name fit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test names in speaker labels at supplied subtitle widths?",
        "When should subtitle speaker name fit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test names in speaker labels at supplied subtitle widths",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test names in speaker labels at supplied subtitle widths. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Test names in speaker labels at supplied subtitle widths versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-audio-subtitle-identity",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Test names in speaker labels at supplied subtitle widths versus Align spoken names with subtitle display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-body-swap-name-tracking",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test names in speaker labels at supplied subtitle widths versus Resolve speaker labels against mind and body state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test names in speaker labels at supplied subtitle widths",
        "outline": [
          "Explain the specific decision: Test names in speaker labels at supplied subtitle widths",
          "Define the applicable contract and limits for Subtitle speaker name fit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test names in speaker labels at supplied subtitle widths; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test names in speaker labels at supplied subtitle widths",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:384",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-audio-only-identity-introduction",
      "slug": "audio-only-identity-introduction",
      "name": "Audio only identity introduction",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/audio-only-identity-introduction/",
        "ja": "/ja/tools/audio-only-identity-introduction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Introduce characters without relying on visual name cards",
      "task": "Introduce characters without relying on visual name cards",
      "searchIntent": {
        "primary": "Complete the task: Introduce characters without relying on visual name cards",
        "queryHypothesis": "audio only identity introduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to introduce characters without relying on visual name cards?",
        "When should audio only identity introduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Introduce characters without relying on visual name cards",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Introduce characters without relying on visual name cards. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-colorist-character-keys",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Introduce characters without relying on visual name cards versus Map stable IDs to visual references without relying on names alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-audio-introduction",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Introduce characters without relying on visual name cards versus Test host introductions and spoken acknowledgments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-nickname-lettering-contrast",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Introduce characters without relying on visual name cards versus Show an intimate form without relying on color alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Introduce characters without relying on visual name cards",
        "outline": [
          "Explain the specific decision: Introduce characters without relying on visual name cards",
          "Define the applicable contract and limits for Audio only identity introduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Introduce characters without relying on visual name cards; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Introduce characters without relying on visual name cards",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:385",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-radio-call-name-differentiation",
      "slug": "radio-call-name-differentiation",
      "name": "Radio call name differentiation",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/radio-call-name-differentiation/",
        "ja": "/ja/tools/radio-call-name-differentiation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Check names under author supplied noisy audio examples",
      "task": "Check names under author supplied noisy audio examples",
      "searchIntent": {
        "primary": "Complete the task: Check names under author supplied noisy audio examples",
        "queryHypothesis": "radio call name differentiation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check names under author supplied noisy audio examples?",
        "When should radio call name differentiation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check names under author supplied noisy audio examples",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check names under author supplied noisy audio examples. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-expedition-party-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Check names under author supplied noisy audio examples versus Differentiate voice calls under noisy travel scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-motion-comic-spoken-cast-separation",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Check names under author supplied noisy audio examples versus Compare approved pronunciations under rapid dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clone-identity-differentiation",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Check names under author supplied noisy audio examples versus Assign legal, personal and laboratory identities to cloned characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check names under author supplied noisy audio examples",
        "outline": [
          "Explain the specific decision: Check names under author supplied noisy audio examples",
          "Define the applicable contract and limits for Radio call name differentiation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check names under author supplied noisy audio examples; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check names under author supplied noisy audio examples",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:386",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-motion-comic-name-reveal-timing",
      "slug": "motion-comic-name-reveal-timing",
      "name": "Motion comic name reveal timing",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/motion-comic-name-reveal-timing/",
        "ja": "/ja/tools/motion-comic-name-reveal-timing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Synchronize audio, captions and visible name props",
      "task": "Synchronize audio, captions and visible name props",
      "searchIntent": {
        "primary": "Complete the task: Synchronize audio, captions and visible name props",
        "queryHypothesis": "motion comic name reveal timing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to synchronize audio, captions and visible name props?",
        "When should motion comic name reveal timing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Synchronize audio, captions and visible name props",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Synchronize audio, captions and visible name props. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Synchronize audio, captions and visible name props versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-reveal-splash",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Synchronize audio, captions and visible name props versus Compare reveal text hierarchy with prior identity clues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-background-name-density",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Synchronize audio, captions and visible name props versus Decide which names deserve visible labels in crowd scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Synchronize audio, captions and visible name props",
        "outline": [
          "Explain the specific decision: Synchronize audio, captions and visible name props",
          "Define the applicable contract and limits for Motion comic name reveal timing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Synchronize audio, captions and visible name props; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Synchronize audio, captions and visible name props",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:387",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-actor-character-credit-mapping",
      "slug": "actor-character-credit-mapping",
      "name": "Actor character credit mapping",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/actor-character-credit-mapping/",
        "ja": "/ja/tools/actor-character-credit-mapping/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Prevent performer names from being confused with character aliases",
      "task": "Prevent performer names from being confused with character aliases",
      "searchIntent": {
        "primary": "Complete the task: Prevent performer names from being confused with character aliases",
        "queryHypothesis": "actor character credit mapping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent performer names from being confused with character aliases?",
        "When should actor character credit mapping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent performer names from being confused with character aliases",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent performer names from being confused with character aliases. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-guest-character-names",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Prevent performer names from being confused with character aliases versus Prevent conflict with archived recurring characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stage-character-performance-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Prevent performer names from being confused with character aliases versus Separate a fictional performer from the role they play; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-cast-registry",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Prevent performer names from being confused with character aliases versus Prevent collisions across sessions and locations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent performer names from being confused with character aliases",
        "outline": [
          "Explain the specific decision: Prevent performer names from being confused with character aliases",
          "Define the applicable contract and limits for Actor character credit mapping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent performer names from being confused with character aliases; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent performer names from being confused with character aliases",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:388",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-dialogue-vocative-pacing",
      "slug": "dialogue-vocative-pacing",
      "name": "Dialogue vocative pacing",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/dialogue-vocative-pacing/",
        "ja": "/ja/tools/dialogue-vocative-pacing/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Measure recorded name duration against a scene timing budget",
      "task": "Measure recorded name duration against a scene timing budget",
      "searchIntent": {
        "primary": "Complete the task: Measure recorded name duration against a scene timing budget",
        "queryHypothesis": "dialogue vocative pacing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to measure recorded name duration against a scene timing budget?",
        "When should dialogue vocative pacing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Measure recorded name duration against a scene timing budget",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Measure recorded name duration against a scene timing budget. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-correction-dialogue",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Measure recorded name duration against a scene timing budget versus Draft corrections that fit the character and scene stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-in-farewell-dialogue",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Measure recorded name duration against a scene timing budget versus Compare last address choices against the relationship arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Measure recorded name duration against a scene timing budget versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Measure recorded name duration against a scene timing budget",
        "outline": [
          "Explain the specific decision: Measure recorded name duration against a scene timing budget",
          "Define the applicable contract and limits for Dialogue vocative pacing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Measure recorded name duration against a scene timing budget; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Measure recorded name duration against a scene timing budget",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:389",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-bilingual-voice-pronunciation-parity",
      "slug": "bilingual-voice-pronunciation-parity",
      "name": "Bilingual voice pronunciation parity",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/bilingual-voice-pronunciation-parity/",
        "ja": "/ja/tools/bilingual-voice-pronunciation-parity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Align creator approved forms across recording languages",
      "task": "Align creator approved forms across recording languages",
      "searchIntent": {
        "primary": "Complete the task: Align creator approved forms across recording languages",
        "queryHypothesis": "bilingual voice pronunciation parity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to align creator approved forms across recording languages?",
        "When should bilingual voice pronunciation parity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Align creator approved forms across recording languages",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Align creator approved forms across recording languages. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Align creator approved forms across recording languages versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Align creator approved forms across recording languages versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Align creator approved forms across recording languages versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Align creator approved forms across recording languages",
        "outline": [
          "Explain the specific decision: Align creator approved forms across recording languages",
          "Define the applicable contract and limits for Bilingual voice pronunciation parity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Align creator approved forms across recording languages; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Align creator approved forms across recording languages",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:392",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-voice-director-alias-sheet",
      "slug": "voice-director-alias-sheet",
      "name": "Voice director alias sheet",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/voice-director-alias-sheet/",
        "ja": "/ja/tools/voice-director-alias-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Tell performers which identity a speaker believes they are addressing",
      "task": "Tell performers which identity a speaker believes they are addressing",
      "searchIntent": {
        "primary": "Complete the task: Tell performers which identity a speaker believes they are addressing",
        "queryHypothesis": "voice director alias sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tell performers which identity a speaker believes they are addressing?",
        "When should voice director alias sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tell performers which identity a speaker believes they are addressing",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tell performers which identity a speaker believes they are addressing. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-voice-cast-name-pronunciation-sheet",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Tell performers which identity a speaker believes they are addressing versus Package author readings and uncertainty for performers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.10476190476190475,
          "sharedProfile": false,
          "difference": "Tell performers which identity a speaker believes they are addressing versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.10166666666666666,
          "sharedProfile": false,
          "difference": "Tell performers which identity a speaker believes they are addressing versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tell performers which identity a speaker believes they are addressing",
        "outline": [
          "Explain the specific decision: Tell performers which identity a speaker believes they are addressing",
          "Define the applicable contract and limits for Voice director alias sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tell performers which identity a speaker believes they are addressing; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tell performers which identity a speaker believes they are addressing",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:393",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-cold-open-unknown-speaker-names",
      "slug": "cold-open-unknown-speaker-names",
      "name": "Cold open unknown speaker names",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/cold-open-unknown-speaker-names/",
        "ja": "/ja/tools/cold-open-unknown-speaker-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Hide reader identity while preserving production clarity",
      "task": "Hide reader identity while preserving production clarity",
      "searchIntent": {
        "primary": "Complete the task: Hide reader identity while preserving production clarity",
        "queryHypothesis": "cold open unknown speaker names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to hide reader identity while preserving production clarity?",
        "When should cold open unknown speaker names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Hide reader identity while preserving production clarity",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Hide reader identity while preserving production clarity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.245,
          "sharedProfile": false,
          "difference": "Hide reader identity while preserving production clarity versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unspoken-name-scene",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Hide reader identity while preserving production clarity versus Keep a name off the page while preserving referential clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-doppelganger-cast-labeling",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Hide reader identity while preserving production clarity versus Maintain intended likeness while preserving reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Hide reader identity while preserving production clarity",
        "outline": [
          "Explain the specific decision: Hide reader identity while preserving production clarity",
          "Define the applicable contract and limits for Cold open unknown speaker names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Hide reader identity while preserving production clarity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Hide reader identity while preserving production clarity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:394",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-sound-alike-suspect-audit",
      "slug": "sound-alike-suspect-audit",
      "name": "Sound alike suspect audit",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/sound-alike-suspect-audit/",
        "ja": "/ja/tools/sound-alike-suspect-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Preserve mystery fairness when names are heard rather than read",
      "task": "Preserve mystery fairness when names are heard rather than read",
      "searchIntent": {
        "primary": "Complete the task: Preserve mystery fairness when names are heard rather than read",
        "queryHypothesis": "sound alike suspect audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve mystery fairness when names are heard rather than read?",
        "When should sound alike suspect audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve mystery fairness when names are heard rather than read",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve mystery fairness when names are heard rather than read. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.10476190476190475,
          "sharedProfile": false,
          "difference": "Preserve mystery fairness when names are heard rather than read versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Preserve mystery fairness when names are heard rather than read versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-naming-anachronism-review",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Preserve mystery fairness when names are heard rather than read versus Flag unsupported forms rather than manufacture certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve mystery fairness when names are heard rather than read",
        "outline": [
          "Explain the specific decision: Preserve mystery fairness when names are heard rather than read",
          "Define the applicable contract and limits for Sound alike suspect audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve mystery fairness when names are heard rather than read; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve mystery fairness when names are heard rather than read",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:396",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-choral-crowd-name-calls",
      "slug": "choral-crowd-name-calls",
      "name": "Choral crowd name calls",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/choral-crowd-name-calls/",
        "ja": "/ja/tools/choral-crowd-name-calls/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Separate overlapping name calls in a storyboard plan",
      "task": "Separate overlapping name calls in a storyboard plan",
      "searchIntent": {
        "primary": "Complete the task: Separate overlapping name calls in a storyboard plan",
        "queryHypothesis": "choral crowd name calls",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate overlapping name calls in a storyboard plan?",
        "When should choral crowd name calls be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate overlapping name calls in a storyboard plan",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate overlapping name calls in a storyboard plan. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hidden-author-identity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Separate overlapping name calls in a storyboard plan versus Plan fictional manuscript credit and eventual author disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-exonym-endonym",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Separate overlapping name calls in a storyboard plan versus Track what a culture calls itself and what outsiders use; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Separate overlapping name calls in a storyboard plan versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate overlapping name calls in a storyboard plan",
        "outline": [
          "Explain the specific decision: Separate overlapping name calls in a storyboard plan",
          "Define the applicable contract and limits for Choral crowd name calls",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate overlapping name calls in a storyboard plan; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate overlapping name calls in a storyboard plan",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:399",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-voice-cast-retake-name-log",
      "slug": "voice-cast-retake-name-log",
      "name": "Voice cast retake name log",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/voice-cast-retake-name-log/",
        "ja": "/ja/tools/voice-cast-retake-name-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Track pronunciation corrections and affected timecodes",
      "task": "Track pronunciation corrections and affected timecodes",
      "searchIntent": {
        "primary": "Complete the task: Track pronunciation corrections and affected timecodes",
        "queryHypothesis": "voice cast retake name log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track pronunciation corrections and affected timecodes?",
        "When should voice cast retake name log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track pronunciation corrections and affected timecodes",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track pronunciation corrections and affected timecodes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-name-edit-decision-log",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Track pronunciation corrections and affected timecodes versus Preserve reasons, reviewers and affected passages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-drama-cast-announcement",
          "score": 0.13125,
          "sharedProfile": true,
          "difference": "Track pronunciation corrections and affected timecodes versus Order introductions with role and pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-synthetic-voice-name-exceptions",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Track pronunciation corrections and affected timecodes versus Prepare reviewed pronunciation hints for a chosen voice system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track pronunciation corrections and affected timecodes",
        "outline": [
          "Explain the specific decision: Track pronunciation corrections and affected timecodes",
          "Define the applicable contract and limits for Voice cast retake name log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track pronunciation corrections and affected timecodes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track pronunciation corrections and affected timecodes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:400",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-motion-comic-recap-audio-names",
      "slug": "motion-comic-recap-audio-names",
      "name": "Motion comic recap audio names",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/motion-comic-recap-audio-names/",
        "ja": "/ja/tools/motion-comic-recap-audio-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Reintroduce names without narrating hidden identities",
      "task": "Reintroduce names without narrating hidden identities",
      "searchIntent": {
        "primary": "Complete the task: Reintroduce names without narrating hidden identities",
        "queryHypothesis": "motion comic recap audio names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reintroduce names without narrating hidden identities?",
        "When should motion comic recap audio names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reintroduce names without narrating hidden identities",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reintroduce names without narrating hidden identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-inherited-questgiver-title",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reintroduce names without narrating hidden identities versus Transfer office without merging save identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-chapter-recap-names",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Reintroduce names without narrating hidden identities versus Select spoiler safe short references for returning readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-episodic-name-reintroduction",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Reintroduce names without narrating hidden identities versus Reintroduce a recurring character after publication gaps; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reintroduce names without narrating hidden identities",
        "outline": [
          "Explain the specific decision: Reintroduce names without narrating hidden identities",
          "Define the applicable contract and limits for Motion comic recap audio names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reintroduce names without narrating hidden identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reintroduce names without narrating hidden identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:401",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-subtitle-romanization-continuity",
      "slug": "subtitle-romanization-continuity",
      "name": "Subtitle romanization continuity",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/subtitle-romanization-continuity/",
        "ja": "/ja/tools/subtitle-romanization-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Match visible Latin spellings to the pronunciation bible",
      "task": "Match visible Latin spellings to the pronunciation bible",
      "searchIntent": {
        "primary": "Complete the task: Match visible Latin spellings to the pronunciation bible",
        "queryHypothesis": "subtitle romanization continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match visible Latin spellings to the pronunciation bible?",
        "When should subtitle romanization continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Match visible Latin spellings to the pronunciation bible",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Match visible Latin spellings to the pronunciation bible. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-apartment-cast-door-labels",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Match visible Latin spellings to the pronunciation bible versus Match visible labels to residents and concealed occupants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-emotional-continuity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Match visible Latin spellings to the pronunciation bible versus Test whether naming changes match the surrounding character behavior; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-badge-continuity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Match visible Latin spellings to the pronunciation bible versus Match art badge text to timeline and identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Match visible Latin spellings to the pronunciation bible",
        "outline": [
          "Explain the specific decision: Match visible Latin spellings to the pronunciation bible",
          "Define the applicable contract and limits for Subtitle romanization continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Match visible Latin spellings to the pronunciation bible; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Match visible Latin spellings to the pronunciation bible",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:402",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-dub-name-length-tradeoff",
      "slug": "dub-name-length-tradeoff",
      "name": "Dub name length tradeoff",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/dub-name-length-tradeoff/",
        "ja": "/ja/tools/dub-name-length-tradeoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Compare lip timing constraints with identity continuity",
      "task": "Compare lip timing constraints with identity continuity",
      "searchIntent": {
        "primary": "Complete the task: Compare lip timing constraints with identity continuity",
        "queryHypothesis": "dub name length tradeoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare lip timing constraints with identity continuity?",
        "When should dub name length tradeoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare lip timing constraints with identity continuity",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare lip timing constraints with identity continuity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-fake-document-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare lip timing constraints with identity continuity versus Reconcile a fictional document with cover identity constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-quest-marker-name-labels",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare lip timing constraints with identity continuity versus Preserve discovered identity under map space constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-length-budget",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Compare lip timing constraints with identity continuity versus Fit approved forms to actual UI or balloon constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare lip timing constraints with identity continuity",
        "outline": [
          "Explain the specific decision: Compare lip timing constraints with identity continuity",
          "Define the applicable contract and limits for Dub name length tradeoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare lip timing constraints with identity continuity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare lip timing constraints with identity continuity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:403",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-audiobook-chapter-name-headings",
      "slug": "audiobook-chapter-name-headings",
      "name": "Audiobook chapter name headings",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/audiobook-chapter-name-headings/",
        "ja": "/ja/tools/audiobook-chapter-name-headings/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Test spoken headings for identity spoilers and clarity",
      "task": "Test spoken headings for identity spoilers and clarity",
      "searchIntent": {
        "primary": "Complete the task: Test spoken headings for identity spoilers and clarity",
        "queryHypothesis": "audiobook chapter name headings",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test spoken headings for identity spoilers and clarity?",
        "When should audiobook chapter name headings be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test spoken headings for identity spoilers and clarity",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test spoken headings for identity spoilers and clarity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-chapter-heading",
          "score": 0.2825,
          "sharedProfile": false,
          "difference": "Test spoken headings for identity spoilers and clarity versus Test headings against viewpoint identity and spoiler exposure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-audio-introduction",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Test spoken headings for identity spoilers and clarity versus Test host introductions and spoken acknowledgments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Test spoken headings for identity spoilers and clarity versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test spoken headings for identity spoilers and clarity",
        "outline": [
          "Explain the specific decision: Test spoken headings for identity spoilers and clarity",
          "Define the applicable contract and limits for Audiobook chapter name headings",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test spoken headings for identity spoilers and clarity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test spoken headings for identity spoilers and clarity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:404",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-audio-drama-cast-announcement",
      "slug": "audio-drama-cast-announcement",
      "name": "Audio drama cast announcement",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/audio-drama-cast-announcement/",
        "ja": "/ja/tools/audio-drama-cast-announcement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Order introductions with role and pronunciation support",
      "task": "Order introductions with role and pronunciation support",
      "searchIntent": {
        "primary": "Complete the task: Order introductions with role and pronunciation support",
        "queryHypothesis": "audio drama cast announcement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to order introductions with role and pronunciation support?",
        "When should audio drama cast announcement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Order introductions with role and pronunciation support",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Order introductions with role and pronunciation support. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-select-name-cards",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Order introductions with role and pronunciation support versus Compare full and short names with pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-tabletop-name-index-cards",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Order introductions with role and pronunciation support versus Produce short physical references with role and pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-voice-cast-retake-name-log",
          "score": 0.13125,
          "sharedProfile": true,
          "difference": "Order introductions with role and pronunciation support versus Track pronunciation corrections and affected timecodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Order introductions with role and pronunciation support",
        "outline": [
          "Explain the specific decision: Order introductions with role and pronunciation support",
          "Define the applicable contract and limits for Audio drama cast announcement",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Order introductions with role and pronunciation support; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Order introductions with role and pronunciation support",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:405",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-podcast-fiction-guest-names",
      "slug": "podcast-fiction-guest-names",
      "name": "Podcast fiction guest names",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/podcast-fiction-guest-names/",
        "ja": "/ja/tools/podcast-fiction-guest-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Avoid confusion between returning and one episode characters",
      "task": "Avoid confusion between returning and one episode characters",
      "searchIntent": {
        "primary": "Complete the task: Avoid confusion between returning and one episode characters",
        "queryHypothesis": "podcast fiction guest names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid confusion between returning and one episode characters?",
        "When should podcast fiction guest names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid confusion between returning and one episode characters",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid confusion between returning and one episode characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-program-character-namespace",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid confusion between returning and one episode characters versus Avoid collisions between display names and technical keys; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-fiction-composite-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Avoid confusion between returning and one episode characters versus Document invented combinations and avoid presenting them as attested; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rebel-cell-identity-separation",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid confusion between returning and one episode characters versus Avoid accidental leakage between cells in story dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid confusion between returning and one episode characters",
        "outline": [
          "Explain the specific decision: Avoid confusion between returning and one episode characters",
          "Define the applicable contract and limits for Podcast fiction guest names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid confusion between returning and one episode characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid confusion between returning and one episode characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:406",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-audio-glossary-access",
      "slug": "audio-glossary-access",
      "name": "Audio glossary access",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/audio-glossary-access/",
        "ja": "/ja/tools/audio-glossary-access/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Supply spoiler gated pronunciation notes by episode",
      "task": "Supply spoiler gated pronunciation notes by episode",
      "searchIntent": {
        "primary": "Complete the task: Supply spoiler gated pronunciation notes by episode",
        "queryHypothesis": "audio glossary access",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to supply spoiler gated pronunciation notes by episode?",
        "When should audio glossary access be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Supply spoiler gated pronunciation notes by episode",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Supply spoiler gated pronunciation notes by episode. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-tabletop-npc-quick-brief",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Supply spoiler gated pronunciation notes by episode versus Generate usable names with pronunciation and encounter notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-drama-cast-announcement",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Supply spoiler gated pronunciation notes by episode versus Order introductions with role and pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-select-name-cards",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Supply spoiler gated pronunciation notes by episode versus Compare full and short names with pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Supply spoiler gated pronunciation notes by episode",
        "outline": [
          "Explain the specific decision: Supply spoiler gated pronunciation notes by episode",
          "Define the applicable contract and limits for Audio glossary access",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Supply spoiler gated pronunciation notes by episode; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Supply spoiler gated pronunciation notes by episode",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:407",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-character-stutter-name-policy",
      "slug": "character-stutter-name-policy",
      "name": "Character stutter name policy",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/character-stutter-name-policy/",
        "ja": "/ja/tools/character-stutter-name-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Record deliberate performance choices without treating disability as a naming trope",
      "task": "Record deliberate performance choices without treating disability as a naming trope",
      "searchIntent": {
        "primary": "Complete the task: Record deliberate performance choices without treating disability as a naming trope",
        "queryHypothesis": "character stutter name policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record deliberate performance choices without treating disability as a naming trope?",
        "When should character stutter name policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record deliberate performance choices without treating disability as a naming trope",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record deliberate performance choices without treating disability as a naming trope. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-forgives-misnaming",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Record deliberate performance choices without treating disability as a naming trope versus Show response and boundaries without treating forgiveness as required; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-disputed-throne-titles",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Record deliberate performance choices without treating disability as a naming trope versus Track rival claims without treating a title as verified legitimacy; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-branch-differentiation",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Record deliberate performance choices without treating disability as a naming trope versus Mark branches without treating all cousins as interchangeable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record deliberate performance choices without treating disability as a naming trope",
        "outline": [
          "Explain the specific decision: Record deliberate performance choices without treating disability as a naming trope",
          "Define the applicable contract and limits for Character stutter name policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record deliberate performance choices without treating disability as a naming trope; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record deliberate performance choices without treating disability as a naming trope",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:408",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-synthetic-voice-name-exceptions",
      "slug": "synthetic-voice-name-exceptions",
      "name": "Synthetic voice name exceptions",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/synthetic-voice-name-exceptions/",
        "ja": "/ja/tools/synthetic-voice-name-exceptions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Prepare reviewed pronunciation hints for a chosen voice system",
      "task": "Prepare reviewed pronunciation hints for a chosen voice system",
      "searchIntent": {
        "primary": "Complete the task: Prepare reviewed pronunciation hints for a chosen voice system",
        "queryHypothesis": "synthetic voice name exceptions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prepare reviewed pronunciation hints for a chosen voice system?",
        "When should synthetic voice name exceptions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prepare reviewed pronunciation hints for a chosen voice system",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prepare reviewed pronunciation hints for a chosen voice system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-romanization-source-map",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Prepare reviewed pronunciation hints for a chosen voice system versus Store the chosen system and exception evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-voice-cast-retake-name-log",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Prepare reviewed pronunciation hints for a chosen voice system versus Track pronunciation corrections and affected timecodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Prepare reviewed pronunciation hints for a chosen voice system versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prepare reviewed pronunciation hints for a chosen voice system",
        "outline": [
          "Explain the specific decision: Prepare reviewed pronunciation hints for a chosen voice system",
          "Define the applicable contract and limits for Synthetic voice name exceptions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prepare reviewed pronunciation hints for a chosen voice system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prepare reviewed pronunciation hints for a chosen voice system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:409",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-performed-name-consent-notes",
      "slug": "performed-name-consent-notes",
      "name": "Performed name consent notes",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/performed-name-consent-notes/",
        "ja": "/ja/tools/performed-name-consent-notes/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Record performer and creator approval for sensitive forms of address",
      "task": "Record performer and creator approval for sensitive forms of address",
      "searchIntent": {
        "primary": "Complete the task: Record performer and creator approval for sensitive forms of address",
        "queryHypothesis": "performed name consent notes",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record performer and creator approval for sensitive forms of address?",
        "When should performed name consent notes be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record performer and creator approval for sensitive forms of address",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record performer and creator approval for sensitive forms of address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Record performer and creator approval for sensitive forms of address versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-voice-pronunciation-parity",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Record performer and creator approval for sensitive forms of address versus Align creator approved forms across recording languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Record performer and creator approval for sensitive forms of address versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record performer and creator approval for sensitive forms of address",
        "outline": [
          "Explain the specific decision: Record performer and creator approval for sensitive forms of address",
          "Define the applicable contract and limits for Performed name consent notes",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record performer and creator approval for sensitive forms of address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record performer and creator approval for sensitive forms of address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:410",
      "profileSource": "data/profiles.json#audio-drama"
    },
    {
      "id": "nw-game-npc-name-registry",
      "slug": "game-npc-name-registry",
      "name": "Game NPC name registry",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-npc-name-registry/",
        "ja": "/ja/tools/game-npc-name-registry/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Assign stable identity keys and separate display names",
      "task": "Assign stable identity keys and separate display names",
      "searchIntent": {
        "primary": "Complete the task: Assign stable identity keys and separate display names",
        "queryHypothesis": "game npc name registry",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to assign stable identity keys and separate display names?",
        "When should game npc name registry be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Insert name as text at output boundaries"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Assign stable identity keys and separate display names",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons",
        "Safely rendered original string"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Assign stable identity keys and separate display names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.30208333333333337,
          "sharedProfile": true,
          "difference": "Assign stable identity keys and separate display names versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-engine-name-key-migration",
          "score": 0.30208333333333337,
          "sharedProfile": false,
          "difference": "Assign stable identity keys and separate display names versus Keep resource keys stable during display name revisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Assign stable identity keys and separate display names versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Assign stable identity keys and separate display names",
        "outline": [
          "Explain the specific decision: Assign stable identity keys and separate display names",
          "Define the applicable contract and limits for Game NPC name registry",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Assign stable identity keys and separate display names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Assign stable identity keys and separate display names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Script-like input remains visible text"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:413",
      "profileSource": "data/profiles.json#game-characters",
      "absorbedModules": [
        {
          "sourceId": "nw-game-name-markup-escaping",
          "input": "displayText",
          "rule": "Insert name as text at output boundaries",
          "output": "Safely rendered original string",
          "acceptance": "Script-like input remains visible text",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-procedural-npc-naming",
      "slug": "procedural-npc-naming",
      "name": "Procedural NPC naming",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/procedural-npc-naming/",
        "ja": "/ja/tools/procedural-npc-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Generate from explicit settlement rules and uniqueness scope",
      "task": "Generate from explicit settlement rules and uniqueness scope",
      "searchIntent": {
        "primary": "Complete the task: Generate from explicit settlement rules and uniqueness scope",
        "queryHypothesis": "procedural npc naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate from explicit settlement rules and uniqueness scope?",
        "When should procedural npc naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "seed",
          "use": "Pin deterministic generation for a saved character ID."
        },
        {
          "key": "corpusVersion",
          "use": "Avoid changed output after a data update."
        },
        {
          "key": "cultureGrammar",
          "use": "Select explicit fictional composition rules."
        },
        {
          "key": "uniquenessScope",
          "use": "Choose settlement, region or project scope without claiming worldwide uniqueness."
        },
        {
          "key": "locksAndExclusions",
          "use": "Preserve accepted components and enforce user-supplied forbidden forms."
        }
      ],
      "rules": [
        "Use a documented deterministic PRNG with a versioned seed contract.",
        "Filter invalid components before combination and validate full forms after combination.",
        "Deduplicate within the declared scope, including saved accepted identities.",
        "Bound attempts and return exhaustion diagnostics rather than loop forever.",
        "Never silently relax a hard exclusion to fill the requested batch.",
        "Use deterministic seed and versioned corpus ordering",
        "Stop when finite eligible combinations are exhausted",
        "Report eligible corpus counts before generation",
        "Distinguish full-name and token exclusions",
        "Regenerate only unlocked components"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Use a documented deterministic PRNG with a versioned seed contract.",
        "Filter invalid components before combination and validate full forms after combination.",
        "Deduplicate within the declared scope, including saved accepted identities.",
        "Bound attempts and return exhaustion diagnostics rather than loop forever.",
        "Never silently relax a hard exclusion to fill the requested batch.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "stable NPC ID and name components",
        "seed, grammar and corpus versions",
        "derivation trace",
        "uniqueness scope",
        "exhaustion reasons and targeted relaxation options",
        "Reproduction bundle",
        "Partial status and missing count",
        "Pool coverage",
        "Matched exclusion reasons",
        "Preserved and regenerated fields"
      ],
      "capabilities": [
        "Replay one NPC exactly from its saved provenance bundle.",
        "Regenerate unlocked components while preserving assigned family structure."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The task creates persistent, reproducible identities under world and save constraints; ad hoc batch names cannot preserve generated settlements.",
        "proposedDifferenceAxes": [
          "rules",
          "data",
          "inputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-family-generation",
          "score": 0.2175,
          "sharedProfile": true,
          "difference": "Generate from explicit settlement rules and uniqueness scope versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Generate from explicit settlement rules and uniqueness scope versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inheritance-event-names",
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Generate from explicit settlement rules and uniqueness scope versus Apply surname and title rules after a succession event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Procedural names are persistent narrative data, not disposable random strings.",
        "outline": [
          "Define what must remain stable in a save",
          "Choose a real uniqueness scope",
          "A dock settlement that runs out of surnames",
          "Explain exhaustion without breaking the world grammar",
          "Version data before shipping an expansion"
        ],
        "story": "Fictional example: a game update regenerates a ferryman under a new surname while an old journal still uses his earlier one. The revised design stores identity output and versioned provenance rather than recomputing on every load.",
        "storyAnalysis": "A reproducible seed is insufficient if corpus ordering changes. Compare saving the accepted name with regenerating against pinned versions.",
        "evidence": "Original deterministic fixtures planned; Ink and Ren'Py inform separation of story state and display strings, not a claim of integration already built.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/npc.md",
        "localizedBodies": {
          "en": "content/en/npc.md",
          "ja": "content/ja/npc.md"
        }
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "Same pinned bundle generates byte-equivalent identity output.",
        "Changing a grammar suffix changes every eligible unlocked generated surname.",
        "Requesting more unique names than the eligible pool returns partial or empty status with exact reason.",
        "A corpus update does not rename existing saved identities.",
        "Same bundle returns identical candidates",
        "Overrequest returns exact shortfall without duplicates",
        "Empty surname pool is explained",
        "Token exclusion cannot be silently relaxed",
        "Locked surname persists for every candidate"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:414",
      "profileSource": "data/profiles.json#game-characters",
      "absorbedModules": [
        {
          "sourceId": "nw-npc-name-seed-reproducibility",
          "input": "seed; corpusVersion",
          "rule": "Use deterministic seed and versioned corpus ordering",
          "output": "Reproduction bundle",
          "acceptance": "Same bundle returns identical candidates",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-npc-unique-name-exhaustion",
          "input": "uniquenessScope; requestedCount",
          "rule": "Stop when finite eligible combinations are exhausted",
          "output": "Partial status and missing count",
          "acceptance": "Overrequest returns exact shortfall without duplicates",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-npc-name-generation-coverage",
          "input": "grammarEligibility",
          "rule": "Report eligible corpus counts before generation",
          "output": "Pool coverage",
          "acceptance": "Empty surname pool is explained",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-npc-forbidden-token-rules",
          "input": "exclusions; exclusionMode",
          "rule": "Distinguish full-name and token exclusions",
          "output": "Matched exclusion reasons",
          "acceptance": "Token exclusion cannot be silently relaxed",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-game-name-randomizer-lock",
          "input": "lockedComponents",
          "rule": "Regenerate only unlocked components",
          "output": "Preserved and regenerated fields",
          "acceptance": "Locked surname persists for every candidate",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "npc",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/corpus.mjs",
          "web/corpus-ui.js"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/corpus.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "grammar",
          "label": [
            "Naming source or invented grammar",
            "名前の資料・架空の命名規則"
          ],
          "type": "select",
          "default": "river",
          "help": null,
          "options": [
            [
              "river",
              [
                "River · vowel-led names, -en families",
                "River · 母音中心の名、姓に -en"
              ]
            ],
            [
              "ridge",
              [
                "Ridge · clusters, -ak families",
                "Ridge · 子音の組合せ、姓に -ak"
              ]
            ],
            [
              "coast",
              [
                "Coast · open syllables, -a families",
                "Coast · 開いた音節、姓に -a"
              ]
            ],
            [
              "us-reference",
              [
                "US reference components · not an invented culture",
                "米国資料の要素・架空文化ではありません"
              ]
            ]
          ]
        },
        {
          "key": "lockSurname",
          "label": [
            "Locked family component · optional",
            "姓を固定・任意"
          ],
          "type": "text",
          "default": "",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "seed",
          "label": [
            "Reproducible seed",
            "再現用シード"
          ],
          "type": "text",
          "default": "woven-01",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "count",
          "label": [
            "Results · 1–30",
            "生成数 · 1〜30"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "exclude",
          "label": [
            "Excluded strings",
            "除外する文字列"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Comma-separated. Matching is case-insensitive.",
            "カンマ区切り。大文字と小文字は区別しません。"
          ]
        },
        {
          "key": "exclusionMode",
          "label": [
            "Exclusion scope",
            "除外の範囲"
          ],
          "type": "select",
          "default": "contains",
          "help": null,
          "options": [
            [
              "contains",
              [
                "Contains string",
                "文字列を含む"
              ]
            ],
            [
              "exact",
              [
                "Exact full name",
                "姓名の完全一致"
              ]
            ]
          ]
        },
        {
          "key": "idPrefix",
          "label": [
            "Stable ID prefix",
            "人物IDの接頭辞"
          ],
          "type": "text",
          "default": "npc",
          "help": null
        },
        {
          "key": "corpusVersion",
          "label": [
            "Invented-pool version · fictional grammars only",
            "架空プールの版・架空規則のみ"
          ],
          "type": "text",
          "default": "npc-invented-corpora-v1",
          "help": null
        },
        {
          "key": "uniquenessScope",
          "label": [
            "Your uniqueness scope label",
            "重複確認の範囲名"
          ],
          "type": "text",
          "default": "project",
          "help": null
        },
        {
          "key": "familySuffix",
          "label": [
            "Override authored family suffix · optional",
            "姓の接尾辞を変更・任意"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "persisted",
          "label": [
            "Accepted identities to preserve",
            "保持する採用済み人物"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "ID | accepted full name | given component | surname. These will not be regenerated.",
            "ID | 採用済みの姓名 | 名 | 姓。これらは再生成しません。"
          ]
        },
        {
          "key": "givenPrefix",
          "label": [
            "Source given-name prefix",
            "資料の名の先頭文字"
          ],
          "type": "text",
          "default": "Ma",
          "help": null
        },
        {
          "key": "surnamePrefix",
          "label": [
            "Source surname prefix",
            "資料の姓の先頭文字"
          ],
          "type": "text",
          "default": "S",
          "help": null
        },
        {
          "key": "minGivenCount",
          "label": [
            "Minimum aggregate published given-name count",
            "名の公開申請合計の下限"
          ],
          "type": "number",
          "default": 0,
          "help": null
        },
        {
          "key": "referenceVersion",
          "label": [
            "Pinned source-component version",
            "名前要素の固定した資料版"
          ],
          "type": "text",
          "default": "cd78e975ed7bb358e018dd62fbe14ced89295e9581c49172ca4eedcb011b3724:117c41cb4668727b7627b2845b6df3f83eb2a22a1813f42c0ff4bdcab86de135",
          "help": null
        }
      ],
      "availableSourceManifest": "data/corpora/manifest.json"
    },
    {
      "id": "nw-playable-character-preset-names",
      "slug": "playable-character-preset-names",
      "name": "Playable character preset names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/playable-character-preset-names/",
        "ja": "/ja/tools/playable-character-preset-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Keep defaults distinct from player chosen identity",
      "task": "Keep defaults distinct from player chosen identity",
      "searchIntent": {
        "primary": "Complete the task: Keep defaults distinct from player chosen identity",
        "queryHypothesis": "playable character preset names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep defaults distinct from player chosen identity?",
        "When should playable character preset names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep defaults distinct from player chosen identity",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep defaults distinct from player chosen identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-live-roleplay-identity-badges",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep defaults distinct from player chosen identity versus Separate player safety information from fictional identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-confession-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep defaults distinct from player chosen identity versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-leaderboard-fiction-identities",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep defaults distinct from player chosen identity versus Separate fictional in world rankings from player account identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep defaults distinct from player chosen identity",
        "outline": [
          "Explain the specific decision: Keep defaults distinct from player chosen identity",
          "Define the applicable contract and limits for Playable character preset names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep defaults distinct from player chosen identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep defaults distinct from player chosen identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:415",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-player-renaming-story-integration",
      "slug": "player-renaming-story-integration",
      "name": "Player renaming story integration",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/player-renaming-story-integration/",
        "ja": "/ja/tools/player-renaming-story-integration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Define which dialogue and records update after renaming",
      "task": "Define which dialogue and records update after renaming",
      "searchIntent": {
        "primary": "Complete the task: Define which dialogue and records update after renaming",
        "queryHypothesis": "player renaming story integration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define which dialogue and records update after renaming?",
        "When should player renaming story integration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define which dialogue and records update after renaming",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define which dialogue and records update after renaming. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-erasure-story-continuity",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Define which dialogue and records update after renaming versus Define how records and memories change after erasure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rank-change-address-timeline",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Define which dialogue and records update after renaming versus Update dialogue after promotions and demotions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-reconciles-dual-identities",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define which dialogue and records update after renaming versus Define which differences remain after integration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define which dialogue and records update after renaming",
        "outline": [
          "Explain the specific decision: Define which dialogue and records update after renaming",
          "Define the applicable contract and limits for Player renaming story integration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define which dialogue and records update after renaming; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define which dialogue and records update after renaming",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:416",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-rpg-companion-name-roster",
      "slug": "rpg-companion-name-roster",
      "name": "RPG companion name roster",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/rpg-companion-name-roster/",
        "ja": "/ja/tools/rpg-companion-name-roster/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Distinguish companions in dialogue and party UI",
      "task": "Distinguish companions in dialogue and party UI",
      "searchIntent": {
        "primary": "Complete the task: Distinguish companions in dialogue and party UI",
        "queryHypothesis": "rpg companion name roster",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish companions in dialogue and party UI?",
        "When should rpg companion name roster be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish companions in dialogue and party UI",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish companions in dialogue and party UI. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-party-list-name-disambiguation",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish companions in dialogue and party UI versus Distinguish shortened names in a compact party display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-suspect-name-roster",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Distinguish companions in dialogue and party UI versus Distinguish suspects while preserving intentionally misleading associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-love-triangle-name-clarity",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Distinguish companions in dialogue and party UI versus Distinguish three leads in rapidly alternating dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish companions in dialogue and party UI",
        "outline": [
          "Explain the specific decision: Distinguish companions in dialogue and party UI",
          "Define the applicable contract and limits for RPG companion name roster",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish companions in dialogue and party UI; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish companions in dialogue and party UI",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:417",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-family-generation",
      "slug": "npc-family-generation",
      "name": "NPC family generation",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-family-generation/",
        "ja": "/ja/tools/npc-family-generation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Propagate household rules through a generated settlement graph",
      "task": "Propagate household rules through a generated settlement graph",
      "searchIntent": {
        "primary": "Complete the task: Propagate household rules through a generated settlement graph",
        "queryHypothesis": "npc family generation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to propagate household rules through a generated settlement graph?",
        "When should npc family generation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Propagate household rules through a generated settlement graph",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Propagate household rules through a generated settlement graph. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-procedural-npc-naming",
          "score": 0.2175,
          "sharedProfile": true,
          "difference": "Propagate household rules through a generated settlement graph versus Generate from explicit settlement rules and uniqueness scope; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Propagate household rules through a generated settlement graph versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-generation-marker",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Propagate household rules through a generated settlement graph versus Apply an author defined generation scheme to eligible relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Propagate household rules through a generated settlement graph",
        "outline": [
          "Explain the specific decision: Propagate household rules through a generated settlement graph",
          "Define the applicable contract and limits for NPC family generation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Propagate household rules through a generated settlement graph; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Propagate household rules through a generated settlement graph",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:418",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-occupation-name-separation",
      "slug": "npc-occupation-name-separation",
      "name": "NPC occupation name separation",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-occupation-name-separation/",
        "ja": "/ja/tools/npc-occupation-name-separation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Keep role titles from replacing individual identity",
      "task": "Keep role titles from replacing individual identity",
      "searchIntent": {
        "primary": "Complete the task: Keep role titles from replacing individual identity",
        "queryHypothesis": "npc occupation name separation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep role titles from replacing individual identity?",
        "When should npc occupation name separation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep role titles from replacing individual identity",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep role titles from replacing individual identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-clan-branch-registry",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep role titles from replacing individual identity versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep role titles from replacing individual identity versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep role titles from replacing individual identity versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep role titles from replacing individual identity",
        "outline": [
          "Explain the specific decision: Keep role titles from replacing individual identity",
          "Define the applicable contract and limits for NPC occupation name separation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep role titles from replacing individual identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep role titles from replacing individual identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:419",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-respawn-identity",
      "slug": "npc-respawn-identity",
      "name": "NPC respawn identity",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-respawn-identity/",
        "ja": "/ja/tools/npc-respawn-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Decide whether respawned units retain or replace identity",
      "task": "Decide whether respawned units retain or replace identity",
      "searchIntent": {
        "primary": "Complete the task: Decide whether respawned units retain or replace identity",
        "queryHypothesis": "npc respawn identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide whether respawned units retain or replace identity?",
        "When should npc respawn identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide whether respawned units retain or replace identity",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide whether respawned units retain or replace identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-dialogue-history-identity",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Decide whether respawned units retain or replace identity versus Decide whether past lines retain historically visible names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Decide whether respawned units retain or replace identity versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-social-memory-names",
          "score": 0.16999999999999998,
          "sharedProfile": true,
          "difference": "Decide whether respawned units retain or replace identity versus Decide which observers remember an earlier identity after a quest; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide whether respawned units retain or replace identity",
        "outline": [
          "Explain the specific decision: Decide whether respawned units retain or replace identity",
          "Define the applicable contract and limits for NPC respawn identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide whether respawned units retain or replace identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide whether respawned units retain or replace identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:420",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-persistence-across-saves",
      "slug": "npc-persistence-across-saves",
      "name": "NPC persistence across saves",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-persistence-across-saves/",
        "ja": "/ja/tools/npc-persistence-across-saves/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Serialize generated names with stable IDs",
      "task": "Serialize generated names with stable IDs",
      "searchIntent": {
        "primary": "Complete the task: Serialize generated names with stable IDs",
        "queryHypothesis": "npc persistence across saves",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to serialize generated names with stable IDs?",
        "When should npc persistence across saves be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Serialize generated names with stable IDs",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Serialize generated names with stable IDs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-localization-name-map",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Serialize generated names with stable IDs versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-translator-handoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Serialize generated names with stable IDs versus Export stable IDs, evidence and unresolved localization decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Serialize generated names with stable IDs versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Serialize generated names with stable IDs",
        "outline": [
          "Explain the specific decision: Serialize generated names with stable IDs",
          "Define the applicable contract and limits for NPC persistence across saves",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Serialize generated names with stable IDs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Serialize generated names with stable IDs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:421",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-seasonal-population-naming",
      "slug": "npc-seasonal-population-naming",
      "name": "NPC seasonal population naming",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-seasonal-population-naming/",
        "ja": "/ja/tools/npc-seasonal-population-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Maintain continuity through time based population changes",
      "task": "Maintain continuity through time based population changes",
      "searchIntent": {
        "primary": "Complete the task: Maintain continuity through time based population changes",
        "queryHypothesis": "npc seasonal population naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain continuity through time based population changes?",
        "When should npc seasonal population naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain continuity through time based population changes",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain continuity through time based population changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-hostile-friendly-identity",
          "score": 0.38333333333333336,
          "sharedProfile": true,
          "difference": "Maintain continuity through time based population changes versus Maintain character continuity through allegiance changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estrangement-address-reversal",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Maintain continuity through time based population changes versus Restore distance through deliberate naming changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-family-generation",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Maintain continuity through time based population changes versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain continuity through time based population changes",
        "outline": [
          "Explain the specific decision: Maintain continuity through time based population changes",
          "Define the applicable contract and limits for NPC seasonal population naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain continuity through time based population changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain continuity through time based population changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:422",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-migration-between-towns",
      "slug": "npc-migration-between-towns",
      "name": "NPC migration between towns",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-migration-between-towns/",
        "ja": "/ja/tools/npc-migration-between-towns/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Preserve individual names while updating local forms of address",
      "task": "Preserve individual names while updating local forms of address",
      "searchIntent": {
        "primary": "Complete the task: Preserve individual names while updating local forms of address",
        "queryHypothesis": "npc migration between towns",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve individual names while updating local forms of address?",
        "When should npc migration between towns be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve individual names while updating local forms of address",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve individual names while updating local forms of address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-save-migration-renamed-npc",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Preserve individual names while updating local forms of address versus Preserve old save IDs while changing approved display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-migration-naming",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Preserve individual names while updating local forms of address versus Track retained, adapted and imposed forms across a journey; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-village-ensemble-name-ecology",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Preserve individual names while updating local forms of address versus Balance local patterns with individual distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve individual names while updating local forms of address",
        "outline": [
          "Explain the specific decision: Preserve individual names while updating local forms of address",
          "Define the applicable contract and limits for NPC migration between towns",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve individual names while updating local forms of address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve individual names while updating local forms of address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:423",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-aging-name-timeline",
      "slug": "npc-aging-name-timeline",
      "name": "NPC aging name timeline",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-aging-name-timeline/",
        "ja": "/ja/tools/npc-aging-name-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Transition child, adult and later references by world date",
      "task": "Transition child, adult and later references by world date",
      "searchIntent": {
        "primary": "Complete the task: Transition child, adult and later references by world date",
        "queryHypothesis": "npc aging name timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transition child, adult and later references by world date?",
        "When should npc aging name timeline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transition child, adult and later references by world date",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transition child, adult and later references by world date. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-timeline-name-changes",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Transition child, adult and later references by world date versus Resolve the correct reference at each book date; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-marriage-event-names",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Transition child, adult and later references by world date versus Update selected fields while preserving preevent references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-session-npc-improvisation-log",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Transition child, adult and later references by world date versus Save improvised names with context for later continuity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transition child, adult and later references by world date",
        "outline": [
          "Explain the specific decision: Transition child, adult and later references by world date",
          "Define the applicable contract and limits for NPC aging name timeline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transition child, adult and later references by world date; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transition child, adult and later references by world date",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:424",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-inheritance-event-names",
      "slug": "npc-inheritance-event-names",
      "name": "NPC inheritance event names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-inheritance-event-names/",
        "ja": "/ja/tools/npc-inheritance-event-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Apply surname and title rules after a succession event",
      "task": "Apply surname and title rules after a succession event",
      "searchIntent": {
        "primary": "Complete the task: Apply surname and title rules after a succession event",
        "queryHypothesis": "npc inheritance event names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply surname and title rules after a succession event?",
        "When should npc inheritance event names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply surname and title rules after a succession event",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply surname and title rules after a succession event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.2931818181818182,
          "sharedProfile": true,
          "difference": "Apply surname and title rules after a succession event versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-marriage-event-names",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Apply surname and title rules after a succession event versus Update selected fields while preserving preevent references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-inheritance-exception",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Apply surname and title rules after a succession event versus Document the story event that overrides the default surname rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply surname and title rules after a succession event",
        "outline": [
          "Explain the specific decision: Apply surname and title rules after a succession event",
          "Define the applicable contract and limits for NPC inheritance event names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply surname and title rules after a succession event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply surname and title rules after a succession event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:425",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-marriage-event-names",
      "slug": "npc-marriage-event-names",
      "name": "NPC marriage event names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-marriage-event-names/",
        "ja": "/ja/tools/npc-marriage-event-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Update selected fields while preserving preevent references",
      "task": "Update selected fields while preserving preevent references",
      "searchIntent": {
        "primary": "Complete the task: Update selected fields while preserving preevent references",
        "queryHypothesis": "npc marriage event names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update selected fields while preserving preevent references?",
        "When should npc marriage event names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update selected fields while preserving preevent references",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update selected fields while preserving preevent references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Update selected fields while preserving preevent references versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inheritance-event-names",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Update selected fields while preserving preevent references versus Apply surname and title rules after a succession event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-forgotten-by-everyone",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Update selected fields while preserving preevent references versus Preserve reader orientation while characters lose references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update selected fields while preserving preevent references",
        "outline": [
          "Explain the specific decision: Update selected fields while preserving preevent references",
          "Define the applicable contract and limits for NPC marriage event names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update selected fields while preserving preevent references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update selected fields while preserving preevent references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:426",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-adoption-event-names",
      "slug": "npc-adoption-event-names",
      "name": "NPC adoption event names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-adoption-event-names/",
        "ja": "/ja/tools/npc-adoption-event-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Apply household rules with author approved identity retention",
      "task": "Apply household rules with author approved identity retention",
      "searchIntent": {
        "primary": "Complete the task: Apply household rules with author approved identity retention",
        "queryHypothesis": "npc adoption event names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply household rules with author approved identity retention?",
        "When should npc adoption event names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply household rules with author approved identity retention",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply household rules with author approved identity retention. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-inheritance-event-names",
          "score": 0.2931818181818182,
          "sharedProfile": true,
          "difference": "Apply household rules with author approved identity retention versus Apply surname and title rules after a succession event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-order-initiation-names",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Apply household rules with author approved identity retention versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wizard-order-name",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Apply household rules with author approved identity retention versus Apply fictional rank and initiation rules to a personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply household rules with author approved identity retention",
        "outline": [
          "Explain the specific decision: Apply household rules with author approved identity retention",
          "Define the applicable contract and limits for NPC adoption event names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply household rules with author approved identity retention; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply household rules with author approved identity retention",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:427",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-relationship-address-lookup",
      "slug": "npc-relationship-address-lookup",
      "name": "NPC relationship address lookup",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-relationship-address-lookup/",
        "ja": "/ja/tools/npc-relationship-address-lookup/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Resolve a display form using speaker listener and game state",
      "task": "Resolve a display form using speaker listener and game state",
      "searchIntent": {
        "primary": "Complete the task: Resolve a display form using speaker listener and game state",
        "queryHypothesis": "npc relationship address lookup",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve a display form using speaker listener and game state?",
        "When should npc relationship address lookup be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve a display form using speaker listener and game state",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve a display form using speaker listener and game state. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-address-relationship-graph",
          "score": 0.23285714285714285,
          "sharedProfile": false,
          "difference": "Resolve a display form using speaker listener and game state versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Resolve a display form using speaker listener and game state versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-body-swap-name-tracking",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Resolve a display form using speaker listener and game state versus Resolve speaker labels against mind and body state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve a display form using speaker listener and game state",
        "outline": [
          "Explain the specific decision: Resolve a display form using speaker listener and game state",
          "Define the applicable contract and limits for NPC relationship address lookup",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve a display form using speaker listener and game state; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve a display form using speaker listener and game state",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:428",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-alias-state-machine",
      "slug": "npc-alias-state-machine",
      "name": "NPC alias state machine",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-alias-state-machine/",
        "ja": "/ja/tools/npc-alias-state-machine/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Change visible identity only when narrative conditions allow it",
      "task": "Change visible identity only when narrative conditions allow it",
      "searchIntent": {
        "primary": "Complete the task: Change visible identity only when narrative conditions allow it",
        "queryHypothesis": "npc alias state machine",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to change visible identity only when narrative conditions allow it?",
        "When should npc alias state machine be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Change visible identity only when narrative conditions allow it",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Change visible identity only when narrative conditions allow it. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-swarm-character-continuity",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Change visible identity only when narrative conditions allow it versus Preserve identity when constituent members change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Change visible identity only when narrative conditions allow it versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Change visible identity only when narrative conditions allow it versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Change visible identity only when narrative conditions allow it",
        "outline": [
          "Explain the specific decision: Change visible identity only when narrative conditions allow it",
          "Define the applicable contract and limits for NPC alias state machine",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Change visible identity only when narrative conditions allow it; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Change visible identity only when narrative conditions allow it",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:429",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-disguise-quest-names",
      "slug": "npc-disguise-quest-names",
      "name": "NPC disguise quest names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-disguise-quest-names/",
        "ja": "/ja/tools/npc-disguise-quest-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Keep quest logs aligned with player knowledge",
      "task": "Keep quest logs aligned with player knowledge",
      "searchIntent": {
        "primary": "Complete the task: Keep quest logs aligned with player knowledge",
        "queryHypothesis": "npc disguise quest names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep quest logs aligned with player knowledge?",
        "When should npc disguise quest names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep quest logs aligned with player knowledge",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep quest logs aligned with player knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-quest-witness-name-ledger",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Keep quest logs aligned with player knowledge versus Prevent logs from revealing identities the player has not learned; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-social-memory-names",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Keep quest logs aligned with player knowledge versus Decide which observers remember an earlier identity after a quest; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-merchant-duplicate-repair",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Keep quest logs aligned with player knowledge versus Avoid same name shopkeepers in a player's likely travel region; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep quest logs aligned with player knowledge",
        "outline": [
          "Explain the specific decision: Keep quest logs aligned with player knowledge",
          "Define the applicable contract and limits for NPC disguise quest names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep quest logs aligned with player knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep quest logs aligned with player knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:430",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-merchant-duplicate-repair",
      "slug": "npc-merchant-duplicate-repair",
      "name": "NPC merchant duplicate repair",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-merchant-duplicate-repair/",
        "ja": "/ja/tools/npc-merchant-duplicate-repair/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Avoid same name shopkeepers in a player's likely travel region",
      "task": "Avoid same name shopkeepers in a player's likely travel region",
      "searchIntent": {
        "primary": "Complete the task: Avoid same name shopkeepers in a player's likely travel region",
        "queryHypothesis": "npc merchant duplicate repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid same name shopkeepers in a player's likely travel region?",
        "When should npc merchant duplicate repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid same name shopkeepers in a player's likely travel region",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid same name shopkeepers in a player's likely travel region. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-disguise-quest-names",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Avoid same name shopkeepers in a player's likely travel region versus Keep quest logs aligned with player knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-procedural-npc-naming",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Avoid same name shopkeepers in a player's likely travel region versus Generate from explicit settlement rules and uniqueness scope; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Avoid same name shopkeepers in a player's likely travel region versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid same name shopkeepers in a player's likely travel region",
        "outline": [
          "Explain the specific decision: Avoid same name shopkeepers in a player's likely travel region",
          "Define the applicable contract and limits for NPC merchant duplicate repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid same name shopkeepers in a player's likely travel region; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid same name shopkeepers in a player's likely travel region",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:431",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-recruit-list-clarity",
      "slug": "npc-recruit-list-clarity",
      "name": "NPC recruit list clarity",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-recruit-list-clarity/",
        "ja": "/ja/tools/npc-recruit-list-clarity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Separate candidates in compact selection menus",
      "task": "Separate candidates in compact selection menus",
      "searchIntent": {
        "primary": "Complete the task: Separate candidates in compact selection menus",
        "queryHypothesis": "npc recruit list clarity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate candidates in compact selection menus?",
        "When should npc recruit list clarity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate candidates in compact selection menus",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate candidates in compact selection menus. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-party-list-name-disambiguation",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Separate candidates in compact selection menus versus Distinguish shortened names in a compact party display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-batch-review",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate candidates in compact selection menus versus Separate generated candidates from accepted character identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manga-creator-signature",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate candidates in compact selection menus versus Coordinate a pen name with a compact production credit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate candidates in compact selection menus",
        "outline": [
          "Explain the specific decision: Separate candidates in compact selection menus",
          "Define the applicable contract and limits for NPC recruit list clarity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate candidates in compact selection menus; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate candidates in compact selection menus",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:432",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-hostile-friendly-identity",
      "slug": "npc-hostile-friendly-identity",
      "name": "NPC hostile friendly identity",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-hostile-friendly-identity/",
        "ja": "/ja/tools/npc-hostile-friendly-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Maintain character continuity through allegiance changes",
      "task": "Maintain character continuity through allegiance changes",
      "searchIntent": {
        "primary": "Complete the task: Maintain character continuity through allegiance changes",
        "queryHypothesis": "npc hostile friendly identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to maintain character continuity through allegiance changes?",
        "When should npc hostile friendly identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Maintain character continuity through allegiance changes",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Maintain character continuity through allegiance changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-seasonal-population-naming",
          "score": 0.38333333333333336,
          "sharedProfile": true,
          "difference": "Maintain character continuity through allegiance changes versus Maintain continuity through time based population changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estrangement-address-reversal",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Maintain character continuity through allegiance changes versus Restore distance through deliberate naming changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-faction-crossing-character-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Maintain character continuity through allegiance changes versus Keep allegiance changes from creating duplicate identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Maintain character continuity through allegiance changes",
        "outline": [
          "Explain the specific decision: Maintain character continuity through allegiance changes",
          "Define the applicable contract and limits for NPC hostile friendly identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Maintain character continuity through allegiance changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Maintain character continuity through allegiance changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:433",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-death-memorial-names",
      "slug": "npc-death-memorial-names",
      "name": "NPC death memorial names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-death-memorial-names/",
        "ja": "/ja/tools/npc-death-memorial-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Preserve names in graves, journals and relationship records",
      "task": "Preserve names in graves, journals and relationship records",
      "searchIntent": {
        "primary": "Complete the task: Preserve names in graves, journals and relationship records",
        "queryHypothesis": "npc death memorial names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve names in graves, journals and relationship records?",
        "When should npc death memorial names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve names in graves, journals and relationship records",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve names in graves, journals and relationship records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Preserve names in graves, journals and relationship records versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-expansion-pack-collisions",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Preserve names in graves, journals and relationship records versus Compare a new cast against base game identity records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-obituary-clue",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Preserve names in graves, journals and relationship records versus Reconcile dates, names and witnesses in fictional records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve names in graves, journals and relationship records",
        "outline": [
          "Explain the specific decision: Preserve names in graves, journals and relationship records",
          "Define the applicable contract and limits for NPC death memorial names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve names in graves, journals and relationship records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve names in graves, journals and relationship records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:434",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-inherited-questgiver-title",
      "slug": "npc-inherited-questgiver-title",
      "name": "NPC inherited questgiver title",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-inherited-questgiver-title/",
        "ja": "/ja/tools/npc-inherited-questgiver-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Transfer office without merging save identities",
      "task": "Transfer office without merging save identities",
      "searchIntent": {
        "primary": "Complete the task: Transfer office without merging save identities",
        "queryHypothesis": "npc inherited questgiver title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transfer office without merging save identities?",
        "When should npc inherited questgiver title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transfer office without merging save identities",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transfer office without merging save identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Transfer office without merging save identities versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-motion-comic-recap-audio-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Transfer office without merging save identities versus Reintroduce names without narrating hidden identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-passes-on-title",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Transfer office without merging save identities versus Preserve the outgoing and incoming holders' distinct identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transfer office without merging save identities",
        "outline": [
          "Explain the specific decision: Transfer office without merging save identities",
          "Define the applicable contract and limits for NPC inherited questgiver title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transfer office without merging save identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transfer office without merging save identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:435",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-generated-biography-name-fit",
      "slug": "npc-generated-biography-name-fit",
      "name": "NPC generated biography name fit",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-generated-biography-name-fit/",
        "ja": "/ja/tools/npc-generated-biography-name-fit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Check a generated name against explicit biography fields",
      "task": "Check a generated name against explicit biography fields",
      "searchIntent": {
        "primary": "Complete the task: Check a generated name against explicit biography fields",
        "queryHypothesis": "npc generated biography name fit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check a generated name against explicit biography fields?",
        "When should npc generated biography name fit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check a generated name against explicit biography fields",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check a generated name against explicit biography fields. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Check a generated name against explicit biography fields versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Check a generated name against explicit biography fields versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-persistence-across-saves",
          "score": 0.13125,
          "sharedProfile": true,
          "difference": "Check a generated name against explicit biography fields versus Serialize generated names with stable IDs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check a generated name against explicit biography fields",
        "outline": [
          "Explain the specific decision: Check a generated name against explicit biography fields",
          "Define the applicable contract and limits for NPC generated biography name fit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check a generated name against explicit biography fields; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check a generated name against explicit biography fields",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:436",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-pronunciation-metadata",
      "slug": "npc-pronunciation-metadata",
      "name": "NPC pronunciation metadata",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-pronunciation-metadata/",
        "ja": "/ja/tools/npc-pronunciation-metadata/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Export approved pronunciations with dialogue assets",
      "task": "Export approved pronunciations with dialogue assets",
      "searchIntent": {
        "primary": "Complete the task: Export approved pronunciations with dialogue assets",
        "queryHypothesis": "npc pronunciation metadata",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export approved pronunciations with dialogue assets?",
        "When should npc pronunciation metadata be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export approved pronunciations with dialogue assets",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export approved pronunciations with dialogue assets. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-motion-comic-spoken-cast-separation",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Export approved pronunciations with dialogue assets versus Compare approved pronunciations under rapid dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-letterer-handoff-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Export approved pronunciations with dialogue assets versus Export approved spellings, pronunciations and forbidden variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Export approved pronunciations with dialogue assets versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export approved pronunciations with dialogue assets",
        "outline": [
          "Explain the specific decision: Export approved pronunciations with dialogue assets",
          "Define the applicable contract and limits for NPC pronunciation metadata",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export approved pronunciations with dialogue assets; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export approved pronunciations with dialogue assets",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:437",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-locale-fallback-names",
      "slug": "npc-locale-fallback-names",
      "name": "NPC locale fallback names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-locale-fallback-names/",
        "ja": "/ja/tools/npc-locale-fallback-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Define a reviewed fallback when a locale is incomplete",
      "task": "Define a reviewed fallback when a locale is incomplete",
      "searchIntent": {
        "primary": "Complete the task: Define a reviewed fallback when a locale is incomplete",
        "queryHypothesis": "npc locale fallback names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define a reviewed fallback when a locale is incomplete?",
        "When should npc locale fallback names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define a reviewed fallback when a locale is incomplete",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define a reviewed fallback when a locale is incomplete. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Define a reviewed fallback when a locale is incomplete versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-translation-table",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define a reviewed fallback when a locale is incomplete versus Export locale variants with review and fallback status; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-off-panel-name-reference",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Define a reviewed fallback when a locale is incomplete versus Maintain clarity when a speaker or listener is unseen; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define a reviewed fallback when a locale is incomplete",
        "outline": [
          "Explain the specific decision: Define a reviewed fallback when a locale is incomplete",
          "Define the applicable contract and limits for NPC locale fallback names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define a reviewed fallback when a locale is incomplete; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define a reviewed fallback when a locale is incomplete",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:438",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-expansion-pack-collisions",
      "slug": "npc-expansion-pack-collisions",
      "name": "NPC expansion pack collisions",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-expansion-pack-collisions/",
        "ja": "/ja/tools/npc-expansion-pack-collisions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Compare a new cast against base game identity records",
      "task": "Compare a new cast against base game identity records",
      "searchIntent": {
        "primary": "Complete the task: Compare a new cast against base game identity records",
        "queryHypothesis": "npc expansion pack collisions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare a new cast against base game identity records?",
        "When should npc expansion pack collisions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare a new cast against base game identity records",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare a new cast against base game identity records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-version-restore",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare a new cast against base game identity records versus Restore parameters and identity records from an explicit version; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-new-cast-collision",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare a new cast against base game identity records versus Compare a proposed cast against previous installments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-death-memorial-names",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Compare a new cast against base game identity records versus Preserve names in graves, journals and relationship records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare a new cast against base game identity records",
        "outline": [
          "Explain the specific decision: Compare a new cast against base game identity records",
          "Define the applicable contract and limits for NPC expansion pack collisions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare a new cast against base game identity records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare a new cast against base game identity records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:442",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-boss-true-name-reveal",
      "slug": "boss-true-name-reveal",
      "name": "Boss true name reveal",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/boss-true-name-reveal/",
        "ja": "/ja/tools/boss-true-name-reveal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Coordinate combat labels and later identity discoveries",
      "task": "Coordinate combat labels and later identity discoveries",
      "searchIntent": {
        "primary": "Complete the task: Coordinate combat labels and later identity discoveries",
        "queryHypothesis": "boss true name reveal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate combat labels and later identity discoveries?",
        "When should boss true name reveal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate combat labels and later identity discoveries",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate combat labels and later identity discoveries. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Coordinate combat labels and later identity discoveries versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonverbal-character-naming",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Coordinate combat labels and later identity discoveries versus Separate communicated identity from other characters' labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-reveal-splash",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Coordinate combat labels and later identity discoveries versus Compare reveal text hierarchy with prior identity clues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate combat labels and later identity discoveries",
        "outline": [
          "Explain the specific decision: Coordinate combat labels and later identity discoveries",
          "Define the applicable contract and limits for Boss true name reveal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate combat labels and later identity discoveries; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate combat labels and later identity discoveries",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:443",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-quest-witness-name-ledger",
      "slug": "quest-witness-name-ledger",
      "name": "Quest witness name ledger",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/quest-witness-name-ledger/",
        "ja": "/ja/tools/quest-witness-name-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Prevent logs from revealing identities the player has not learned",
      "task": "Prevent logs from revealing identities the player has not learned",
      "searchIntent": {
        "primary": "Complete the task: Prevent logs from revealing identities the player has not learned",
        "queryHypothesis": "quest witness name ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent logs from revealing identities the player has not learned?",
        "When should quest witness name ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent logs from revealing identities the player has not learned",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent logs from revealing identities the player has not learned. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-disguise-quest-names",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Prevent logs from revealing identities the player has not learned versus Keep quest logs aligned with player knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-bargain-witness-ledger",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Prevent logs from revealing identities the player has not learned versus Record who witnessed a pact and which terms they know; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-space-station-transient-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Prevent logs from revealing identities the player has not learned versus Reconcile visitor logs with locally used identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent logs from revealing identities the player has not learned",
        "outline": [
          "Explain the specific decision: Prevent logs from revealing identities the player has not learned",
          "Define the applicable contract and limits for Quest witness name ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent logs from revealing identities the player has not learned; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent logs from revealing identities the player has not learned",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:444",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-dialogue-variable-name-safety",
      "slug": "dialogue-variable-name-safety",
      "name": "Dialogue variable name safety",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/dialogue-variable-name-safety/",
        "ja": "/ja/tools/dialogue-variable-name-safety/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Insert player and NPC display names as text rather than executable markup",
      "task": "Insert player and NPC display names as text rather than executable markup",
      "searchIntent": {
        "primary": "Complete the task: Insert player and NPC display names as text rather than executable markup",
        "queryHypothesis": "dialogue variable name safety",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to insert player and NPC display names as text rather than executable markup?",
        "When should dialogue variable name safety be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Insert player and NPC display names as text rather than executable markup",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Insert player and NPC display names as text rather than executable markup. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dialogue-nameplate-overflow",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Insert player and NPC display names as text rather than executable markup versus Compare wrapping, scaling and abbreviated display strategies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-dialogue-tag-rename",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Insert player and NPC display names as text rather than executable markup versus Distinguish script labels from spoken name text; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-name-dialogue-grammar",
          "score": 0.10421052631578948,
          "sharedProfile": true,
          "difference": "Insert player and NPC display names as text rather than executable markup versus Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Insert player and NPC display names as text rather than executable markup",
        "outline": [
          "Explain the specific decision: Insert player and NPC display names as text rather than executable markup",
          "Define the applicable contract and limits for Dialogue variable name safety",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Insert player and NPC display names as text rather than executable markup; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Insert player and NPC display names as text rather than executable markup",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:445",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-rpg-journal-name-refresh",
      "slug": "rpg-journal-name-refresh",
      "name": "RPG journal name refresh",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/rpg-journal-name-refresh/",
        "ja": "/ja/tools/rpg-journal-name-refresh/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Update references after an identity reveal without rewriting historical facts",
      "task": "Update references after an identity reveal without rewriting historical facts",
      "searchIntent": {
        "primary": "Complete the task: Update references after an identity reveal without rewriting historical facts",
        "queryHypothesis": "rpg journal name refresh",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update references after an identity reveal without rewriting historical facts?",
        "When should rpg journal name refresh be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update references after an identity reveal without rewriting historical facts",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update references after an identity reveal without rewriting historical facts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-student-council-office-names",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Update references after an identity reveal without rewriting historical facts versus Update office references after elections without replacing character IDs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mystery-reveal-name-recap",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Update references after an identity reveal without rewriting historical facts versus Explain the identity solution without contradicting earlier references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Update references after an identity reveal without rewriting historical facts versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update references after an identity reveal without rewriting historical facts",
        "outline": [
          "Explain the specific decision: Update references after an identity reveal without rewriting historical facts",
          "Define the applicable contract and limits for RPG journal name refresh",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update references after an identity reveal without rewriting historical facts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update references after an identity reveal without rewriting historical facts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:446",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-game-cast-localization-keys",
      "slug": "game-cast-localization-keys",
      "name": "Game cast localization keys",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-cast-localization-keys/",
        "ja": "/ja/tools/game-cast-localization-keys/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Export stable keys independently of translated display names",
      "task": "Export stable keys independently of translated display names",
      "searchIntent": {
        "primary": "Complete the task: Export stable keys independently of translated display names",
        "queryHypothesis": "game cast localization keys",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export stable keys independently of translated display names?",
        "When should game cast localization keys be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export stable keys independently of translated display names",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export stable keys independently of translated display names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.30208333333333337,
          "sharedProfile": true,
          "difference": "Export stable keys independently of translated display names versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-engine-name-key-migration",
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Export stable keys independently of translated display names versus Keep resource keys stable during display name revisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-character-id-export",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Export stable keys independently of translated display names versus Produce stable keys and display strings for production pipelines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export stable keys independently of translated display names",
        "outline": [
          "Explain the specific decision: Export stable keys independently of translated display names",
          "Define the applicable contract and limits for Game cast localization keys",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export stable keys independently of translated display names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export stable keys independently of translated display names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:447",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-game-codex-spoiler-names",
      "slug": "game-codex-spoiler-names",
      "name": "Game codex spoiler names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-codex-spoiler-names/",
        "ja": "/ja/tools/game-codex-spoiler-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Gate names by discovery flags with explicit fallback labels",
      "task": "Gate names by discovery flags with explicit fallback labels",
      "searchIntent": {
        "primary": "Complete the task: Gate names by discovery flags with explicit fallback labels",
        "queryHypothesis": "game codex spoiler names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to gate names by discovery flags with explicit fallback labels?",
        "When should game codex spoiler names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Gate names by discovery flags with explicit fallback labels",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Gate names by discovery flags with explicit fallback labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-accessibility-labels",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Gate names by discovery flags with explicit fallback labels versus Provide readable labels alongside compact visual names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-translation-table",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Gate names by discovery flags with explicit fallback labels versus Export locale variants with review and fallback status; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prophecy-title-spoiler",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Gate names by discovery flags with explicit fallback labels versus Avoid exposing the future role in early character labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Gate names by discovery flags with explicit fallback labels",
        "outline": [
          "Explain the specific decision: Gate names by discovery flags with explicit fallback labels",
          "Define the applicable contract and limits for Game codex spoiler names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Gate names by discovery flags with explicit fallback labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Gate names by discovery flags with explicit fallback labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:448",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-game-name-import-validation",
      "slug": "game-name-import-validation",
      "name": "Game name import validation",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-name-import-validation/",
        "ja": "/ja/tools/game-name-import-validation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Reject malformed datasets without silently dropping characters",
      "task": "Reject malformed datasets without silently dropping characters",
      "searchIntent": {
        "primary": "Complete the task: Reject malformed datasets without silently dropping characters",
        "queryHypothesis": "game name import validation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reject malformed datasets without silently dropping characters?",
        "When should game name import validation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reject malformed datasets without silently dropping characters",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reject malformed datasets without silently dropping characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-records-mismatch",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Reject malformed datasets without silently dropping characters versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-source-contradiction",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Reject malformed datasets without silently dropping characters versus Compare conflicting references without silently selecting one; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Reject malformed datasets without silently dropping characters versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reject malformed datasets without silently dropping characters",
        "outline": [
          "Explain the specific decision: Reject malformed datasets without silently dropping characters",
          "Define the applicable contract and limits for Game name import validation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reject malformed datasets without silently dropping characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reject malformed datasets without silently dropping characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:449",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-game-name-accessibility-labels",
      "slug": "game-name-accessibility-labels",
      "name": "Game name accessibility labels",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-name-accessibility-labels/",
        "ja": "/ja/tools/game-name-accessibility-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Provide readable labels alongside compact visual names",
      "task": "Provide readable labels alongside compact visual names",
      "searchIntent": {
        "primary": "Complete the task: Provide readable labels alongside compact visual names",
        "queryHypothesis": "game name accessibility labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide readable labels alongside compact visual names?",
        "When should game name accessibility labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide readable labels alongside compact visual names",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide readable labels alongside compact visual names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-photo-mode-labels",
          "score": 0.1990909090909091,
          "sharedProfile": false,
          "difference": "Provide readable labels alongside compact visual names versus Keep optional labels consistent with story spoiler settings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-accessibility",
          "score": 0.1875,
          "sharedProfile": false,
          "difference": "Provide readable labels alongside compact visual names versus Provide a fair alternative when a clue relies on visual or audio distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-codex-spoiler-names",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Provide readable labels alongside compact visual names versus Gate names by discovery flags with explicit fallback labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide readable labels alongside compact visual names",
        "outline": [
          "Explain the specific decision: Provide readable labels alongside compact visual names",
          "Define the applicable contract and limits for Game name accessibility labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide readable labels alongside compact visual names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide readable labels alongside compact visual names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:450",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-game-narrative-identity-tests",
      "slug": "game-narrative-identity-tests",
      "name": "Game narrative identity tests",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/game-narrative-identity-tests/",
        "ja": "/ja/tools/game-narrative-identity-tests/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Build state fixtures for names before and after quest events",
      "task": "Build state fixtures for names before and after quest events",
      "searchIntent": {
        "primary": "Complete the task: Build state fixtures for names before and after quest events",
        "queryHypothesis": "game narrative identity tests",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build state fixtures for names before and after quest events?",
        "When should game narrative identity tests be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build state fixtures for names before and after quest events",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build state fixtures for names before and after quest events. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-test-revision-comparison",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Build state fixtures for names before and after quest events versus Compare before and after candidates with disclosed test conditions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-dialogue-history-identity",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Build state fixtures for names before and after quest events versus Decide whether past lines retain historically visible names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-elemental-identity-convention",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Build state fixtures for names before and after quest events versus Build explicit fictional naming rules beyond a single elemental adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build state fixtures for names before and after quest events",
        "outline": [
          "Explain the specific decision: Build state fixtures for names before and after quest events",
          "Define the applicable contract and limits for Game narrative identity tests",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build state fixtures for names before and after quest events; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build state fixtures for names before and after quest events",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:451",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-player-name-dialogue-grammar",
      "slug": "player-name-dialogue-grammar",
      "name": "Player name dialogue grammar",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/player-name-dialogue-grammar/",
        "ja": "/ja/tools/player-name-dialogue-grammar/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Define locale specific sentence patterns without inferring gender from names",
      "task": "Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants.",
      "searchIntent": {
        "primary": "Complete the task: Define locale specific sentence patterns without inferring gender from names",
        "queryHypothesis": "player name dialogue grammar",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define locale specific sentence patterns without inferring gender from names?",
        "When should player name dialogue grammar be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "identities",
          "use": "Player or fixture IDs and exact approved name forms."
        },
        {
          "key": "forms",
          "use": "Explicit authored case/reference keys per identity and locale."
        },
        {
          "key": "templates",
          "use": "Stable line ID, locale and text using a small documented token syntax."
        },
        {
          "key": "variantRules",
          "use": "Which fixture identities and grammatical keys each line must support."
        }
      ],
      "rules": [
        "Only documented literal tokens are parsed; no code evaluation.",
        "Unknown or missing form keys remain unresolved, not guessed.",
        "Preserve special characters as text and escape HTML at rendering boundaries.",
        "Do not infer gender, pronouns, honorifics or declensions from a name.",
        "Different locales require independent authored lines and forms.",
        "Export unresolved line/identity combinations separately from rendered text."
      ],
      "requiredData": [
        {
          "description": "User-supplied locale templates",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Explicit grammatical/referring forms and non-sensitive fixture identities",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Only documented literal tokens are parsed; no code evaluation.",
        "Unknown or missing form keys remain unresolved, not guessed.",
        "Preserve special characters as text and escape HTML at rendering boundaries.",
        "Do not infer gender, pronouns, honorifics or declensions from a name.",
        "Different locales require independent authored lines and forms.",
        "Export unresolved line/identity combinations separately from rendered text."
      ],
      "outputs": [
        "Per-line per-fixture rendered dialogue",
        "Missing-token/key/locale diagnostics",
        "Author handoff with template versions and exact supplied forms"
      ],
      "capabilities": [
        "Show all fixture identities affected by a missing form, including names with punctuation or markup characters.",
        "Test a pronoun-independent alternative without inventing a name-based grammar rule."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The user must render dialogue safely with supplied inflected or reference forms; neither naming generation nor cross-edition mappings validates template completeness.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "character-localization-name-map",
          "difference": "Localization maps identities across editions; this task parses tokenized dialogue and requires author-supplied grammatical forms without guessing gender or morphology."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-correction-dialogue",
          "score": 0.128125,
          "sharedProfile": false,
          "difference": "Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants. versus Draft corrections that fit the character and scene stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-chosen-name-review",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants. versus Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-vocative-pacing",
          "score": 0.10823529411764705,
          "sharedProfile": false,
          "difference": "Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants. versus Measure recorded name duration against a scene timing budget; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A name slot is a grammatical interface, not permission to infer who the player is.",
        "outline": [
          "Define the token contract",
          "Supply grammatical choices deliberately",
          "Fictional scene: a player name on a mission board",
          "Test punctuation and missing forms",
          "Localize the sentence as well as the slot"
        ],
        "story": "A game writer finds that a congratulatory line assumes a title for every player name. A player chooses a punctuation-bearing mononym. The team authors an alternative sentence and explicit optional reference forms instead of classifying the player from the spelling.",
        "storyAnalysis": "A different name could make the old line appear correct while leaving the template contract broken for the next player.",
        "evidence": "Original template fixtures; no claim of a universal grammar or a game-engine integration.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/dialogue.md",
        "localizedBodies": {
          "en": "content/en/dialogue.md",
          "ja": "content/ja/dialogue.md"
        }
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Markup-looking input is displayed as literal text.",
        "A missing authored form blocks that line and never substitutes a guessed form.",
        "Unsupported tokens and duplicated line IDs fail with locations.",
        "Changing a supplied form updates only lines using that key.",
        "No identity input automatically establishes gender or pronouns."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:453",
      "profileSource": "data/profiles.json#game-characters",
      "specBatch": "batch-02",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "dialogue",
        "engineFiles": [
          "web/dialogue-slots.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/dialogue.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "fixtures",
          "label": [
            "Player-name fixtures · JSON",
            "プレイヤー名の例・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"courier\",\n    \"name\": \"Mira\",\n    \"forms\": {\n      \"en\": {\n        \"subject\": \"They\",\n        \"possessive\": \"their\"\n      },\n      \"ja\": {\n        \"call\": \"ミラさん\"\n      }\n    }\n  },\n  {\n    \"id\": \"visitor\",\n    \"name\": \"<Aven & Co.>\",\n    \"forms\": {\n      \"en\": {\n        \"subject\": \"He\",\n        \"possessive\": \"his\"\n      }\n    }\n  }\n]",
          "help": [
            "Each object: id, exact name, forms keyed by locale and literal form key. Name, gender and grammar are not inferred. The visitor intentionally lacks a Japanese call form.",
            "各オブジェクトはid、正確なname、言語と表記キーごとのforms。名前・性別・文法は推測しません。visitorの日本語の呼称は意図的に未入力です。"
          ]
        },
        {
          "key": "templates",
          "label": [
            "Authored sentence templates · JSON",
            "作者が書く台詞テンプレート・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"welcome-en\",\n    \"locale\": \"en\",\n    \"text\": \"Welcome, {{name}}.\"\n  },\n  {\n    \"id\": \"parcel-en\",\n    \"locale\": \"en\",\n    \"text\": \"{{subject}} left {{possessive}} parcel for {{name}}.\"\n  },\n  {\n    \"id\": \"welcome-ja\",\n    \"locale\": \"ja\",\n    \"text\": \"{{call}}、受付へどうぞ。\"\n  }\n]",
          "help": [
            "Each object: id, exact locale label, text. Tokens use {{name}} or an explicit ASCII form key such as {{subject}}. No expressions, nested tokens, automatic translation or locale fallback.",
            "各オブジェクトはid、正確なlocale、text。{{name}}または{{subject}}のような明示したASCIIキーを使います。式・入れ子・自動翻訳・別言語からの補完は行いません。"
          ]
        },
        {
          "key": "fixtureIds",
          "label": [
            "Fixture IDs · blank = all",
            "人物ID・空欄は全員"
          ],
          "type": "text",
          "default": "",
          "help": [
            "Comma-separated IDs, not names. Up to 120 scoped line/fixture combinations.",
            "名前ではなく、カンマ区切りのID。対象とする台詞・人物の組合せは最大120件。"
          ]
        },
        {
          "key": "localeFilter",
          "label": [
            "Exact locale label · blank = all",
            "正確な言語ラベル・空欄は全言語"
          ],
          "type": "text",
          "default": "",
          "help": null
        }
      ]
    },
    {
      "id": "nw-player-chosen-name-review",
      "slug": "player-chosen-name-review",
      "name": "Player chosen name review",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/player-chosen-name-review/",
        "ja": "/ja/tools/player-chosen-name-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Game writers and developers integrating player-authored names into story interfaces and save identifiers.",
      "scenario": "Two distinct chosen displays survive the input screen but collapse to the same storage key after a later transformation; the author needs an end-to-end naming contract.",
      "task": "Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently.",
      "searchIntent": {
        "primary": "Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently.",
        "queryHypothesis": "player chosen name review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Which pipeline stage collapsed two distinct player displays into one key?",
        "Can a storage key be repaired while preserving both chosen displays?"
      ],
      "inputs": [
        {
          "key": "fixtures",
          "use": "Stable fixture IDs and exact creator-supplied player display strings."
        },
        {
          "key": "stages",
          "use": "Ordered, explicit transform or validation records with exact supported policies and size units."
        },
        {
          "key": "reservedKeys",
          "use": "Author-declared reserved strings in a specified stage scope."
        },
        {
          "key": "keyStage",
          "use": "Select which stage output is used as the identifier for collision checking."
        },
        {
          "key": "expectedRoundTrips",
          "use": "Optional explicit expected return displays; unknown is not assumed equal."
        }
      ],
      "rules": [
        "Preserve raw display, every stage output and the exact rule that rejects or changes it.",
        "No implicit trimming, case change, normalization, truncation or transliteration.",
        "Reject unsupported stage operations instead of evaluating arbitrary code.",
        "A display can pass its own checks while two fixtures collide at a later declared key stage.",
        "Report collisions as groups of fixture IDs, never merge their identity records.",
        "Use explicit code-point or grapheme limits; do not label a limit as cultural appropriateness.",
        "Reserved strings are project declarations, not a real-world prohibition list.",
        "Do not certify a particular game engine or destination without an actual integration check."
      ],
      "requiredData": [
        {
          "description": "Original Unicode boundary/collision fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Author-defined pipeline and reserved strings; no profanity or cultural blacklist dataset",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Preserve raw display, every stage output and the exact rule that rejects or changes it.",
        "No implicit trimming, case change, normalization, truncation or transliteration.",
        "Reject unsupported stage operations instead of evaluating arbitrary code.",
        "A display can pass its own checks while two fixtures collide at a later declared key stage.",
        "Report collisions as groups of fixture IDs, never merge their identity records.",
        "Use explicit code-point or grapheme limits; do not label a limit as cultural appropriateness.",
        "Reserved strings are project declarations, not a real-world prohibition list.",
        "Do not certify a particular game engine or destination without an actual integration check."
      ],
      "outputs": [
        "Raw-to-stage trace and first failing rule",
        "Declared key collision groups with preserved source displays",
        "Expected-round-trip mismatch or unknown state",
        "Private implementation handoff for the selected pipeline"
      ],
      "capabilities": [
        "Locate a collision introduced after a successful input-screen validation.",
        "Show that repairing a storage-key rule can preserve both chosen displays instead of forcing a rename."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The task audits a sequence of technical identity boundaries and non-injective transformations. A name-length filter or dialogue slot alone cannot reveal which downstream stage lost the distinction.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "player-name-dialogue-grammar",
          "difference": "Dialogue substitutes explicit forms into authored sentences. This workbench applies an ordered declared transformation/validation pipeline, preserves raw displays and reports per-stage rejection and cross-fixture storage-key collisions; no culture or universal name-validity judgment is made."
        }
      },
      "nearestTools": [
        {
          "id": "nw-player-name-dialogue-grammar",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently. versus Validate authored dialogue templates and explicit grammatical form slots for player-chosen names across scene variants.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-self-chosen-character-name",
          "score": 0.11704545454545454,
          "sharedProfile": false,
          "difference": "Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently. versus Design a chosen identity with consent and viewpoint boundaries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-collaboration-review",
          "score": 0.09826086956521739,
          "sharedProfile": false,
          "difference": "Trace creator-supplied player-name fixtures through an explicit display/storage pipeline and detect stage failures or key collisions without rewriting the chosen display silently. versus Prepare a commentable package without sending it to anyone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A chosen display should not be blamed for a later system that silently merges identities.",
        "outline": [
          "Follow the name past the input screen",
          "A key is not the visible identity",
          "Original scene: two save slots with one normalized key",
          "Inspect the exact stage that changed the result",
          "Preserve unknown round trips"
        ],
        "story": "Two players in an invented co-op story keep distinct displays but a lowercasing storage rule maps them to one slot. The writer changes the key contract, rather than declaring that one player’s name is less legitimate.",
        "storyAnalysis": "A different font or sentence template does not repair a storage collision. The naming decision includes preserving the display while choosing a technically unambiguous internal key.",
        "evidence": "Original finite pipeline fixtures; no claim of actual user data, cultural prohibition or external integration.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/playerPipeline.md",
        "localizedBodies": {
          "en": "content/en/playerPipeline.md",
          "ja": "content/ja/playerPipeline.md"
        }
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Swapping trim and length-validation stages changes the trace in the expected way.",
        "Two distinct displays that collapse under declared lowercase produce one reported collision group and two preserved IDs.",
        "No undeclared operation changes a string.",
        "Unsupported operations and invalid stage references fail explicitly.",
        "A missing expected round trip is unknown, not a success.",
        "Export states pipeline scope and does not claim cultural, trademark or real-engine approval."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:454",
      "profileSource": "data/profiles.json#game-characters",
      "specBatch": "batch-03",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Dedicated state, scoped references and failure handling; no production time or cost estimate fabricated."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-game-name-unicode-normalization",
          "input": "Exact fixture IDs/displays, explicit normalize form/source stage and key-stage selection.",
          "rule": "No implicit normalization; raw display remains unchanged. Compare exact available stage outputs, preserve distinct IDs even when normalized keys match.",
          "output": "Per-stage trace, collision groups with source displays, unknown/known modeled return states and a private implementation handoff.",
          "acceptance": "Decomposed and precomposed displays stay distinct under identity and collide under explicit NFC; separate fixtureId key preserves both displays. Unsupported operations fail.",
          "evidence": [
            "PIPELINE-01",
            "PIPELINE-03",
            "PIPELINE-04",
            "PIPELINE-07",
            "reports/player-pipeline-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-name-data-duplicate-normalization",
          "input": "Exact fixture IDs/displays, explicit normalize form/source stage and key-stage selection.",
          "rule": "No implicit normalization; raw display remains unchanged. Compare exact available stage outputs, preserve distinct IDs even when normalized keys match.",
          "output": "Per-stage trace, collision groups with source displays, unknown/known modeled return states and a private implementation handoff.",
          "acceptance": "Decomposed and precomposed displays stay distinct under identity and collide under explicit NFC; separate fixtureId key preserves both displays. Unsupported operations fail.",
          "evidence": [
            "PIPELINE-01",
            "PIPELINE-03",
            "PIPELINE-04",
            "PIPELINE-07",
            "reports/player-pipeline-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "playerPipeline",
        "engineFiles": [
          "web/player-name-pipeline.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/player-pipeline.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "fixtures",
          "label": [
            "Chosen display fixtures · JSON",
            "選んだ表示の入力例・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"p1\",\n    \"display\": \"Mira\"\n  },\n  {\n    \"id\": \"p2\",\n    \"display\": \"mira\"\n  },\n  {\n    \"id\": \"p3\",\n    \"display\": \"  Kiri  \"\n  },\n  {\n    \"id\": \"p4\",\n    \"display\": \"青́\"\n  }\n]",
          "help": [
            "id, exact display. 1–50 fictional or creator-supplied examples, including explicit empty strings. No generated player research.",
            "idと正確なdisplay。1〜50件の創作例か作者の入力です。空文字も指定できます。プレイヤー調査の捏造はしません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "stages",
          "label": [
            "Ordered stages · JSON",
            "順序のある段階・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"inputCheck\",\n    \"from\": \"raw\",\n    \"op\": \"length\",\n    \"unit\": \"grapheme\",\n    \"min\": 1,\n    \"max\": 12\n  },\n  {\n    \"id\": \"keyTrim\",\n    \"from\": \"inputCheck\",\n    \"op\": \"trim\"\n  },\n  {\n    \"id\": \"key\",\n    \"from\": \"keyTrim\",\n    \"op\": \"lowercase\"\n  },\n  {\n    \"id\": \"loadedDisplay\",\n    \"from\": \"raw\",\n    \"op\": \"identity\"\n  }\n]",
          "help": [
            "Each id/from/op is explicit. from is raw or an earlier stage. Operations: identity, trim, lowercase, normalize (form), length (unit/min/max), truncate (unit/max), fixtureId. Nothing runs implicitly.",
            "id/from/opを明示します。fromはrawか前の段階です。操作はidentity、trim、lowercase、normalize（form）、length（unit/min/max）、truncate（unit/max）、fixtureId。暗黙の処理はありません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "keyStage",
          "label": [
            "Identifier stage ID",
            "識別キーの段階ID"
          ],
          "type": "text",
          "default": "key",
          "help": [
            "Exact equality at this existing stage defines a collision. IDs are not merged.",
            "登録したこの段階での完全一致を衝突とします。個別IDは統合しません。"
          ]
        },
        {
          "key": "returnStage",
          "label": [
            "Return-display stage ID",
            "戻る表示の段階ID"
          ],
          "type": "text",
          "default": "loadedDisplay",
          "help": [
            "Compare this output with supplied expectations; raw is also permitted. This models a contract, not an actual engine read-back.",
            "この出力と入力した期待値を比較します。rawも使えます。実際のエンジンから読み戻す検査ではありません。"
          ]
        },
        {
          "key": "reservedKeys",
          "label": [
            "Stage-scoped reserved values · JSON",
            "段階ごとの予約値・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "stage, exact value, authored reason. Exact case/space match only; no profanity or culture blacklist.",
            "stage、正確なvalue、作者のreason。大文字小文字と空白も区別します。差別語や文化の禁止一覧ではありません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "expectedRoundTrips",
          "label": [
            "Expected return displays · JSON",
            "期待する戻り表示・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"fixture\": \"p1\",\n    \"value\": \"Mira\"\n  },\n  {\n    \"fixture\": \"p2\",\n    \"value\": \"mira\"\n  }\n]",
          "help": [
            "fixture and exact value. Omitted fixtures remain unknown, never assumed successful.",
            "fixtureと正確なvalue。指定のない例はunknownで、成功とみなしません。"
          ],
          "maxLength": 150000
        }
      ]
    },
    {
      "id": "nw-save-migration-renamed-npc",
      "slug": "save-migration-renamed-npc",
      "name": "Save migration renamed NPC",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/save-migration-renamed-npc/",
        "ja": "/ja/tools/save-migration-renamed-npc/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Preserve old save IDs while changing approved display names",
      "task": "Preserve old save IDs while changing approved display names",
      "searchIntent": {
        "primary": "Complete the task: Preserve old save IDs while changing approved display names",
        "queryHypothesis": "save migration renamed npc",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve old save IDs while changing approved display names?",
        "When should save migration renamed npc be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve old save IDs while changing approved display names",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve old save IDs while changing approved display names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-migration-between-towns",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Preserve old save IDs while changing approved display names versus Preserve individual names while updating local forms of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Preserve old save IDs while changing approved display names versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-persistence-across-saves",
          "score": 0.1222222222222222,
          "sharedProfile": true,
          "difference": "Preserve old save IDs while changing approved display names versus Serialize generated names with stable IDs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve old save IDs while changing approved display names",
        "outline": [
          "Explain the specific decision: Preserve old save IDs while changing approved display names",
          "Define the applicable contract and limits for Save migration renamed NPC",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve old save IDs while changing approved display names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve old save IDs while changing approved display names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:455",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-companion-nickname-unlock",
      "slug": "companion-nickname-unlock",
      "name": "Companion nickname unlock",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/companion-nickname-unlock/",
        "ja": "/ja/tools/companion-nickname-unlock/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Tie private address forms to explicit relationship flags",
      "task": "Tie private address forms to explicit relationship flags",
      "searchIntent": {
        "primary": "Complete the task: Tie private address forms to explicit relationship flags",
        "queryHypothesis": "companion nickname unlock",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie private address forms to explicit relationship flags?",
        "When should companion nickname unlock be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie private address forms to explicit relationship flags",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie private address forms to explicit relationship flags. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Tie private address forms to explicit relationship flags versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-intimate-nickname-boundaries",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Tie private address forms to explicit relationship flags versus Restrict private names to authorized speakers and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-social-register-naming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Tie private address forms to explicit relationship flags versus Compare public formality with private address without stereotyping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie private address forms to explicit relationship flags",
        "outline": [
          "Explain the specific decision: Tie private address forms to explicit relationship flags",
          "Define the applicable contract and limits for Companion nickname unlock",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie private address forms to explicit relationship flags; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie private address forms to explicit relationship flags",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:456",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-npc-social-memory-names",
      "slug": "npc-social-memory-names",
      "name": "NPC social memory names",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-social-memory-names/",
        "ja": "/ja/tools/npc-social-memory-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Decide which observers remember an earlier identity after a quest",
      "task": "Decide which observers remember an earlier identity after a quest",
      "searchIntent": {
        "primary": "Complete the task: Decide which observers remember an earlier identity after a quest",
        "queryHypothesis": "npc social memory names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide which observers remember an earlier identity after a quest?",
        "When should npc social memory names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide which observers remember an earlier identity after a quest",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide which observers remember an earlier identity after a quest. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-respawn-identity",
          "score": 0.16999999999999998,
          "sharedProfile": true,
          "difference": "Decide which observers remember an earlier identity after a quest versus Decide whether respawned units retain or replace identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Decide which observers remember an earlier identity after a quest versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Decide which observers remember an earlier identity after a quest versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide which observers remember an earlier identity after a quest",
        "outline": [
          "Explain the specific decision: Decide which observers remember an earlier identity after a quest",
          "Define the applicable contract and limits for NPC social memory names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide which observers remember an earlier identity after a quest; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide which observers remember an earlier identity after a quest",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:457",
      "profileSource": "data/profiles.json#game-characters"
    },
    {
      "id": "nw-character-name-hud-budget",
      "slug": "character-name-hud-budget",
      "name": "Character name HUD budget",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/character-name-hud-budget/",
        "ja": "/ja/tools/character-name-hud-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Fit approved names to actual rendered HUD dimensions",
      "task": "Fit approved names to actual rendered HUD dimensions",
      "searchIntent": {
        "primary": "Complete the task: Fit approved names to actual rendered HUD dimensions",
        "queryHypothesis": "character name hud budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to fit approved names to actual rendered HUD dimensions?",
        "When should character name hud budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Fit approved names to actual rendered HUD dimensions",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Fit approved names to actual rendered HUD dimensions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-length-budget",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Fit approved names to actual rendered HUD dimensions versus Fit approved forms to actual UI or balloon constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-name-budget",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Fit approved names to actual rendered HUD dimensions versus Allocate memorable naming signals to narratively important roles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Fit approved names to actual rendered HUD dimensions versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Fit approved names to actual rendered HUD dimensions",
        "outline": [
          "Explain the specific decision: Fit approved names to actual rendered HUD dimensions",
          "Define the applicable contract and limits for Character name HUD budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Fit approved names to actual rendered HUD dimensions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Fit approved names to actual rendered HUD dimensions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:460",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-party-list-name-disambiguation",
      "slug": "party-list-name-disambiguation",
      "name": "Party list name disambiguation",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/party-list-name-disambiguation/",
        "ja": "/ja/tools/party-list-name-disambiguation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Distinguish shortened names in a compact party display",
      "task": "Distinguish shortened names in a compact party display",
      "searchIntent": {
        "primary": "Complete the task: Distinguish shortened names in a compact party display",
        "queryHypothesis": "party list name disambiguation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish shortened names in a compact party display?",
        "When should party list name disambiguation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish shortened names in a compact party display",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish shortened names in a compact party display. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-rpg-companion-name-roster",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish shortened names in a compact party display versus Distinguish companions in dialogue and party UI; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-recruit-list-clarity",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Distinguish shortened names in a compact party display versus Separate candidates in compact selection menus; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-expedition-party-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Distinguish shortened names in a compact party display versus Differentiate voice calls under noisy travel scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish shortened names in a compact party display",
        "outline": [
          "Explain the specific decision: Distinguish shortened names in a compact party display",
          "Define the applicable contract and limits for Party list name disambiguation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish shortened names in a compact party display; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish shortened names in a compact party display",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:461",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-combat-log-actor-clarity",
      "slug": "combat-log-actor-clarity",
      "name": "Combat log actor clarity",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/combat-log-actor-clarity/",
        "ja": "/ja/tools/combat-log-actor-clarity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Keep similar actor names distinguishable in fast logs",
      "task": "Keep similar actor names distinguishable in fast logs",
      "searchIntent": {
        "primary": "Complete the task: Keep similar actor names distinguishable in fast logs",
        "queryHypothesis": "combat log actor clarity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep similar actor names distinguishable in fast logs?",
        "When should combat log actor clarity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep similar actor names distinguishable in fast logs",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep similar actor names distinguishable in fast logs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-comic-cover-character-credit",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Keep similar actor names distinguishable in fast logs versus Separate character names from creator and actor credits; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-disguise-quest-names",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Keep similar actor names distinguishable in fast logs versus Keep quest logs aligned with player knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-one-shot-cast-memory-budget",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Keep similar actor names distinguishable in fast logs versus Keep a short session cast distinguishable without a glossary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep similar actor names distinguishable in fast logs",
        "outline": [
          "Explain the specific decision: Keep similar actor names distinguishable in fast logs",
          "Define the applicable contract and limits for Combat log actor clarity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep similar actor names distinguishable in fast logs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep similar actor names distinguishable in fast logs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:462",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-dialogue-nameplate-overflow",
      "slug": "dialogue-nameplate-overflow",
      "name": "Dialogue nameplate overflow",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/dialogue-nameplate-overflow/",
        "ja": "/ja/tools/dialogue-nameplate-overflow/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Compare wrapping, scaling and abbreviated display strategies",
      "task": "Compare wrapping, scaling and abbreviated display strategies",
      "searchIntent": {
        "primary": "Complete the task: Compare wrapping, scaling and abbreviated display strategies",
        "queryHypothesis": "dialogue nameplate overflow",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare wrapping, scaling and abbreviated display strategies?",
        "When should dialogue nameplate overflow be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Preserve logical identity order in stacked nameplates"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare wrapping, scaling and abbreviated display strategies",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings",
        "Ordered accessible label"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare wrapping, scaling and abbreviated display strategies. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-dialogue-variable-name-safety",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Compare wrapping, scaling and abbreviated display strategies versus Insert player and NPC display names as text rather than executable markup; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-correction-dialogue",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare wrapping, scaling and abbreviated display strategies versus Draft corrections that fit the character and scene stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-in-farewell-dialogue",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare wrapping, scaling and abbreviated display strategies versus Compare last address choices against the relationship arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare wrapping, scaling and abbreviated display strategies",
        "outline": [
          "Explain the specific decision: Compare wrapping, scaling and abbreviated display strategies",
          "Define the applicable contract and limits for Dialogue nameplate overflow",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare wrapping, scaling and abbreviated display strategies; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare wrapping, scaling and abbreviated display strategies",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Visual split does not reverse spoken identity"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:463",
      "profileSource": "data/profiles.json#game-ui",
      "absorbedModules": [
        {
          "sourceId": "nw-game-name-multiline-ordering",
          "input": "lineOrder",
          "rule": "Preserve logical identity order in stacked nameplates",
          "output": "Ordered accessible label",
          "acceptance": "Visual split does not reverse spoken identity",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-inventory-owner-name-labels",
      "slug": "inventory-owner-name-labels",
      "name": "Inventory owner name labels",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/inventory-owner-name-labels/",
        "ja": "/ja/tools/inventory-owner-name-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Link ownership to stable characters despite short display labels",
      "task": "Link ownership to stable characters despite short display labels",
      "searchIntent": {
        "primary": "Complete the task: Link ownership to stable characters despite short display labels",
        "queryHypothesis": "inventory owner name labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link ownership to stable characters despite short display labels?",
        "When should inventory owner name labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link ownership to stable characters despite short display labels",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link ownership to stable characters despite short display labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Link ownership to stable characters despite short display labels versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-accessibility-labels",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Link ownership to stable characters despite short display labels versus Provide readable labels alongside compact visual names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Link ownership to stable characters despite short display labels versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link ownership to stable characters despite short display labels",
        "outline": [
          "Explain the specific decision: Link ownership to stable characters despite short display labels",
          "Define the applicable contract and limits for Inventory owner name labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link ownership to stable characters despite short display labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link ownership to stable characters despite short display labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:464",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-quest-marker-name-labels",
      "slug": "quest-marker-name-labels",
      "name": "Quest marker name labels",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/quest-marker-name-labels/",
        "ja": "/ja/tools/quest-marker-name-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Preserve discovered identity under map space constraints",
      "task": "Preserve discovered identity under map space constraints",
      "searchIntent": {
        "primary": "Complete the task: Preserve discovered identity under map space constraints",
        "queryHypothesis": "quest marker name labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve discovered identity under map space constraints?",
        "When should quest marker name labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve discovered identity under map space constraints",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve discovered identity under map space constraints. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-comic-fake-document-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Preserve discovered identity under map space constraints versus Reconcile a fictional document with cover identity constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dub-name-length-tradeoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Preserve discovered identity under map space constraints versus Compare lip timing constraints with identity continuity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Preserve discovered identity under map space constraints versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve discovered identity under map space constraints",
        "outline": [
          "Explain the specific decision: Preserve discovered identity under map space constraints",
          "Define the applicable contract and limits for Quest marker name labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve discovered identity under map space constraints; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve discovered identity under map space constraints",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:465",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-map-npc-label-priority",
      "slug": "map-npc-label-priority",
      "name": "Map NPC label priority",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/map-npc-label-priority/",
        "ja": "/ja/tools/map-npc-label-priority/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Decide which names remain visible when labels overlap",
      "task": "Decide which names remain visible when labels overlap",
      "searchIntent": {
        "primary": "Complete the task: Decide which names remain visible when labels overlap",
        "queryHypothesis": "map npc label priority",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide which names remain visible when labels overlap?",
        "When should map npc label priority be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide which names remain visible when labels overlap",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide which names remain visible when labels overlap. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-comic-background-name-density",
          "score": 0.26,
          "sharedProfile": false,
          "difference": "Decide which names remain visible when labels overlap versus Decide which names deserve visible labels in crowd scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-social-memory-names",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Decide which names remain visible when labels overlap versus Decide which observers remember an earlier identity after a quest; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-expelled-member-references",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Decide which names remain visible when labels overlap versus Record which titles cease and which personal names remain; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide which names remain visible when labels overlap",
        "outline": [
          "Explain the specific decision: Decide which names remain visible when labels overlap",
          "Define the applicable contract and limits for Map NPC label priority",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide which names remain visible when labels overlap; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide which names remain visible when labels overlap",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:466",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-leaderboard-fiction-identities",
      "slug": "leaderboard-fiction-identities",
      "name": "Leaderboard fiction identities",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/leaderboard-fiction-identities/",
        "ja": "/ja/tools/leaderboard-fiction-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Separate fictional in world rankings from player account identity",
      "task": "Separate fictional in world rankings from player account identity",
      "searchIntent": {
        "primary": "Complete the task: Separate fictional in world rankings from player account identity",
        "queryHypothesis": "leaderboard fiction identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate fictional in world rankings from player account identity?",
        "When should leaderboard fiction identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate fictional in world rankings from player account identity",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate fictional in world rankings from player account identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-live-roleplay-identity-badges",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate fictional in world rankings from player account identity versus Separate player safety information from fictional identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate fictional in world rankings from player account identity versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-idol-group-fictional-identities",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Separate fictional in world rankings from player account identity versus Keep stage persona and private identity relationships explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate fictional in world rankings from player account identity",
        "outline": [
          "Explain the specific decision: Separate fictional in world rankings from player account identity",
          "Define the applicable contract and limits for Leaderboard fiction identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate fictional in world rankings from player account identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate fictional in world rankings from player account identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:467",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-character-select-name-cards",
      "slug": "character-select-name-cards",
      "name": "Character select name cards",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/character-select-name-cards/",
        "ja": "/ja/tools/character-select-name-cards/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Compare full and short names with pronunciation support",
      "task": "Compare full and short names with pronunciation support",
      "searchIntent": {
        "primary": "Complete the task: Compare full and short names with pronunciation support",
        "queryHypothesis": "character select name cards",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare full and short names with pronunciation support?",
        "When should character select name cards be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare full and short names with pronunciation support",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare full and short names with pronunciation support. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-tabletop-name-index-cards",
          "score": 0.25,
          "sharedProfile": false,
          "difference": "Compare full and short names with pronunciation support versus Produce short physical references with role and pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-drama-cast-announcement",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Compare full and short names with pronunciation support versus Order introductions with role and pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Compare full and short names with pronunciation support versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare full and short names with pronunciation support",
        "outline": [
          "Explain the specific decision: Compare full and short names with pronunciation support",
          "Define the applicable contract and limits for Character select name cards",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare full and short names with pronunciation support; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare full and short names with pronunciation support",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:468",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-character-creation-name-feedback",
      "slug": "character-creation-name-feedback",
      "name": "Character creation name feedback",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/character-creation-name-feedback/",
        "ja": "/ja/tools/character-creation-name-feedback/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Explain constraints before a player submits an invalid name",
      "task": "Explain constraints before a player submits an invalid name",
      "searchIntent": {
        "primary": "Complete the task: Explain constraints before a player submits an invalid name",
        "queryHypothesis": "character creation name feedback",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain constraints before a player submits an invalid name?",
        "When should character creation name feedback be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain constraints before a player submits an invalid name",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain constraints before a player submits an invalid name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-generation-error-ui",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Explain constraints before a player submits an invalid name versus Explain exhausted constraints and offer targeted relaxations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-test-contradictory-feedback",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Explain constraints before a player submits an invalid name versus Preserve disagreement instead of collapsing it into one score; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Explain constraints before a player submits an invalid name versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain constraints before a player submits an invalid name",
        "outline": [
          "Explain the specific decision: Explain constraints before a player submits an invalid name",
          "Define the applicable contract and limits for Character creation name feedback",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain constraints before a player submits an invalid name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain constraints before a player submits an invalid name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:469",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-controller-name-entry-flow",
      "slug": "controller-name-entry-flow",
      "name": "Controller name entry flow",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/controller-name-entry-flow/",
        "ja": "/ja/tools/controller-name-entry-flow/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Evaluate required name input using limited navigation",
      "task": "Evaluate required name input using limited navigation",
      "searchIntent": {
        "primary": "Complete the task: Evaluate required name input using limited navigation",
        "queryHypothesis": "controller name entry flow",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to evaluate required name input using limited navigation?",
        "When should controller name entry flow be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Evaluate required name input using limited navigation",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Evaluate required name input using limited navigation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-naming-deadline",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Evaluate required name input using limited navigation versus Choose among supplied candidates using explicit rejection criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-translated-redraw-name",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Evaluate required name input using limited navigation versus List art edits required by a localization decision; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-culture-naming-contrast",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Evaluate required name input using limited navigation versus Compare two invented cultures using explicit structural rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Evaluate required name input using limited navigation",
        "outline": [
          "Explain the specific decision: Evaluate required name input using limited navigation",
          "Define the applicable contract and limits for Controller name entry flow",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Evaluate required name input using limited navigation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Evaluate required name input using limited navigation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:470",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-screen-reader-character-names",
      "slug": "screen-reader-character-names",
      "name": "Screen reader character names",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/screen-reader-character-names/",
        "ja": "/ja/tools/screen-reader-character-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Keep accessible display consistent with visible identity",
      "task": "Keep accessible display consistent with visible identity",
      "searchIntent": {
        "primary": "Complete the task: Keep accessible display consistent with visible identity",
        "queryHypothesis": "screen reader character names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep accessible display consistent with visible identity?",
        "When should screen reader character names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep accessible display consistent with visible identity",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep accessible display consistent with visible identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-screen-reader-brief",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Keep accessible display consistent with visible identity versus Provide author approved reading without relying on glyph guessing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep accessible display consistent with visible identity versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-save-format",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Keep accessible display consistent with visible identity versus Serialize identity, display variants and generation provenance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep accessible display consistent with visible identity",
        "outline": [
          "Explain the specific decision: Keep accessible display consistent with visible identity",
          "Define the applicable contract and limits for Screen reader character names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep accessible display consistent with visible identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep accessible display consistent with visible identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:471",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-font-glyph-audit",
      "slug": "game-font-glyph-audit",
      "name": "Game font glyph audit",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-font-glyph-audit/",
        "ja": "/ja/tools/game-font-glyph-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Verify approved name characters against actual font coverage",
      "task": "Verify approved name characters against actual font coverage",
      "searchIntent": {
        "primary": "Complete the task: Verify approved name characters against actual font coverage",
        "queryHypothesis": "game font glyph audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to verify approved name characters against actual font coverage?",
        "When should game font glyph audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Verify approved name characters against actual font coverage",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Verify approved name characters against actual font coverage. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Verify approved name characters against actual font coverage versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-font-coverage-test",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Verify approved name characters against actual font coverage versus Detect missing glyphs in the actual selected font; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Verify approved name characters against actual font coverage versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Verify approved name characters against actual font coverage",
        "outline": [
          "Explain the specific decision: Verify approved name characters against actual font coverage",
          "Define the applicable contract and limits for Game font glyph audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Verify approved name characters against actual font coverage; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Verify approved name characters against actual font coverage",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:472",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-text-width-name-audit",
      "slug": "game-text-width-name-audit",
      "name": "Game text width name audit",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-text-width-name-audit/",
        "ja": "/ja/tools/game-text-width-name-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Measure actual text instead of using character count as width",
      "task": "Measure actual text instead of using character count as width",
      "searchIntent": {
        "primary": "Complete the task: Measure actual text instead of using character count as width",
        "queryHypothesis": "game text width name audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to measure actual text instead of using character count as width?",
        "When should game text width name audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Measure actual text instead of using character count as width",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Measure actual text instead of using character count as width. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Measure actual text instead of using character count as width versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-font-glyph-audit",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Measure actual text instead of using character count as width versus Verify approved name characters against actual font coverage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-continuity-audit",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Measure actual text instead of using character count as width versus Find speaker pairs using unearned levels of familiarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Measure actual text instead of using character count as width",
        "outline": [
          "Explain the specific decision: Measure actual text instead of using character count as width",
          "Define the applicable contract and limits for Game text width name audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Measure actual text instead of using character count as width; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Measure actual text instead of using character count as width",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:473",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-save-format",
      "slug": "game-name-save-format",
      "name": "Game name save format",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-save-format/",
        "ja": "/ja/tools/game-name-save-format/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Serialize identity, display variants and generation provenance",
      "task": "Serialize identity, display variants and generation provenance",
      "searchIntent": {
        "primary": "Complete the task: Serialize identity, display variants and generation provenance",
        "queryHypothesis": "game name save format",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to serialize identity, display variants and generation provenance?",
        "When should game name save format be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Serialize identity, display variants and generation provenance",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Serialize identity, display variants and generation provenance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Serialize identity, display variants and generation provenance versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-screen-reader-character-names",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Serialize identity, display variants and generation provenance versus Keep accessible display consistent with visible identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-variant-audit",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Serialize identity, display variants and generation provenance versus Find spelling variants for human identity confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Serialize identity, display variants and generation provenance",
        "outline": [
          "Explain the specific decision: Serialize identity, display variants and generation provenance",
          "Define the applicable contract and limits for Game name save format",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Serialize identity, display variants and generation provenance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Serialize identity, display variants and generation provenance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:476",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-translation-table",
      "slug": "game-name-translation-table",
      "name": "Game name translation table",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-translation-table/",
        "ja": "/ja/tools/game-name-translation-table/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Export locale variants with review and fallback status",
      "task": "Export locale variants with review and fallback status",
      "searchIntent": {
        "primary": "Complete the task: Export locale variants with review and fallback status",
        "queryHypothesis": "game name translation table",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export locale variants with review and fallback status?",
        "When should game name translation table be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export locale variants with review and fallback status",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export locale variants with review and fallback status. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-comic-letterer-handoff-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Export locale variants with review and fallback status versus Export approved spellings, pronunciations and forbidden variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-codex-spoiler-names",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Export locale variants with review and fallback status versus Gate names by discovery flags with explicit fallback labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-localization-name-screenshots",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Export locale variants with review and fallback status versus Generate a review checklist tied to actual UI scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export locale variants with review and fallback status",
        "outline": [
          "Explain the specific decision: Export locale variants with review and fallback status",
          "Define the applicable contract and limits for Game name translation table",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export locale variants with review and fallback status; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export locale variants with review and fallback status",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:477",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-renpy-character-display-names",
      "slug": "renpy-character-display-names",
      "name": "RenPy character display names",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/renpy-character-display-names/",
        "ja": "/ja/tools/renpy-character-display-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Plan changing display strings with stable script identities",
      "task": "Plan changing display strings with stable script identities",
      "searchIntent": {
        "primary": "Complete the task: Plan changing display strings with stable script identities",
        "queryHypothesis": "renpy character display names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to plan changing display strings with stable script identities?",
        "When should renpy character display names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Plan changing display strings with stable script identities",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Plan changing display strings with stable script identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-character-id-export",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Plan changing display strings with stable script identities versus Produce stable keys and display strings for production pipelines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Plan changing display strings with stable script identities versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Plan changing display strings with stable script identities versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Plan changing display strings with stable script identities",
        "outline": [
          "Explain the specific decision: Plan changing display strings with stable script identities",
          "Define the applicable contract and limits for RenPy character display names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Plan changing display strings with stable script identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Plan changing display strings with stable script identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:478",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-ink-character-name-variables",
      "slug": "ink-character-name-variables",
      "name": "Ink character name variables",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/ink-character-name-variables/",
        "ja": "/ja/tools/ink-character-name-variables/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Map display identity to story state without renaming knot paths",
      "task": "Map display identity to story state without renaming knot paths",
      "searchIntent": {
        "primary": "Complete the task: Map display identity to story state without renaming knot paths",
        "queryHypothesis": "ink character name variables",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map display identity to story state without renaming knot paths?",
        "When should ink character name variables be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map display identity to story state without renaming knot paths",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map display identity to story state without renaming knot paths. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-ending-signature",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Map display identity to story state without renaming knot paths versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Map display identity to story state without renaming knot paths versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-screen-reader-character-names",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Map display identity to story state without renaming knot paths versus Keep accessible display consistent with visible identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map display identity to story state without renaming knot paths",
        "outline": [
          "Explain the specific decision: Map display identity to story state without renaming knot paths",
          "Define the applicable contract and limits for Ink character name variables",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map display identity to story state without renaming knot paths; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map display identity to story state without renaming knot paths",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:479",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-engine-name-key-migration",
      "slug": "game-engine-name-key-migration",
      "name": "Game engine name key migration",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-engine-name-key-migration/",
        "ja": "/ja/tools/game-engine-name-key-migration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Keep resource keys stable during display name revisions",
      "task": "Keep resource keys stable during display name revisions",
      "searchIntent": {
        "primary": "Complete the task: Keep resource keys stable during display name revisions",
        "queryHypothesis": "game engine name key migration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep resource keys stable during display name revisions?",
        "When should game engine name key migration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep resource keys stable during display name revisions",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep resource keys stable during display name revisions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.30208333333333337,
          "sharedProfile": false,
          "difference": "Keep resource keys stable during display name revisions versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Keep resource keys stable during display name revisions versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-character-id-export",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Keep resource keys stable during display name revisions versus Produce stable keys and display strings for production pipelines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep resource keys stable during display name revisions",
        "outline": [
          "Explain the specific decision: Keep resource keys stable during display name revisions",
          "Define the applicable contract and limits for Game engine name key migration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep resource keys stable during display name revisions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep resource keys stable during display name revisions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:480",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-localization-name-screenshots",
      "slug": "game-localization-name-screenshots",
      "name": "Game localization name screenshots",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-localization-name-screenshots/",
        "ja": "/ja/tools/game-localization-name-screenshots/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Generate a review checklist tied to actual UI scenes",
      "task": "Generate a review checklist tied to actual UI scenes",
      "searchIntent": {
        "primary": "Complete the task: Generate a review checklist tied to actual UI scenes",
        "queryHypothesis": "game localization name screenshots",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate a review checklist tied to actual UI scenes?",
        "When should game localization name screenshots be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate a review checklist tied to actual UI scenes",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate a review checklist tied to actual UI scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Generate a review checklist tied to actual UI scenes versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-translation-table",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Generate a review checklist tied to actual UI scenes versus Export locale variants with review and fallback status; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-maximum-expansion",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Generate a review checklist tied to actual UI scenes versus Test worst case localized names across declared UI components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate a review checklist tied to actual UI scenes",
        "outline": [
          "Explain the specific decision: Generate a review checklist tied to actual UI scenes",
          "Define the applicable contract and limits for Game localization name screenshots",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate a review checklist tied to actual UI scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate a review checklist tied to actual UI scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:481",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-fallback-audit",
      "slug": "game-name-fallback-audit",
      "name": "Game name fallback audit",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-fallback-audit/",
        "ja": "/ja/tools/game-name-fallback-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Detect when a missing translation shows a misleading identity",
      "task": "Detect when a missing translation shows a misleading identity",
      "searchIntent": {
        "primary": "Complete the task: Detect when a missing translation shows a misleading identity",
        "queryHypothesis": "game name fallback audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect when a missing translation shows a misleading identity?",
        "When should game name fallback audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect when a missing translation shows a misleading identity",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect when a missing translation shows a misleading identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-terminology-drift-audit",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Detect when a missing translation shows a misleading identity versus Detect one identity translated inconsistently across episodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-morphology-collision-audit",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Detect when a missing translation shows a misleading identity versus Detect when generated forms collapse across grammatical operations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-font-glyph-audit",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Detect when a missing translation shows a misleading identity versus Verify approved name characters against actual font coverage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect when a missing translation shows a misleading identity",
        "outline": [
          "Explain the specific decision: Detect when a missing translation shows a misleading identity",
          "Define the applicable contract and limits for Game name fallback audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect when a missing translation shows a misleading identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect when a missing translation shows a misleading identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:482",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-nickname-notification",
      "slug": "game-nickname-notification",
      "name": "Game nickname notification",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-nickname-notification/",
        "ja": "/ja/tools/game-nickname-notification/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Announce a changed name in a way players can understand",
      "task": "Announce a changed name in a way players can understand",
      "searchIntent": {
        "primary": "Complete the task: Announce a changed name in a way players can understand",
        "queryHypothesis": "game nickname notification",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to announce a changed name in a way players can understand?",
        "When should game nickname notification be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Announce a changed name in a way players can understand",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Announce a changed name in a way players can understand. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-accepts-unwanted-nickname",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Announce a changed name in a way players can understand versus Trace changed meaning and remaining boundaries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Announce a changed name in a way players can understand versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Announce a changed name in a way players can understand versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Announce a changed name in a way players can understand",
        "outline": [
          "Explain the specific decision: Announce a changed name in a way players can understand",
          "Define the applicable contract and limits for Game nickname notification",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Announce a changed name in a way players can understand; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Announce a changed name in a way players can understand",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:483",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-dialogue-history-identity",
      "slug": "game-dialogue-history-identity",
      "name": "Game dialogue history identity",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-dialogue-history-identity/",
        "ja": "/ja/tools/game-dialogue-history-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Decide whether past lines retain historically visible names",
      "task": "Decide whether past lines retain historically visible names",
      "searchIntent": {
        "primary": "Complete the task: Decide whether past lines retain historically visible names",
        "queryHypothesis": "game dialogue history identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide whether past lines retain historically visible names?",
        "When should game dialogue history identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide whether past lines retain historically visible names",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide whether past lines retain historically visible names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-npc-respawn-identity",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Decide whether past lines retain historically visible names versus Decide whether respawned units retain or replace identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnated-identity-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Decide whether past lines retain historically visible names versus Link past and present names with controlled narrative evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-narrative-identity-tests",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Decide whether past lines retain historically visible names versus Build state fixtures for names before and after quest events; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide whether past lines retain historically visible names",
        "outline": [
          "Explain the specific decision: Decide whether past lines retain historically visible names",
          "Define the applicable contract and limits for Game dialogue history identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide whether past lines retain historically visible names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide whether past lines retain historically visible names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:484",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-photo-mode-labels",
      "slug": "game-photo-mode-labels",
      "name": "Game photo mode labels",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-photo-mode-labels/",
        "ja": "/ja/tools/game-photo-mode-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Keep optional labels consistent with story spoiler settings",
      "task": "Keep optional labels consistent with story spoiler settings",
      "searchIntent": {
        "primary": "Complete the task: Keep optional labels consistent with story spoiler settings",
        "queryHypothesis": "game photo mode labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep optional labels consistent with story spoiler settings?",
        "When should game photo mode labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep optional labels consistent with story spoiler settings",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep optional labels consistent with story spoiler settings. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-accessibility-labels",
          "score": 0.1990909090909091,
          "sharedProfile": false,
          "difference": "Keep optional labels consistent with story spoiler settings versus Provide readable labels alongside compact visual names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-cast-silhouette-labels",
          "score": 0.19444444444444442,
          "sharedProfile": false,
          "difference": "Keep optional labels consistent with story spoiler settings versus Keep production labels distinct from final in story names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Keep optional labels consistent with story spoiler settings versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep optional labels consistent with story spoiler settings",
        "outline": [
          "Explain the specific decision: Keep optional labels consistent with story spoiler settings",
          "Define the applicable contract and limits for Game photo mode labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep optional labels consistent with story spoiler settings; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep optional labels consistent with story spoiler settings",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:485",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-streamer-name-visibility",
      "slug": "game-streamer-name-visibility",
      "name": "Game streamer name visibility",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-streamer-name-visibility/",
        "ja": "/ja/tools/game-streamer-name-visibility/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Define a local presentation policy for chosen display names",
      "task": "Define a local presentation policy for chosen display names",
      "searchIntent": {
        "primary": "Complete the task: Define a local presentation policy for chosen display names",
        "queryHypothesis": "game streamer name visibility",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define a local presentation policy for chosen display names?",
        "When should game streamer name visibility be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define a local presentation policy for chosen display names",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define a local presentation policy for chosen display names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Define a local presentation policy for chosen display names versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-save-format",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Define a local presentation policy for chosen display names versus Serialize identity, display variants and generation provenance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-honorific-policy-for-fiction",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define a local presentation policy for chosen display names versus Define a consistent policy using sourced language guidance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define a local presentation policy for chosen display names",
        "outline": [
          "Explain the specific decision: Define a local presentation policy for chosen display names",
          "Define the applicable contract and limits for Game streamer name visibility",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define a local presentation policy for chosen display names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define a local presentation policy for chosen display names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:486",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-generation-error-ui",
      "slug": "game-name-generation-error-ui",
      "name": "Game name generation error UI",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-generation-error-ui/",
        "ja": "/ja/tools/game-name-generation-error-ui/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Explain exhausted constraints and offer targeted relaxations",
      "task": "Explain exhausted constraints and offer targeted relaxations",
      "searchIntent": {
        "primary": "Complete the task: Explain exhausted constraints and offer targeted relaxations",
        "queryHypothesis": "game name generation error ui",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain exhausted constraints and offer targeted relaxations?",
        "When should game name generation error ui be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain exhausted constraints and offer targeted relaxations",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain exhausted constraints and offer targeted relaxations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-creation-name-feedback",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Explain exhausted constraints and offer targeted relaxations versus Explain constraints before a player submits an invalid name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Explain exhausted constraints and offer targeted relaxations versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-name-tradeoff-exercise",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Explain exhausted constraints and offer targeted relaxations versus Explain what a localization preserves and loses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain exhausted constraints and offer targeted relaxations",
        "outline": [
          "Explain the specific decision: Explain exhausted constraints and offer targeted relaxations",
          "Define the applicable contract and limits for Game name generation error UI",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain exhausted constraints and offer targeted relaxations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain exhausted constraints and offer targeted relaxations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:488",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-generated-cast-import-diff",
      "slug": "game-generated-cast-import-diff",
      "name": "Game generated cast import diff",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-generated-cast-import-diff/",
        "ja": "/ja/tools/game-generated-cast-import-diff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Compare approved and newly generated names before replacement",
      "task": "Compare approved and newly generated names before replacement",
      "searchIntent": {
        "primary": "Complete the task: Compare approved and newly generated names before replacement",
        "queryHypothesis": "game generated cast import diff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare approved and newly generated names before replacement?",
        "When should game generated cast import diff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare approved and newly generated names before replacement",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare approved and newly generated names before replacement. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-series-cast-change-diff",
          "score": 0.12826086956521737,
          "sharedProfile": false,
          "difference": "Compare approved and newly generated names before replacement versus Reconcile explicit base/current/incoming naming snapshots, preserve compatible changes, resolve whole-record and field conflicts under current locks, and validate reading ownership before exporting a complete ledger.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-generated-biography-name-fit",
          "score": 0.125,
          "sharedProfile": false,
          "difference": "Compare approved and newly generated names before replacement versus Check a generated name against explicit biography fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-global-replace-safety",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare approved and newly generated names before replacement versus Preview exact identity scoped edits before applying any replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare approved and newly generated names before replacement",
        "outline": [
          "Explain the specific decision: Compare approved and newly generated names before replacement",
          "Define the applicable contract and limits for Game generated cast import diff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare approved and newly generated names before replacement; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare approved and newly generated names before replacement",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:489",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-data-version-pin",
      "slug": "game-name-data-version-pin",
      "name": "Game name data version pin",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-data-version-pin/",
        "ja": "/ja/tools/game-name-data-version-pin/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Make save generated names reproducible across data updates",
      "task": "Make save generated names reproducible across data updates",
      "searchIntent": {
        "primary": "Complete the task: Make save generated names reproducible across data updates",
        "queryHypothesis": "game name data version pin",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make save generated names reproducible across data updates?",
        "When should game name data version pin be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make save generated names reproducible across data updates",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make save generated names reproducible across data updates. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-example-provenance",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Make save generated names reproducible across data updates versus Mark static examples as authored, generated or externally sourced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-geographic-scope",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Make save generated names reproducible across data updates versus Record coverage and avoid projecting a sample across a culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.10875,
          "sharedProfile": true,
          "difference": "Make save generated names reproducible across data updates versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make save generated names reproducible across data updates",
        "outline": [
          "Explain the specific decision: Make save generated names reproducible across data updates",
          "Define the applicable contract and limits for Game name data version pin",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make save generated names reproducible across data updates; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make save generated names reproducible across data updates",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:490",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-game-name-maximum-expansion",
      "slug": "game-name-maximum-expansion",
      "name": "Game name maximum expansion",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-maximum-expansion/",
        "ja": "/ja/tools/game-name-maximum-expansion/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Test worst case localized names across declared UI components",
      "task": "Test worst case localized names across declared UI components",
      "searchIntent": {
        "primary": "Complete the task: Test worst case localized names across declared UI components",
        "queryHypothesis": "game name maximum expansion",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test worst case localized names across declared UI components?",
        "When should game name maximum expansion be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test worst case localized names across declared UI components",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test worst case localized names across declared UI components. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-localization-name-screenshots",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Test worst case localized names across declared UI components versus Generate a review checklist tied to actual UI scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test worst case localized names across declared UI components versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-translation-brief",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test worst case localized names across declared UI components versus Preserve author intent across localized bylines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test worst case localized names across declared UI components",
        "outline": [
          "Explain the specific decision: Test worst case localized names across declared UI components",
          "Define the applicable contract and limits for Game name maximum expansion",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test worst case localized names across declared UI components; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test worst case localized names across declared UI components",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:491",
      "profileSource": "data/profiles.json#game-ui"
    },
    {
      "id": "nw-tabletop-npc-quick-brief",
      "slug": "tabletop-npc-quick-brief",
      "name": "Tabletop NPC quick brief",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/tabletop-npc-quick-brief/",
        "ja": "/ja/tools/tabletop-npc-quick-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Generate usable names with pronunciation and encounter notes",
      "task": "Generate usable names with pronunciation and encounter notes",
      "searchIntent": {
        "primary": "Complete the task: Generate usable names with pronunciation and encounter notes",
        "queryHypothesis": "tabletop npc quick brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate usable names with pronunciation and encounter notes?",
        "When should tabletop npc quick brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate usable names with pronunciation and encounter notes",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate usable names with pronunciation and encounter notes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-audio-glossary-access",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Generate usable names with pronunciation and encounter notes versus Supply spoiler gated pronunciation notes by episode; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-procedural-npc-naming",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Generate usable names with pronunciation and encounter notes versus Generate from explicit settlement rules and uniqueness scope; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-tabletop-name-index-cards",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Generate usable names with pronunciation and encounter notes versus Produce short physical references with role and pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate usable names with pronunciation and encounter notes",
        "outline": [
          "Explain the specific decision: Generate usable names with pronunciation and encounter notes",
          "Define the applicable contract and limits for Tabletop NPC quick brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate usable names with pronunciation and encounter notes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate usable names with pronunciation and encounter notes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:495",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-cast-registry",
      "slug": "campaign-cast-registry",
      "name": "Campaign cast registry",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-cast-registry/",
        "ja": "/ja/tools/campaign-cast-registry/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Prevent collisions across sessions and locations",
      "task": "Prevent collisions across sessions and locations",
      "searchIntent": {
        "primary": "Complete the task: Prevent collisions across sessions and locations",
        "queryHypothesis": "campaign cast registry",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent collisions across sessions and locations?",
        "When should campaign cast registry be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent collisions across sessions and locations",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent collisions across sessions and locations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-character-registry",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Prevent collisions across sessions and locations versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Prevent collisions across sessions and locations versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anthology-recurring-cast-names",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Prevent collisions across sessions and locations versus Detect accidental reuse across otherwise independent stories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent collisions across sessions and locations",
        "outline": [
          "Explain the specific decision: Prevent collisions across sessions and locations",
          "Define the applicable contract and limits for Campaign cast registry",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent collisions across sessions and locations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent collisions across sessions and locations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:496",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-session-npc-improvisation-log",
      "slug": "session-npc-improvisation-log",
      "name": "Session NPC improvisation log",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/session-npc-improvisation-log/",
        "ja": "/ja/tools/session-npc-improvisation-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Save improvised names with context for later continuity",
      "task": "Save improvised names with context for later continuity",
      "searchIntent": {
        "primary": "Complete the task: Save improvised names with context for later continuity",
        "queryHypothesis": "session npc improvisation log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to save improvised names with context for later continuity?",
        "When should session npc improvisation log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Save improvised names with context for later continuity",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Save improvised names with context for later continuity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-penal-renaming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Save improvised names with context for later continuity versus Trace coercion, records and later reclamation in story context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-hostile-friendly-identity",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Save improvised names with context for later continuity versus Maintain character continuity through allegiance changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-aging-name-timeline",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Save improvised names with context for later continuity versus Transition child, adult and later references by world date; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Save improvised names with context for later continuity",
        "outline": [
          "Explain the specific decision: Save improvised names with context for later continuity",
          "Define the applicable contract and limits for Session NPC improvisation log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Save improvised names with context for later continuity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Save improvised names with context for later continuity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:497",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-table-pronunciation-cards",
      "slug": "table-pronunciation-cards",
      "name": "Table pronunciation cards",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/table-pronunciation-cards/",
        "ja": "/ja/tools/table-pronunciation-cards/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Provide player approved pronunciations for recurring NPCs",
      "task": "Provide player approved pronunciations for recurring NPCs",
      "searchIntent": {
        "primary": "Complete the task: Provide player approved pronunciations for recurring NPCs",
        "queryHypothesis": "table pronunciation cards",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide player approved pronunciations for recurring NPCs?",
        "When should table pronunciation cards be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide player approved pronunciations for recurring NPCs",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide player approved pronunciations for recurring NPCs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Provide player approved pronunciations for recurring NPCs versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Provide player approved pronunciations for recurring NPCs versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Provide player approved pronunciations for recurring NPCs versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide player approved pronunciations for recurring NPCs",
        "outline": [
          "Explain the specific decision: Provide player approved pronunciations for recurring NPCs",
          "Define the applicable contract and limits for Table pronunciation cards",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide player approved pronunciations for recurring NPCs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide player approved pronunciations for recurring NPCs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:498",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-player-character-separation",
      "slug": "campaign-player-character-separation",
      "name": "Campaign player character separation",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-player-character-separation/",
        "ja": "/ja/tools/campaign-player-character-separation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Compare names the group will frequently say together",
      "task": "Compare names the group will frequently say together",
      "searchIntent": {
        "primary": "Complete the task: Compare names the group will frequently say together",
        "queryHypothesis": "campaign player character separation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare names the group will frequently say together?",
        "When should campaign player character separation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare names the group will frequently say together",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare names the group will frequently say together. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Compare names the group will frequently say together versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare names the group will frequently say together versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-belonging-scene",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare names the group will frequently say together versus Compare inclusion and coercion in a group naming ritual; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare names the group will frequently say together",
        "outline": [
          "Explain the specific decision: Compare names the group will frequently say together",
          "Define the applicable contract and limits for Campaign player character separation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare names the group will frequently say together; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare names the group will frequently say together",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:499",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-gm-secret-identity-sheet",
      "slug": "gm-secret-identity-sheet",
      "name": "GM secret identity sheet",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/gm-secret-identity-sheet/",
        "ja": "/ja/tools/gm-secret-identity-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Separate private true names from player facing references",
      "task": "Separate private true names from player facing references",
      "searchIntent": {
        "primary": "Complete the task: Separate private true names from player facing references",
        "queryHypothesis": "gm secret identity sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate private true names from player facing references?",
        "When should gm secret identity sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate private true names from player facing references",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate private true names from player facing references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-royal-identity",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Separate private true names from player facing references versus Manage birth title, assumed name and recognition triggers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-editor-name-correction-sheet",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Separate private true names from player facing references versus Track corrections with page and panel references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-live-roleplay-identity-badges",
          "score": 0.13125,
          "sharedProfile": true,
          "difference": "Separate private true names from player facing references versus Separate player safety information from fictional identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate private true names from player facing references",
        "outline": [
          "Explain the specific decision: Separate private true names from player facing references",
          "Define the applicable contract and limits for GM secret identity sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate private true names from player facing references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate private true names from player facing references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:500",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-player-facing-cast-handout",
      "slug": "player-facing-cast-handout",
      "name": "Player facing cast handout",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/player-facing-cast-handout/",
        "ja": "/ja/tools/player-facing-cast-handout/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Export only identities known to the party",
      "task": "Export only identities known to the party",
      "searchIntent": {
        "primary": "Complete the task: Export only identities known to the party",
        "queryHypothesis": "player facing cast handout",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export only identities known to the party?",
        "When should player facing cast handout be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export only identities known to the party",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export only identities known to the party. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-multi-timeline-cast-names",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Export only identities known to the party versus Distinguish contemporaries, ancestors and repeated identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-spoiler-safe-glossary",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Export only identities known to the party versus Export entries only after the reader reaches the relevant reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Export only identities known to the party versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export only identities known to the party",
        "outline": [
          "Explain the specific decision: Export only identities known to the party",
          "Define the applicable contract and limits for Player facing cast handout",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export only identities known to the party; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export only identities known to the party",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:501",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-family-tree",
      "slug": "campaign-family-tree",
      "name": "Campaign family tree",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-family-tree/",
        "ja": "/ja/tools/campaign-family-tree/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Build relationship linked names from player approved lore",
      "task": "Build relationship linked names from player approved lore",
      "searchIntent": {
        "primary": "Complete the task: Build relationship linked names from player approved lore",
        "queryHypothesis": "campaign family tree",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build relationship linked names from player approved lore?",
        "When should campaign family tree be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build relationship linked names from player approved lore",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build relationship linked names from player approved lore. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-name-planner",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Build relationship linked names from player approved lore versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-tree-label-layout",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Build relationship linked names from player approved lore versus Lay out an authored occurrence DAG with source-bound label dimensions, inspect remaining geometric problems and export a private ID-labelled SVG.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Build relationship linked names from player approved lore versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build relationship linked names from player approved lore",
        "outline": [
          "Explain the specific decision: Build relationship linked names from player approved lore",
          "Define the applicable contract and limits for Campaign family tree",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build relationship linked names from player approved lore; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build relationship linked names from player approved lore",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:502",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-faction-address-rules",
      "slug": "campaign-faction-address-rules",
      "name": "Campaign faction address rules",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-faction-address-rules/",
        "ja": "/ja/tools/campaign-faction-address-rules/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Assign titles and personal names according to fictional memberships",
      "task": "Assign titles and personal names according to fictional memberships",
      "searchIntent": {
        "primary": "Complete the task: Assign titles and personal names according to fictional memberships",
        "queryHypothesis": "campaign faction address rules",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to assign titles and personal names according to fictional memberships?",
        "When should campaign faction address rules be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Assign titles and personal names according to fictional memberships",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Assign titles and personal names according to fictional memberships. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-court-ensemble-address-map",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Assign titles and personal names according to fictional memberships versus Disambiguate personal names, offices and ranked titles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-title-reward",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Assign titles and personal names according to fictional memberships versus Create earned titles tied to actual in game actions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-expelled-member-references",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Assign titles and personal names according to fictional memberships versus Record which titles cease and which personal names remain; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Assign titles and personal names according to fictional memberships",
        "outline": [
          "Explain the specific decision: Assign titles and personal names according to fictional memberships",
          "Define the applicable contract and limits for Campaign faction address rules",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Assign titles and personal names according to fictional memberships; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Assign titles and personal names according to fictional memberships",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:503",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-recurring-villain-title-chain",
      "slug": "recurring-villain-title-chain",
      "name": "Recurring villain title chain",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/recurring-villain-title-chain/",
        "ja": "/ja/tools/recurring-villain-title-chain/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Track changing epithets across encounters",
      "task": "Track changing epithets across encounters",
      "searchIntent": {
        "primary": "Complete the task: Track changing epithets across encounters",
        "queryHypothesis": "recurring villain title chain",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track changing epithets across encounters?",
        "When should recurring villain title chain be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track changing epithets across encounters",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track changing epithets across encounters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-earned-title-progression",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Track changing epithets across encounters versus Sequence titles across actual narrative achievements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anthology-recurring-cast-names",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Track changing epithets across encounters versus Detect accidental reuse across otherwise independent stories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-immortal-reputation-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track changing epithets across encounters versus Track names across communities and centuries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track changing epithets across encounters",
        "outline": [
          "Explain the specific decision: Track changing epithets across encounters",
          "Define the applicable contract and limits for Recurring villain title chain",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track changing epithets across encounters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track changing epithets across encounters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:504",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-one-shot-cast-memory-budget",
      "slug": "one-shot-cast-memory-budget",
      "name": "One shot cast memory budget",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/one-shot-cast-memory-budget/",
        "ja": "/ja/tools/one-shot-cast-memory-budget/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Keep a short session cast distinguishable without a glossary",
      "task": "Keep a short session cast distinguishable without a glossary",
      "searchIntent": {
        "primary": "Complete the task: Keep a short session cast distinguishable without a glossary",
        "queryHypothesis": "one shot cast memory budget",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep a short session cast distinguishable without a glossary?",
        "When should one shot cast memory budget be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep a short session cast distinguishable without a glossary",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep a short session cast distinguishable without a glossary. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-name-budget",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Keep a short session cast distinguishable without a glossary versus Allocate memorable naming signals to narratively important roles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.11597222222222221,
          "sharedProfile": false,
          "difference": "Keep a short session cast distinguishable without a glossary versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-new-cast-collision",
          "score": 0.10875,
          "sharedProfile": false,
          "difference": "Keep a short session cast distinguishable without a glossary versus Compare a proposed cast against previous installments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep a short session cast distinguishable without a glossary",
        "outline": [
          "Explain the specific decision: Keep a short session cast distinguishable without a glossary",
          "Define the applicable contract and limits for One shot cast memory budget",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep a short session cast distinguishable without a glossary; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep a short session cast distinguishable without a glossary",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:505",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-convention-game-pregenerated-names",
      "slug": "convention-game-pregenerated-names",
      "name": "Convention game pregenerated names",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/convention-game-pregenerated-names/",
        "ja": "/ja/tools/convention-game-pregenerated-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Design pronounceable player selectable characters with neutral role cues",
      "task": "Design pronounceable player selectable characters with neutral role cues",
      "searchIntent": {
        "primary": "Complete the task: Design pronounceable player selectable characters with neutral role cues",
        "queryHypothesis": "convention game pregenerated names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design pronounceable player selectable characters with neutral role cues?",
        "When should convention game pregenerated names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design pronounceable player selectable characters with neutral role cues",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design pronounceable player selectable characters with neutral role cues. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-elemental-identity-convention",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Design pronounceable player selectable characters with neutral role cues versus Build explicit fictional naming rules beyond a single elemental adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-codex-spoiler-names",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Design pronounceable player selectable characters with neutral role cues versus Gate names by discovery flags with explicit fallback labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-localization-name-screenshots",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Design pronounceable player selectable characters with neutral role cues versus Generate a review checklist tied to actual UI scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design pronounceable player selectable characters with neutral role cues",
        "outline": [
          "Explain the specific decision: Design pronounceable player selectable characters with neutral role cues",
          "Define the applicable contract and limits for Convention game pregenerated names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design pronounceable player selectable characters with neutral role cues; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design pronounceable player selectable characters with neutral role cues",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:506",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-west-marches-npc-continuity",
      "slug": "west-marches-npc-continuity",
      "name": "West marches NPC continuity",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/west-marches-npc-continuity/",
        "ja": "/ja/tools/west-marches-npc-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Reconcile names recorded by different game masters",
      "task": "Reconcile names recorded by different game masters",
      "searchIntent": {
        "primary": "Complete the task: Reconcile names recorded by different game masters",
        "queryHypothesis": "west marches npc continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile names recorded by different game masters?",
        "When should west marches npc continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile names recorded by different game masters",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile names recorded by different game masters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-prop-name-continuity",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Reconcile names recorded by different game masters versus Reconcile signs and letters with translated dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-expansion-pack-collisions",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Reconcile names recorded by different game masters versus Compare a new cast against base game identity records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-relationship-address-lookup",
          "score": 0.10416666666666666,
          "sharedProfile": false,
          "difference": "Reconcile names recorded by different game masters versus Resolve a display form using speaker listener and game state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile names recorded by different game masters",
        "outline": [
          "Explain the specific decision: Reconcile names recorded by different game masters",
          "Define the applicable contract and limits for West marches NPC continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile names recorded by different game masters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile names recorded by different game masters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:507",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-shared-campaign-naming-authority",
      "slug": "shared-campaign-naming-authority",
      "name": "Shared campaign naming authority",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/shared-campaign-naming-authority/",
        "ja": "/ja/tools/shared-campaign-naming-authority/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Record who may introduce or revise each naming rule",
      "task": "Record who may introduce or revise each naming rule",
      "searchIntent": {
        "primary": "Complete the task: Record who may introduce or revise each naming rule",
        "queryHypothesis": "shared campaign naming authority",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record who may introduce or revise each naming rule?",
        "When should shared campaign naming authority be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record who may introduce or revise each naming rule",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record who may introduce or revise each naming rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Record who may introduce or revise each naming rule versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-loses-naming-authority",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Record who may introduce or revise each naming rule versus Track who controls labels and how that power shifts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-consent-map",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Record who may introduce or revise each naming rule versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record who may introduce or revise each naming rule",
        "outline": [
          "Explain the specific decision: Record who may introduce or revise each naming rule",
          "Define the applicable contract and limits for Shared campaign naming authority",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record who may introduce or revise each naming rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record who may introduce or revise each naming rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:508",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-retcon-name-repair",
      "slug": "campaign-retcon-name-repair",
      "name": "Campaign retcon name repair",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-retcon-name-repair/",
        "ja": "/ja/tools/campaign-retcon-name-repair/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Preserve table notes after an agreed identity revision",
      "task": "Preserve table notes after an agreed identity revision",
      "searchIntent": {
        "primary": "Complete the task: Preserve table notes after an agreed identity revision",
        "queryHypothesis": "campaign retcon name repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve table notes after an agreed identity revision?",
        "When should campaign retcon name repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve table notes after an agreed identity revision",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve table notes after an agreed identity revision. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-settlement-pronunciation",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve table notes after an agreed identity revision versus Keep place derived character references consistent at the table; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-social-memory-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Preserve table notes after an agreed identity revision versus Decide which observers remember an earlier identity after a quest; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-rpg-journal-name-refresh",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Preserve table notes after an agreed identity revision versus Update references after an identity reveal without rewriting historical facts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve table notes after an agreed identity revision",
        "outline": [
          "Explain the specific decision: Preserve table notes after an agreed identity revision",
          "Define the applicable contract and limits for Campaign retcon name repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve table notes after an agreed identity revision; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve table notes after an agreed identity revision",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:509",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-player-nickname-adoption",
      "slug": "player-nickname-adoption",
      "name": "Player nickname adoption",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/player-nickname-adoption/",
        "ja": "/ja/tools/player-nickname-adoption/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Track table invented nicknames separately from in world forms",
      "task": "Track table invented nicknames separately from in world forms",
      "searchIntent": {
        "primary": "Complete the task: Track table invented nicknames separately from in world forms",
        "queryHypothesis": "player nickname adoption",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track table invented nicknames separately from in world forms?",
        "When should player nickname adoption be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track table invented nicknames separately from in world forms",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track table invented nicknames separately from in world forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-trading-guild-diaspora-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track table invented nicknames separately from in world forms versus Track professional and home community forms separately; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-adoption-naming",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Track table invented nicknames separately from in world forms versus Integrate an outsider into an invented clan's explicit rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-plant-person-seasonal-identity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track table invented nicknames separately from in world forms versus Link seasonal forms to continuity in an invented biology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track table invented nicknames separately from in world forms",
        "outline": [
          "Explain the specific decision: Track table invented nicknames separately from in world forms",
          "Define the applicable contract and limits for Player nickname adoption",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track table invented nicknames separately from in world forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track table invented nicknames separately from in world forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:510",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-npc-mistaken-identity-encounter",
      "slug": "npc-mistaken-identity-encounter",
      "name": "NPC mistaken identity encounter",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/npc-mistaken-identity-encounter/",
        "ja": "/ja/tools/npc-mistaken-identity-encounter/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Design fair recoverable name confusion for a live session",
      "task": "Design fair recoverable name confusion for a live session",
      "searchIntent": {
        "primary": "Complete the task: Design fair recoverable name confusion for a live session",
        "queryHypothesis": "npc mistaken identity encounter",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design fair recoverable name confusion for a live session?",
        "When should npc mistaken identity encounter be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design fair recoverable name confusion for a live session",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design fair recoverable name confusion for a live session. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-summoned-entity-misidentification",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Design fair recoverable name confusion for a live session versus Design a recoverable targeting mistake with fair setup; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.16818181818181818,
          "sharedProfile": false,
          "difference": "Design fair recoverable name confusion for a live session versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-respawn-identity",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Design fair recoverable name confusion for a live session versus Decide whether respawned units retain or replace identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design fair recoverable name confusion for a live session",
        "outline": [
          "Explain the specific decision: Design fair recoverable name confusion for a live session",
          "Define the applicable contract and limits for NPC mistaken identity encounter",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design fair recoverable name confusion for a live session; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design fair recoverable name confusion for a live session",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:511",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-rumor-name-variants",
      "slug": "campaign-rumor-name-variants",
      "name": "Campaign rumor name variants",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-rumor-name-variants/",
        "ja": "/ja/tools/campaign-rumor-name-variants/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Link inconsistent rumors without revealing the true person too early",
      "task": "Link inconsistent rumors without revealing the true person too early",
      "searchIntent": {
        "primary": "Complete the task: Link inconsistent rumors without revealing the true person too early",
        "queryHypothesis": "campaign rumor name variants",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link inconsistent rumors without revealing the true person too early?",
        "When should campaign rumor name variants be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link inconsistent rumors without revealing the true person too early",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link inconsistent rumors without revealing the true person too early. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-downtime-household-names",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Link inconsistent rumors without revealing the true person too early versus Extend a household without replacing established members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Link inconsistent rumors without revealing the true person too early versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-setting-naming-bible",
          "score": 0.08666666666666667,
          "sharedProfile": false,
          "difference": "Link inconsistent rumors without revealing the true person too early versus Link places, institutions and people without merging their naming grammars; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link inconsistent rumors without revealing the true person too early",
        "outline": [
          "Explain the specific decision: Link inconsistent rumors without revealing the true person too early",
          "Define the applicable contract and limits for Campaign rumor name variants",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link inconsistent rumors without revealing the true person too early; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link inconsistent rumors without revealing the true person too early",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:512",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-downtime-household-names",
      "slug": "campaign-downtime-household-names",
      "name": "Campaign downtime household names",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-downtime-household-names/",
        "ja": "/ja/tools/campaign-downtime-household-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Extend a household without replacing established members",
      "task": "Extend a household without replacing established members",
      "searchIntent": {
        "primary": "Complete the task: Extend a household without replacing established members",
        "queryHypothesis": "campaign downtime household names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to extend a household without replacing established members?",
        "When should campaign downtime household names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Extend a household without replacing established members",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Extend a household without replacing established members. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shipboard-rank-reference",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Extend a household without replacing established members versus Handle promotions without replacing personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-household-surname",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Extend a household without replacing established members versus Negotiate a shared fictional surname across unrelated members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-rumor-name-variants",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Extend a household without replacing established members versus Link inconsistent rumors without revealing the true person too early; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Extend a household without replacing established members",
        "outline": [
          "Explain the specific decision: Extend a household without replacing established members",
          "Define the applicable contract and limits for Campaign downtime household names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Extend a household without replacing established members; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Extend a household without replacing established members",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:513",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-settlement-pronunciation",
      "slug": "campaign-settlement-pronunciation",
      "name": "Campaign settlement pronunciation",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-settlement-pronunciation/",
        "ja": "/ja/tools/campaign-settlement-pronunciation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Keep place derived character references consistent at the table",
      "task": "Keep place derived character references consistent at the table",
      "searchIntent": {
        "primary": "Complete the task: Keep place derived character references consistent at the table",
        "queryHypothesis": "campaign settlement pronunciation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep place derived character references consistent at the table?",
        "When should campaign settlement pronunciation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep place derived character references consistent at the table",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep place derived character references consistent at the table. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-posthumous-name-rules",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep place derived character references consistent at the table versus Keep living and memorial references consistent; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Keep place derived character references consistent at the table versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-retcon-name-repair",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Keep place derived character references consistent at the table versus Preserve table notes after an agreed identity revision; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep place derived character references consistent at the table",
        "outline": [
          "Explain the specific decision: Keep place derived character references consistent at the table",
          "Define the applicable contract and limits for Campaign settlement pronunciation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep place derived character references consistent at the table; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep place derived character references consistent at the table",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:514",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-memorial-name-list",
      "slug": "campaign-memorial-name-list",
      "name": "Campaign memorial name list",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-memorial-name-list/",
        "ja": "/ja/tools/campaign-memorial-name-list/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Preserve dead or departed characters in a spoiler appropriate handout",
      "task": "Preserve dead or departed characters in a spoiler appropriate handout",
      "searchIntent": {
        "primary": "Complete the task: Preserve dead or departed characters in a spoiler appropriate handout",
        "queryHypothesis": "campaign memorial name list",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve dead or departed characters in a spoiler appropriate handout?",
        "When should campaign memorial name list be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve dead or departed characters in a spoiler appropriate handout",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve dead or departed characters in a spoiler appropriate handout. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-memorial-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve dead or departed characters in a spoiler appropriate handout versus Track whom a child is named for and who knows the connection; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-volume-cast-page",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve dead or departed characters in a spoiler appropriate handout versus Generate spoiler bounded entries by volume; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-cast-evidence-coverage",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve dead or departed characters in a spoiler appropriate handout versus Identify characters with no period appropriate support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve dead or departed characters in a spoiler appropriate handout",
        "outline": [
          "Explain the specific decision: Preserve dead or departed characters in a spoiler appropriate handout",
          "Define the applicable contract and limits for Campaign memorial name list",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve dead or departed characters in a spoiler appropriate handout; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve dead or departed characters in a spoiler appropriate handout",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:515",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-title-reward",
      "slug": "campaign-title-reward",
      "name": "Campaign title reward",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-title-reward/",
        "ja": "/ja/tools/campaign-title-reward/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Create earned titles tied to actual in game actions",
      "task": "Create earned titles tied to actual in game actions",
      "searchIntent": {
        "primary": "Complete the task: Create earned titles tied to actual in game actions",
        "queryHypothesis": "campaign title reward",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to create earned titles tied to actual in game actions?",
        "When should campaign title reward be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Create earned titles tied to actual in game actions",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Create earned titles tied to actual in game actions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-earned-title-progression",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Create earned titles tied to actual in game actions versus Sequence titles across actual narrative achievements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-faction-address-rules",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Create earned titles tied to actual in game actions versus Assign titles and personal names according to fictional memberships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Create earned titles tied to actual in game actions versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Create earned titles tied to actual in game actions",
        "outline": [
          "Explain the specific decision: Create earned titles tied to actual in game actions",
          "Define the applicable contract and limits for Campaign title reward",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Create earned titles tied to actual in game actions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Create earned titles tied to actual in game actions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:516",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-oath-name-contract",
      "slug": "campaign-oath-name-contract",
      "name": "Campaign oath name contract",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-oath-name-contract/",
        "ja": "/ja/tools/campaign-oath-name-contract/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Define invented magical name permissions in player readable terms",
      "task": "Define invented magical name permissions in player readable terms",
      "searchIntent": {
        "primary": "Complete the task: Define invented magical name permissions in player readable terms",
        "queryHypothesis": "campaign oath name contract",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define invented magical name permissions in player readable terms?",
        "When should campaign oath name contract be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define invented magical name permissions in player readable terms",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define invented magical name permissions in player readable terms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-family-tree",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Define invented magical name permissions in player readable terms versus Build relationship linked names from player approved lore; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magical-contract-signatory-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Define invented magical name permissions in player readable terms versus Define which identity form a fictional contract recognizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-bound-oath-breach",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Define invented magical name permissions in player readable terms versus Define breach detection and consequences under authored rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define invented magical name permissions in player readable terms",
        "outline": [
          "Explain the specific decision: Define invented magical name permissions in player readable terms",
          "Define the applicable contract and limits for Campaign oath name contract",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define invented magical name permissions in player readable terms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define invented magical name permissions in player readable terms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:517",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-tabletop-name-index-cards",
      "slug": "tabletop-name-index-cards",
      "name": "Tabletop name index cards",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/tabletop-name-index-cards/",
        "ja": "/ja/tools/tabletop-name-index-cards/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Produce short physical references with role and pronunciation",
      "task": "Produce short physical references with role and pronunciation",
      "searchIntent": {
        "primary": "Complete the task: Produce short physical references with role and pronunciation",
        "queryHypothesis": "tabletop name index cards",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce short physical references with role and pronunciation?",
        "When should tabletop name index cards be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce short physical references with role and pronunciation",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce short physical references with role and pronunciation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-select-name-cards",
          "score": 0.25,
          "sharedProfile": false,
          "difference": "Produce short physical references with role and pronunciation versus Compare full and short names with pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-drama-cast-announcement",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Produce short physical references with role and pronunciation versus Order introductions with role and pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Produce short physical references with role and pronunciation versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce short physical references with role and pronunciation",
        "outline": [
          "Explain the specific decision: Produce short physical references with role and pronunciation",
          "Define the applicable contract and limits for Tabletop name index cards",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce short physical references with role and pronunciation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce short physical references with role and pronunciation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:518",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-tabletop-accessibility-name-review",
      "slug": "tabletop-accessibility-name-review",
      "name": "Tabletop accessibility name review",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/tabletop-accessibility-name-review/",
        "ja": "/ja/tools/tabletop-accessibility-name-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Collect group preferences about difficult spoken distinctions",
      "task": "Collect group preferences about difficult spoken distinctions",
      "searchIntent": {
        "primary": "Complete the task: Collect group preferences about difficult spoken distinctions",
        "queryHypothesis": "tabletop accessibility name review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect group preferences about difficult spoken distinctions?",
        "When should tabletop accessibility name review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect group preferences about difficult spoken distinctions",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect group preferences about difficult spoken distinctions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-accessibility-comparison",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Collect group preferences about difficult spoken distinctions versus Record participant specific difficulties without generalizing to a diagnosis; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-accessibility",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Collect group preferences about difficult spoken distinctions versus Provide a fair alternative when a clue relies on visual or audio distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Collect group preferences about difficult spoken distinctions versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect group preferences about difficult spoken distinctions",
        "outline": [
          "Explain the specific decision: Collect group preferences about difficult spoken distinctions",
          "Define the applicable contract and limits for Tabletop accessibility name review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect group preferences about difficult spoken distinctions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect group preferences about difficult spoken distinctions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:519",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-live-roleplay-identity-badges",
      "slug": "live-roleplay-identity-badges",
      "name": "Live roleplay identity badges",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/live-roleplay-identity-badges/",
        "ja": "/ja/tools/live-roleplay-identity-badges/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Separate player safety information from fictional identity",
      "task": "Separate player safety information from fictional identity",
      "searchIntent": {
        "primary": "Complete the task: Separate player safety information from fictional identity",
        "queryHypothesis": "live roleplay identity badges",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate player safety information from fictional identity?",
        "When should live roleplay identity badges be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate player safety information from fictional identity",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate player safety information from fictional identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-leaderboard-fiction-identities",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate player safety information from fictional identity versus Separate fictional in world rankings from player account identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate player safety information from fictional identity versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-detective-notebook-identity-map",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Separate player safety information from fictional identity versus Separate hypothesis, testimony and corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate player safety information from fictional identity",
        "outline": [
          "Explain the specific decision: Separate player safety information from fictional identity",
          "Define the applicable contract and limits for Live roleplay identity badges",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate player safety information from fictional identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate player safety information from fictional identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:520",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-live-roleplay-alias-reveal",
      "slug": "live-roleplay-alias-reveal",
      "name": "Live roleplay alias reveal",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/live-roleplay-alias-reveal/",
        "ja": "/ja/tools/live-roleplay-alias-reveal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Schedule badge or roster changes at an agreed story event",
      "task": "Schedule badge or roster changes at an agreed story event",
      "searchIntent": {
        "primary": "Complete the task: Schedule badge or roster changes at an agreed story event",
        "queryHypothesis": "live roleplay alias reveal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to schedule badge or roster changes at an agreed story event?",
        "When should live roleplay alias reveal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Schedule badge or roster changes at an agreed story event",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Schedule badge or roster changes at an agreed story event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alias-reveal-comprehension",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Schedule badge or roster changes at an agreed story event versus Test whether readers understand an identity connection at the intended moment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Schedule badge or roster changes at an agreed story event versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-author-rebrand-timeline",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Schedule badge or roster changes at an agreed story event versus Schedule name changes across a backlist and active series; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Schedule badge or roster changes at an agreed story event",
        "outline": [
          "Explain the specific decision: Schedule badge or roster changes at an agreed story event",
          "Define the applicable contract and limits for Live roleplay alias reveal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Schedule badge or roster changes at an agreed story event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Schedule badge or roster changes at an agreed story event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:521",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-collaborative-fiction-name-proposal",
      "slug": "collaborative-fiction-name-proposal",
      "name": "Collaborative fiction name proposal",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/collaborative-fiction-name-proposal/",
        "ja": "/ja/tools/collaborative-fiction-name-proposal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Collect votes and reasons without presenting popularity as quality",
      "task": "Collect votes and reasons without presenting popularity as quality",
      "searchIntent": {
        "primary": "Complete the task: Collect votes and reasons without presenting popularity as quality",
        "queryHypothesis": "collaborative fiction name proposal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect votes and reasons without presenting popularity as quality?",
        "When should collaborative fiction name proposal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect votes and reasons without presenting popularity as quality",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect votes and reasons without presenting popularity as quality. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-fiction-composite-names",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Collect votes and reasons without presenting popularity as quality versus Document invented combinations and avoid presenting them as attested; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-witness-protection-fiction-names",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Collect votes and reasons without presenting popularity as quality versus Design fictional continuity without offering real evasion procedures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-text-to-speech-test",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Collect votes and reasons without presenting popularity as quality versus Collect recorded or reviewed pronunciations without accuracy claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect votes and reasons without presenting popularity as quality",
        "outline": [
          "Explain the specific decision: Collect votes and reasons without presenting popularity as quality",
          "Define the applicable contract and limits for Collaborative fiction name proposal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect votes and reasons without presenting popularity as quality; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect votes and reasons without presenting popularity as quality",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:522",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-campaign-lore-naming-conflict",
      "slug": "campaign-lore-naming-conflict",
      "name": "Campaign lore naming conflict",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-lore-naming-conflict/",
        "ja": "/ja/tools/campaign-lore-naming-conflict/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Reconcile two contributor supplied naming conventions",
      "task": "Reconcile two contributor supplied naming conventions",
      "searchIntent": {
        "primary": "Complete the task: Reconcile two contributor supplied naming conventions",
        "queryHypothesis": "campaign lore naming conflict",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile two contributor supplied naming conventions?",
        "When should campaign lore naming conflict be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile two contributor supplied naming conventions",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile two contributor supplied naming conventions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-intermarried-fictional-houses",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Reconcile two contributor supplied naming conventions versus Reconcile two invented inheritance policies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-merged-identity-systems",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile two contributor supplied naming conventions versus Reconcile naming rules after two fictional organizations combine; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-lost-sibling-reunion-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Reconcile two contributor supplied naming conventions versus Reconcile names learned in separate households; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile two contributor supplied naming conventions",
        "outline": [
          "Explain the specific decision: Reconcile two contributor supplied naming conventions",
          "Define the applicable contract and limits for Campaign lore naming conflict",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile two contributor supplied naming conventions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile two contributor supplied naming conventions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:523",
      "profileSource": "data/profiles.json#tabletop"
    },
    {
      "id": "nw-world-naming-grammar-builder",
      "slug": "world-naming-grammar-builder",
      "name": "World naming grammar builder",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/world-naming-grammar-builder/",
        "ja": "/ja/tools/world-naming-grammar-builder/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define phonotactics and morphology before generating personal names",
      "task": "Define phonotactics and morphology before generating personal names",
      "searchIntent": {
        "primary": "Complete the task: Define phonotactics and morphology before generating personal names",
        "queryHypothesis": "world naming grammar builder",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define phonotactics and morphology before generating personal names?",
        "When should world naming grammar builder be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "inventory",
          "use": "Declare original sounds or graphemes and allowed slots."
        },
        {
          "key": "morphemes",
          "use": "Supply invented components with explicitly fictional glosses."
        },
        {
          "key": "transforms",
          "use": "Set ordered boundary changes, affixes and inheritance operations."
        },
        {
          "key": "testCorpus",
          "use": "Provide positive and negative examples before generation."
        }
      ],
      "rules": [
        "Validate grammar references and detect nonterminating transformations.",
        "Apply transforms in declared order and store every intermediate form.",
        "Separate fictional glosses from real lexical evidence.",
        "Generate only forms passing the positive and negative test contract.",
        "Do not equate one biological species with one culture grammar.",
        "Derive through the declared parent relation and authored transform",
        "Apply explicitly authored morphology rather than real-language inference",
        "Require a stated exception reason before accepting an invalid form",
        "Export the actual rules and their version"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Validate grammar references and detect nonterminating transformations.",
        "Apply transforms in declared order and store every intermediate form.",
        "Separate fictional glosses from real lexical evidence.",
        "Generate only forms passing the positive and negative test contract.",
        "Do not equate one biological species with one culture grammar.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "generated forms with component traces",
        "failed rule explanations",
        "grammar comparison corpus",
        "portable versioned style guide",
        "Transformation trace",
        "Transformation trace",
        "Exception ledger",
        "Reusable grammar document"
      ],
      "capabilities": [
        "Replay a derivation step by step.",
        "Compare two authored culture grammars using the same test roles and distinct structural constraints."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The user creates a generative fictional rule system with derivations and tests, rather than selecting a style from a universal word pool.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define phonotactics and morphology before generating personal names versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-epithet-builder",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Define phonotactics and morphology before generating personal names versus Resolve reputation-based epithets from authored deeds, witnesses and audience adoption at a selected story point.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Define phonotactics and morphology before generating personal names versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Consistency comes from rules with exceptions, not from a repeated decorative suffix.",
        "outline": [
          "Invent the rule before the sample list",
          "Explain one complete derivation",
          "Two neighboring cultures with different inheritance logic",
          "A border interpreter's chosen form",
          "Test exceptions before expanding the corpus"
        ],
        "story": "Fictional example: a border interpreter retains a home lineage component while adapting a public trade-language form. A clerk wrongly applies the trade grammar to the entire name; the corrected record preserves both forms.",
        "storyAnalysis": "The decision depends on declared contact and inheritance rules. Compare a random blend that has no derivation and cannot explain the correction.",
        "evidence": "Original grammar fixtures and fictional component lists; no real-language meanings asserted.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/grammar.md",
        "localizedBodies": {
          "en": "content/en/grammar.md",
          "ja": "content/ja/grammar.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "An illegal final cluster is rejected by the declared boundary rule.",
        "Reordering two noncommuting transforms changes the expected fixture.",
        "A recursive unbounded transform is rejected before generation.",
        "Every displayed meaning from invented morphemes is labeled a fictional gloss.",
        "Wrong parent relation cannot satisfy derivation",
        "Missing morpheme rule returns conflict",
        "Undocumented exception remains invalid",
        "Exported examples reference the pinned grammar"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:527",
      "profileSource": "data/profiles.json#world-grammar",
      "absorbedModules": [
        {
          "sourceId": "nw-invented-matronymic-grammar",
          "input": "maternalTransform",
          "rule": "Derive through the declared parent relation and authored transform",
          "output": "Transformation trace",
          "acceptance": "Wrong parent relation cannot satisfy derivation",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-invented-patronymic-grammar",
          "input": "paternalTransform",
          "rule": "Apply explicitly authored morphology rather than real-language inference",
          "output": "Transformation trace",
          "acceptance": "Missing morpheme rule returns conflict",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-invented-name-grammar-exception",
          "input": "exceptions",
          "rule": "Require a stated exception reason before accepting an invalid form",
          "output": "Exception ledger",
          "acceptance": "Undocumented exception remains invalid",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-invented-culture-name-style-guide",
          "input": "styleGuideExport",
          "rule": "Export the actual rules and their version",
          "output": "Reusable grammar document",
          "acceptance": "Exported examples reference the pinned grammar",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "grammar",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "onsets",
          "label": [
            "Onsets · comma-separated",
            "語頭の要素・カンマ区切り"
          ],
          "type": "text",
          "default": "v, n, s",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "vowels",
          "label": [
            "Nuclei · comma-separated",
            "中心の要素・カンマ区切り"
          ],
          "type": "text",
          "default": "ae, i, o",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "codas",
          "label": [
            "Codas · optional",
            "末尾の要素・任意"
          ],
          "type": "text",
          "default": "n, r",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "suffix",
          "label": [
            "Fixed suffix · optional",
            "固定の接尾辞・任意"
          ],
          "type": "text",
          "default": "el",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "transforms",
          "label": [
            "Ordered transforms",
            "順序付きの変換"
          ],
          "type": "textarea",
          "default": "ne | nai",
          "help": [
            "One rule per line: from | to. Rules apply once in order; cyclic chains are rejected.",
            "1行ごとに 変換前 | 変換後。上から順に適用し、循環する変換は拒否します。"
          ]
        },
        {
          "key": "forbidden",
          "label": [
            "Forbidden clusters",
            "許可しない並び"
          ],
          "type": "text",
          "default": "rr, nn",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "seed",
          "label": [
            "Reproducible seed",
            "再現用シード"
          ],
          "type": "text",
          "default": "woven-01",
          "help": [
            "",
            ""
          ]
        },
        {
          "key": "count",
          "label": [
            "Results · 1–30",
            "生成数 · 1〜30"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "exclude",
          "label": [
            "Excluded strings",
            "除外する文字列"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Comma-separated. Matching is case-insensitive.",
            "カンマ区切り。大文字と小文字は区別しません。"
          ]
        },
        {
          "key": "exclusionMode",
          "label": [
            "Exclusion scope",
            "除外の範囲"
          ],
          "type": "select",
          "default": "contains",
          "help": null,
          "options": [
            [
              "contains",
              [
                "Contains string",
                "文字列を含む"
              ]
            ],
            [
              "exact",
              [
                "Exact full name",
                "姓名の完全一致"
              ]
            ]
          ]
        },
        {
          "key": "grammarVersion",
          "label": [
            "Grammar version",
            "文法の版"
          ],
          "type": "text",
          "default": "1",
          "help": null
        },
        {
          "key": "testCorpus",
          "label": [
            "Positive and negative examples",
            "許可例と拒否例"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "name | accept/reject. A failed example blocks generation.",
            "表記 | accept/reject。不一致があれば生成を止めます。"
          ]
        },
        {
          "key": "exceptions",
          "label": [
            "Authored exceptions",
            "作者が定める例外"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "name | reason. Explicit fictional exceptions only.",
            "表記 | 理由。架空の例外として明示します。"
          ]
        },
        {
          "key": "compareOnsets",
          "label": [
            "Second grammar onsets",
            "比較用文法の語頭"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "compareVowels",
          "label": [
            "Second grammar nuclei",
            "比較用文法の中心"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "compareCodas",
          "label": [
            "Second grammar codas",
            "比較用文法の末尾"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "compareSuffix",
          "label": [
            "Second grammar suffix",
            "比較用文法の接尾辞"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "parentLinks",
          "label": [
            "Fictional parent-derived forms",
            "架空の親名からの派生"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "child ID | maternal source ID | paternal source ID",
            "子のID | 母系の参照ID | 父系の参照ID"
          ]
        },
        {
          "key": "parentRoots",
          "label": [
            "Supplied fictional parent roots",
            "作者指定の架空の親語幹"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "person ID | fictional root",
            "人物ID | 架空の語幹"
          ]
        },
        {
          "key": "parentPolicy",
          "label": [
            "Derivation source relation",
            "派生元の関係"
          ],
          "type": "select",
          "default": "maternal",
          "help": null,
          "options": [
            [
              "maternal",
              [
                "Maternal source",
                "母系の参照元"
              ]
            ],
            [
              "paternal",
              [
                "Paternal source",
                "父系の参照元"
              ]
            ]
          ]
        },
        {
          "key": "parentTransforms",
          "label": [
            "Ordered fictional parent transforms",
            "親語幹に対する架空の変換"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "from | to. Applied once in order to the selected parent root.",
            "変換前 | 変換後。選んだ親語幹へ順に一度ずつ適用。"
          ]
        },
        {
          "key": "parentSuffix",
          "label": [
            "Fictional parent-name suffix",
            "架空の親名派生の接尾辞"
          ],
          "type": "text",
          "default": "",
          "help": null
        }
      ]
    },
    {
      "id": "nw-culture-naming-contrast",
      "slug": "culture-naming-contrast",
      "name": "Culture naming contrast",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/culture-naming-contrast/",
        "ja": "/ja/tools/culture-naming-contrast/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Compare two invented cultures using explicit structural rules",
      "task": "Compare two invented cultures using explicit structural rules",
      "searchIntent": {
        "primary": "Complete the task: Compare two invented cultures using explicit structural rules",
        "queryHypothesis": "culture naming contrast",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare two invented cultures using explicit structural rules?",
        "When should culture naming contrast be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare two invented cultures using explicit structural rules",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare two invented cultures using explicit structural rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nonhuman-culture-naming-contrast",
          "score": 0.2833333333333333,
          "sharedProfile": false,
          "difference": "Compare two invented cultures using explicit structural rules versus Distinguish cultures within a species rather than one species one style; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-world-culture-grouping-test",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Compare two invented cultures using explicit structural rules versus Test whether readers group invented names according to authored cultures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-intermarried-fictional-houses",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare two invented cultures using explicit structural rules versus Reconcile two invented inheritance policies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare two invented cultures using explicit structural rules",
        "outline": [
          "Explain the specific decision: Compare two invented cultures using explicit structural rules",
          "Define the applicable contract and limits for Culture naming contrast",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare two invented cultures using explicit structural rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare two invented cultures using explicit structural rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:528",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-surname-inheritance",
      "slug": "invented-surname-inheritance",
      "name": "Invented surname inheritance",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-surname-inheritance/",
        "ja": "/ja/tools/invented-surname-inheritance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Model family transmission independently of given name generation",
      "task": "Model family transmission independently of given name generation",
      "searchIntent": {
        "primary": "Complete the task: Model family transmission independently of given name generation",
        "queryHypothesis": "invented surname inheritance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model family transmission independently of given name generation?",
        "When should invented surname inheritance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model family transmission independently of given name generation",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model family transmission independently of given name generation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-surname-construction",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Model family transmission independently of given name generation versus Build a family identifier with explicit inheritance assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-occupation-surnames",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Model family transmission independently of given name generation versus Model when an occupational label becomes hereditary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secular-name-reform",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Model family transmission independently of given name generation versus Model a culture changing its naming institutions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model family transmission independently of given name generation",
        "outline": [
          "Explain the specific decision: Model family transmission independently of given name generation",
          "Define the applicable contract and limits for Invented surname inheritance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model family transmission independently of given name generation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model family transmission independently of given name generation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:529",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-lineage-chain",
      "slug": "invented-lineage-chain",
      "name": "Invented lineage chain",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-lineage-chain/",
        "ja": "/ja/tools/invented-lineage-chain/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Build multigeneration references with a readable shortening policy",
      "task": "Build multigeneration references with a readable shortening policy",
      "searchIntent": {
        "primary": "Complete the task: Build multigeneration references with a readable shortening policy",
        "queryHypothesis": "invented lineage chain",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build multigeneration references with a readable shortening policy?",
        "When should invented lineage chain be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build multigeneration references with a readable shortening policy",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build multigeneration references with a readable shortening policy. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-posthumous-name-rules",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Build multigeneration references with a readable shortening policy versus Keep living and memorial references consistent; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-namesake-ancestor-chain",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Build multigeneration references with a readable shortening policy versus Show repeated names with unambiguous narrative references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sensory-name-translation",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Build multigeneration references with a readable shortening policy versus Translate nonspoken identity cues into readable narrative labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build multigeneration references with a readable shortening policy",
        "outline": [
          "Explain the specific decision: Build multigeneration references with a readable shortening policy",
          "Define the applicable contract and limits for Invented lineage chain",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build multigeneration references with a readable shortening policy; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build multigeneration references with a readable shortening policy",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:532",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-name-case-endings",
      "slug": "invented-name-case-endings",
      "name": "Invented name case endings",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-name-case-endings/",
        "ja": "/ja/tools/invented-name-case-endings/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Creators writing invented-language dialogue, interface templates and world-language style sheets.",
      "scenario": "A character’s address and possessive forms look like new names to the production team; the author needs a complete approved paradigm and an ambiguity check.",
      "task": "Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants.",
      "searchIntent": {
        "primary": "Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants.",
        "queryHypothesis": "invented name case endings",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "When should a missing form remain unresolved?",
        "Can identical grammatical forms retain different function keys?"
      ],
      "inputs": [
        {
          "key": "people",
          "use": "Stable IDs, unchanged citation forms and explicit class assignments."
        },
        {
          "key": "stems",
          "use": "Declared stem variants by identity/key; never infer an irregular stem from a citation form."
        },
        {
          "key": "slots",
          "use": "Finite authored grammatical functions and required/optional status, independent of real-language terminology."
        },
        {
          "key": "classes",
          "use": "Per-class slot rules selecting a stem and literal prefix/suffix or explicit whole form."
        },
        {
          "key": "exceptions",
          "use": "Identity/slot-specific declared replacements with reason and expected current rule provenance."
        },
        {
          "key": "syncretism",
          "use": "Explicit allowed coincident slot pairs; distinguish intended shared forms from unreviewed ambiguity."
        },
        {
          "key": "reviews",
          "use": "Exact local authored form reviews bound to source and coincidence snapshots; not external approval."
        },
        {
          "key": "languageKey",
          "use": "Exact invented form-set label for a real downstream dialogue fixture object."
        },
        {
          "key": "revision",
          "use": "Positive authored version label included in review scope, with literal source comparison rather than version-only approval."
        }
      ],
      "rules": [
        "Keep citation form and person ID unchanged across the paradigm.",
        "Require explicit class, slot and stem references; missing rules stay missing rather than guessed.",
        "Apply only literal authored realization rules; do not translate grammatical categories into a real language.",
        "Record which base and rule produced each form; exceptions do not silently erase the default.",
        "Treat same display in multiple slots as a declared or unreviewed coincidence, not an automatic grammar error.",
        "Preserve distinct people even when all their realized forms coincide.",
        "Handoff to dialogue uses stable form keys and exact declared display; exporting is not permission to overwrite a manuscript."
      ],
      "requiredData": [
        {
          "description": "Original fictional class/slot paradigms and deliberate coincident-form fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Creator-approved stem and grammar sheets; no real linguistic rule inventory imported",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Keep citation form and person ID unchanged across the paradigm.",
        "Require explicit class, slot and stem references; missing rules stay missing rather than guessed.",
        "Apply only literal authored realization rules; do not translate grammatical categories into a real language.",
        "Record which base and rule produced each form; exceptions do not silently erase the default.",
        "Treat same display in multiple slots as a declared or unreviewed coincidence, not an automatic grammar error.",
        "Preserve distinct people even when all their realized forms coincide.",
        "Handoff to dialogue uses stable form keys and exact declared display; exporting is not permission to overwrite a manuscript."
      ],
      "outputs": [
        "Complete person-by-function paradigm with missing and exception states",
        "Coincident-slot/identity ambiguity review retaining declared allowances",
        "Versioned form-key handoff for downstream dialogue or lettering"
      ],
      "capabilities": [
        "Expose a missing or stale irregular form without deriving a guessed replacement.",
        "Distinguish intended coincident grammatical forms from unresolved cross-slot ambiguity, and keep all original identities."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The main task is constructing function-indexed forms from declared stems and inflection rules. A dialogue-slot tool selects already supplied forms, and a historical derivation tool transforms a root through eras; neither builds and checks a grammatical paradigm with declared syncretism and missing slots.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "player-name-dialogue-grammar",
          "difference": "The existing dialogue resolver chooses supplied forms for an exact context and does not create grammar. This proposal constructs a finite paradigm from explicit stems, slot rules and exceptions, reports missing slots and coincident forms, and hands off approved form keys. It is not a claim about real Japanese, English or another language."
        }
      },
      "nearestTools": [
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.110625,
          "sharedProfile": false,
          "difference": "Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants. versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants. versus Remove overdetermined motifs while preserving relevant story function; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.10823529411764705,
          "sharedProfile": true,
          "difference": "Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants. versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Different grammatical forms can remain one identity; identical forms can still need different keys.",
        "outline": [
          "A recipe dedication mistaken for a different person",
          "Define a finite function inventory",
          "Keep the citation name outside the generated paradigm",
          "Read intentional shared forms",
          "Prepare a scoped form-key handoff"
        ],
        "story": "In an invented community kitchen, a newcomer mistakes the possessive form in a gift-recipe dedication for the name of another person. A host uses the address form to invite the recipient to cook. An approved function-indexed sheet lets the writer stage that misunderstanding without multiplying the cast or claiming the grammar belongs to a real language.",
        "storyAnalysis": "If every grammatical form receives a new person ID, the cast multiplies; if every shared spelling loses its slot key, dialogue cannot choose the intended function. The paradigm preserves both distinctions.",
        "evidence": "Original complete EN/JA kitchen guides, literal paradigm fixtures, PARA tests and observed browser handoff.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/morphology.md",
        "localizedBodies": {
          "en": "content/en/morphology.md",
          "ja": "content/ja/morphology.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Changing one class suffix changes precisely its dependent forms.",
        "A missing stem yields an unresolved slot rather than use of the citation form as a guessed fallback.",
        "An explicit exception preserves trace and does not mutate unrelated slots.",
        "Allowed syncretism and unreviewed identical forms remain different states.",
        "A fixed downstream form key selects the intended exact output, even if another slot shares the spelling."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:533",
      "profileSource": "data/profiles.json#world-grammar",
      "specBatch": "batch-06",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Task-specific state/trace rules, ambiguity handling and original bilingual explanation; not a measured effort estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "morphology",
        "engineFiles": [
          "web/name-paradigms.mjs",
          "web/morphology-view.mjs",
          "web/morphology-tool.mjs",
          "web/morphology-capture.js",
          "scripts/render-morphology.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/morphology.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "People & citation forms · JSON",
            "人物と元の表記・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"alda\",\n    \"citation\": \"Alda\",\n    \"class\": \"open\"\n  },\n  {\n    \"id\": \"bren\",\n    \"citation\": \"Bren\",\n    \"class\": \"open\"\n  }\n]",
          "help": [
            "id/citation/class. Changing a grammatical form never creates a new person. Up to 30 people; person-by-function rows ≤120.",
            "id/citation/class。文法の形が変わっても人物を増やしません。30人まで、人物と機能の組は120件以内。"
          ],
          "maxLength": 150000
        },
        {
          "key": "stems",
          "label": [
            "Explicit stem variants · JSON",
            "明示した語幹・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"person\": \"alda\",\n    \"key\": \"base\",\n    \"text\": \"Ald\"\n  },\n  {\n    \"person\": \"alda\",\n    \"key\": \"poss\",\n    \"text\": \"Ald\"\n  },\n  {\n    \"person\": \"bren\",\n    \"key\": \"base\",\n    \"text\": \"Bren\"\n  }\n]",
          "help": [
            "person/key/text. Missing is not the same as an explicitly empty text. No stem is inferred from the citation name.",
            "person/key/text。未登録と明示した空のtextは違います。元の表記から語幹を推測しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "slots",
          "label": [
            "Authored functions · JSON",
            "作者が定める機能・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"address\",\n    \"label\": \"Direct address\",\n    \"required\": true\n  },\n  {\n    \"id\": \"possessive\",\n    \"label\": \"Possession label\",\n    \"required\": true\n  },\n  {\n    \"id\": \"topic\",\n    \"label\": \"Topic reference\",\n    \"required\": true\n  }\n]",
          "help": [
            "Unique id/label/required. IDs become literal dialogue form keys; name is reserved and unsupported. Labels do not assert a real-language grammar.",
            "固有のid/label/required。IDは台詞用の表記キーになります。nameは予約済みで使えません。labelは実在言語の文法の認定ではありません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "classes",
          "label": [
            "Classes and realization rules · JSON",
            "類と表記の規則・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"open\",\n    \"label\": \"Invented open class\",\n    \"rules\": [\n      {\n        \"slot\": \"address\",\n        \"kind\": \"affix\",\n        \"stem\": \"base\",\n        \"prefix\": \"\",\n        \"suffix\": \"e\"\n      },\n      {\n        \"slot\": \"possessive\",\n        \"kind\": \"affix\",\n        \"stem\": \"poss\",\n        \"prefix\": \"\",\n        \"suffix\": \"em\"\n      },\n      {\n        \"slot\": \"topic\",\n        \"kind\": \"affix\",\n        \"stem\": \"base\",\n        \"prefix\": \"\",\n        \"suffix\": \"e\"\n      }\n    ]\n  }\n]",
          "help": [
            "affix chooses a stem with literal prefix/suffix. citation explicitly uses the original display; whole supplies exact text. Missing rules remain unresolved.",
            "affixは語幹とprefix/suffix、citationは明示的な元の表示、wholeは正確なtextを使います。欠けた規則を自動補完しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "exceptions",
          "label": [
            "Scoped whole-form exceptions · JSON",
            "範囲付きの全形例外・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "person/slot/form/expected/reason. Use the capture controls below to record the current exact base rather than guessing expected data.",
            "person/slot/form/expected/reason。下の記録操作で現在の生成元を取り込み、expectedを推測して書かないようにします。"
          ],
          "maxLength": 150000
        },
        {
          "key": "syncretism",
          "label": [
            "Allowed coincident function pairs · JSON",
            "同形を許容する機能の組・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"scope\": \"class\",\n    \"target\": \"open\",\n    \"slots\": [\n      \"address\",\n      \"topic\"\n    ],\n    \"reason\": \"The invented convention deliberately shares one form in these two functions.\"\n  }\n]",
          "help": [
            "scope person/class, known target, exactly two slots, reason. Pair permissions are not transitive and never merge different people.",
            "scopeはperson/class、既存のtarget、二つのslots、reason。許容は推移的に広げず、別人も統合しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "reviews",
          "label": [
            "Exact authored review records · JSON",
            "作者の正確な確認記録・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Captured locally with a note. An unchanged revision number alone does not keep a changed derivation approved.",
            "メモとともにローカルで記録します。revisionを変えなくても、生成元の変更は古い確認と不一致になります。"
          ],
          "maxLength": 150000,
          "requiredInProject": true
        },
        {
          "key": "languageKey",
          "label": [
            "Literal language key for handoff",
            "引き渡し用の言語キー"
          ],
          "type": "text",
          "default": "kitchen",
          "help": [
            "An authored identifier, not an automatic translation target.",
            "作者の識別子で、自動翻訳の対象ではありません。"
          ]
        },
        {
          "key": "revision",
          "label": [
            "Paradigm revision · positive integer",
            "変化表の版・正の整数"
          ],
          "type": "number",
          "default": 1,
          "help": null
        }
      ]
    },
    {
      "id": "nw-invented-gender-free-morphology",
      "slug": "invented-gender-free-morphology",
      "name": "Invented gender free morphology",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-gender-free-morphology/",
        "ja": "/ja/tools/invented-gender-free-morphology/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Generate under a fictional grammar with no gender inference",
      "task": "Generate under a fictional grammar with no gender inference",
      "searchIntent": {
        "primary": "Complete the task: Generate under a fictional grammar with no gender inference",
        "queryHypothesis": "invented gender free morphology",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate under a fictional grammar with no gender inference?",
        "When should invented gender free morphology be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Generate under a fictional grammar with no gender inference",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Generate under a fictional grammar with no gender inference. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Generate under a fictional grammar with no gender inference versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Generate under a fictional grammar with no gender inference versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Generate under a fictional grammar with no gender inference versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Generate under a fictional grammar with no gender inference",
        "outline": [
          "Explain the specific decision: Generate under a fictional grammar with no gender inference",
          "Define the applicable contract and limits for Invented gender free morphology",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Generate under a fictional grammar with no gender inference; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Generate under a fictional grammar with no gender inference",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:534",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-life-stage-names",
      "slug": "invented-life-stage-names",
      "name": "Invented life stage names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-life-stage-names/",
        "ja": "/ja/tools/invented-life-stage-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Transition name components at declared social milestones",
      "task": "Transition name components at declared social milestones",
      "searchIntent": {
        "primary": "Complete the task: Transition name components at declared social milestones",
        "queryHypothesis": "invented life stage names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transition name components at declared social milestones?",
        "When should invented life stage names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transition name components at declared social milestones",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transition name components at declared social milestones. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-naming-ceremony",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Transition name components at declared social milestones versus Link name assignment to authored social rituals and timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Transition name components at declared social milestones versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.15125,
          "sharedProfile": true,
          "difference": "Transition name components at declared social milestones versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transition name components at declared social milestones",
        "outline": [
          "Explain the specific decision: Transition name components at declared social milestones",
          "Define the applicable contract and limits for Invented life stage names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transition name components at declared social milestones; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transition name components at declared social milestones",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:535",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-achievement-names",
      "slug": "invented-achievement-names",
      "name": "Invented achievement names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-achievement-names/",
        "ja": "/ja/tools/invented-achievement-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Derive an earned component from a documented story action",
      "task": "Derive an earned component from a documented story action",
      "searchIntent": {
        "primary": "Complete the task: Derive an earned component from a documented story action",
        "queryHypothesis": "invented achievement names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive an earned component from a documented story action?",
        "When should invented achievement names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive an earned component from a documented story action",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive an earned component from a documented story action. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Derive an earned component from a documented story action versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Derive an earned component from a documented story action versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Derive an earned component from a documented story action versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive an earned component from a documented story action",
        "outline": [
          "Explain the specific decision: Derive an earned component from a documented story action",
          "Define the applicable contract and limits for Invented achievement names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive an earned component from a documented story action; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive an earned component from a documented story action",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:536",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-occupation-surnames",
      "slug": "invented-occupation-surnames",
      "name": "Invented occupation surnames",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-occupation-surnames/",
        "ja": "/ja/tools/invented-occupation-surnames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Model when an occupational label becomes hereditary",
      "task": "Model when an occupational label becomes hereditary",
      "searchIntent": {
        "primary": "Complete the task: Model when an occupational label becomes hereditary",
        "queryHypothesis": "invented occupation surnames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model when an occupational label becomes hereditary?",
        "When should invented occupation surnames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model when an occupational label becomes hereditary",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model when an occupational label becomes hereditary. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Model when an occupational label becomes hereditary versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-names-without-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Model when an occupational label becomes hereditary versus Design a reference system that does not assume family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-surname-inheritance",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Model when an occupational label becomes hereditary versus Model family transmission independently of given name generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model when an occupational label becomes hereditary",
        "outline": [
          "Explain the specific decision: Model when an occupational label becomes hereditary",
          "Define the applicable contract and limits for Invented occupation surnames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model when an occupational label becomes hereditary; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model when an occupational label becomes hereditary",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:537",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-locality-surnames",
      "slug": "invented-locality-surnames",
      "name": "Invented locality surnames",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-locality-surnames/",
        "ja": "/ja/tools/invented-locality-surnames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Derive a surname from a supplied fictional place grammar",
      "task": "Derive a surname from a supplied fictional place grammar",
      "searchIntent": {
        "primary": "Complete the task: Derive a surname from a supplied fictional place grammar",
        "queryHypothesis": "invented locality surnames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive a surname from a supplied fictional place grammar?",
        "When should invented locality surnames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive a surname from a supplied fictional place grammar",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive a surname from a supplied fictional place grammar. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-names-without-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Derive a surname from a supplied fictional place grammar versus Design a reference system that does not assume family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-occupation-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Derive a surname from a supplied fictional place grammar versus Model when an occupational label becomes hereditary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Derive a surname from a supplied fictional place grammar versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive a surname from a supplied fictional place grammar",
        "outline": [
          "Explain the specific decision: Derive a surname from a supplied fictional place grammar",
          "Define the applicable contract and limits for Invented locality surnames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive a surname from a supplied fictional place grammar; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive a surname from a supplied fictional place grammar",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:538",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-house-name-particles",
      "slug": "invented-house-name-particles",
      "name": "Invented house name particles",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-house-name-particles/",
        "ja": "/ja/tools/invented-house-name-particles/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Apply particles and capitalization consistently",
      "task": "Apply particles and capitalization consistently",
      "searchIntent": {
        "primary": "Complete the task: Apply particles and capitalization consistently",
        "queryHypothesis": "invented house name particles",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply particles and capitalization consistently?",
        "When should invented house name particles be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply particles and capitalization consistently",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply particles and capitalization consistently. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-loan-adaptation",
          "score": 0.16285714285714287,
          "sharedProfile": true,
          "difference": "Apply particles and capitalization consistently versus Apply explicit sound substitutions to borrowed names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-achievement-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Apply particles and capitalization consistently versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-ceremony",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Apply particles and capitalization consistently versus Link name assignment to authored social rituals and timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply particles and capitalization consistently",
        "outline": [
          "Explain the specific decision: Apply particles and capitalization consistently",
          "Define the applicable contract and limits for Invented house name particles",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply particles and capitalization consistently; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply particles and capitalization consistently",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:539",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-clan-name-affixes",
      "slug": "invented-clan-name-affixes",
      "name": "Invented clan name affixes",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-clan-name-affixes/",
        "ja": "/ja/tools/invented-clan-name-affixes/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Enforce a declared clan marker across eligible members",
      "task": "Enforce a declared clan marker across eligible members",
      "searchIntent": {
        "primary": "Complete the task: Enforce a declared clan marker across eligible members",
        "queryHypothesis": "invented clan name affixes",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to enforce a declared clan marker across eligible members?",
        "When should invented clan name affixes be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Enforce a declared clan marker across eligible members",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Enforce a declared clan marker across eligible members. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Enforce a declared clan marker across eligible members versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-adoption-naming",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Enforce a declared clan marker across eligible members versus Integrate an outsider into an invented clan's explicit rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Enforce a declared clan marker across eligible members versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Enforce a declared clan marker across eligible members",
        "outline": [
          "Explain the specific decision: Enforce a declared clan marker across eligible members",
          "Define the applicable contract and limits for Invented clan name affixes",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Enforce a declared clan marker across eligible members; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Enforce a declared clan marker across eligible members",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:540",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-name-taboo-system",
      "slug": "invented-name-taboo-system",
      "name": "Invented name taboo system",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-name-taboo-system/",
        "ja": "/ja/tools/invented-name-taboo-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Exclude prohibited forms with an explicit cultural rule ledger",
      "task": "Exclude prohibited forms with an explicit cultural rule ledger",
      "searchIntent": {
        "primary": "Complete the task: Exclude prohibited forms with an explicit cultural rule ledger",
        "queryHypothesis": "invented name taboo system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to exclude prohibited forms with an explicit cultural rule ledger?",
        "When should invented name taboo system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Exclude prohibited forms with an explicit cultural rule ledger",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Exclude prohibited forms with an explicit cultural rule ledger. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-naming-system-reader-load",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Exclude prohibited forms with an explicit cultural rule ledger versus Test grammar complexity against reader recall exercises; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Exclude prohibited forms with an explicit cultural rule ledger versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-resistance-names",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Exclude prohibited forms with an explicit cultural rule ledger versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Exclude prohibited forms with an explicit cultural rule ledger",
        "outline": [
          "Explain the specific decision: Exclude prohibited forms with an explicit cultural rule ledger",
          "Define the applicable contract and limits for Invented name taboo system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Exclude prohibited forms with an explicit cultural rule ledger; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Exclude prohibited forms with an explicit cultural rule ledger",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:541",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-secret-public-names",
      "slug": "invented-secret-public-names",
      "name": "Invented secret public names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-secret-public-names/",
        "ja": "/ja/tools/invented-secret-public-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define access to name layers within a fictional culture",
      "task": "Define access to name layers within a fictional culture",
      "searchIntent": {
        "primary": "Complete the task: Define access to name layers within a fictional culture",
        "queryHypothesis": "invented secret public names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define access to name layers within a fictional culture?",
        "When should invented secret public names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define access to name layers within a fictional culture",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define access to name layers within a fictional culture. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Define access to name layers within a fictional culture versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-exonym-endonym",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Define access to name layers within a fictional culture versus Track what a culture calls itself and what outsiders use; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sacred-name-avoidance",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Define access to name layers within a fictional culture versus Define who may speak which name in which context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define access to name layers within a fictional culture",
        "outline": [
          "Explain the specific decision: Define access to name layers within a fictional culture",
          "Define the applicable contract and limits for Invented secret public names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define access to name layers within a fictional culture; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define access to name layers within a fictional culture",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:542",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-naming-ceremony",
      "slug": "invented-naming-ceremony",
      "name": "Invented naming ceremony",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-naming-ceremony/",
        "ja": "/ja/tools/invented-naming-ceremony/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Link name assignment to authored social rituals and timeline",
      "task": "Link name assignment to authored social rituals and timeline",
      "searchIntent": {
        "primary": "Complete the task: Link name assignment to authored social rituals and timeline",
        "queryHypothesis": "invented naming ceremony",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link name assignment to authored social rituals and timeline?",
        "When should invented naming ceremony be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link name assignment to authored social rituals and timeline",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link name assignment to authored social rituals and timeline. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-resistance-names",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Link name assignment to authored social rituals and timeline versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Link name assignment to authored social rituals and timeline versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-achievement-names",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Link name assignment to authored social rituals and timeline versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link name assignment to authored social rituals and timeline",
        "outline": [
          "Explain the specific decision: Link name assignment to authored social rituals and timeline",
          "Define the applicable contract and limits for Invented naming ceremony",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link name assignment to authored social rituals and timeline; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link name assignment to authored social rituals and timeline",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:543",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-exonym-endonym",
      "slug": "invented-exonym-endonym",
      "name": "Invented exonym endonym",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-exonym-endonym/",
        "ja": "/ja/tools/invented-exonym-endonym/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Track what a culture calls itself and what outsiders use",
      "task": "Track what a culture calls itself and what outsiders use",
      "searchIntent": {
        "primary": "Complete the task: Track what a culture calls itself and what outsiders use",
        "queryHypothesis": "invented exonym endonym",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track what a culture calls itself and what outsiders use?",
        "When should invented exonym endonym be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track what a culture calls itself and what outsiders use",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track what a culture calls itself and what outsiders use. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Track what a culture calls itself and what outsiders use versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secular-name-reform",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Track what a culture calls itself and what outsiders use versus Model a culture changing its naming institutions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-achievement-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Track what a culture calls itself and what outsiders use versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track what a culture calls itself and what outsiders use",
        "outline": [
          "Explain the specific decision: Track what a culture calls itself and what outsiders use",
          "Define the applicable contract and limits for Invented exonym endonym",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track what a culture calls itself and what outsiders use; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track what a culture calls itself and what outsiders use",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:544",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-trade-language-names",
      "slug": "invented-trade-language-names",
      "name": "Invented trade language names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-trade-language-names/",
        "ja": "/ja/tools/invented-trade-language-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Create contact forms distinct from native language names",
      "task": "Create contact forms distinct from native language names",
      "searchIntent": {
        "primary": "Complete the task: Create contact forms distinct from native language names",
        "queryHypothesis": "invented trade language names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to create contact forms distinct from native language names?",
        "When should invented trade language names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Create contact forms distinct from native language names",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Create contact forms distinct from native language names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Create contact forms distinct from native language names versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Create contact forms distinct from native language names versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Create contact forms distinct from native language names versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Create contact forms distinct from native language names",
        "outline": [
          "Explain the specific decision: Create contact forms distinct from native language names",
          "Define the applicable contract and limits for Invented trade language names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Create contact forms distinct from native language names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Create contact forms distinct from native language names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:545",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-diaspora-name-adaptation",
      "slug": "invented-diaspora-name-adaptation",
      "name": "Invented diaspora name adaptation",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-diaspora-name-adaptation/",
        "ja": "/ja/tools/invented-diaspora-name-adaptation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Preserve identity across declared language contact rules",
      "task": "Preserve identity across declared language contact rules",
      "searchIntent": {
        "primary": "Complete the task: Preserve identity across declared language contact rules",
        "queryHypothesis": "invented diaspora name adaptation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve identity across declared language contact rules?",
        "When should invented diaspora name adaptation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve identity across declared language contact rules",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve identity across declared language contact rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-trade-language-names",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Preserve identity across declared language contact rules versus Create contact forms distinct from native language names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-clan-name-affixes",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Preserve identity across declared language contact rules versus Enforce a declared clan marker across eligible members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-loan-adaptation",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Preserve identity across declared language contact rules versus Apply explicit sound substitutions to borrowed names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve identity across declared language contact rules",
        "outline": [
          "Explain the specific decision: Preserve identity across declared language contact rules",
          "Define the applicable contract and limits for Invented diaspora name adaptation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve identity across declared language contact rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve identity across declared language contact rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:546",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-colonization-name-policy",
      "slug": "invented-colonization-name-policy",
      "name": "Invented colonization name policy",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-colonization-name-policy/",
        "ja": "/ja/tools/invented-colonization-name-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Distinguish imposed labels from self identification in the story",
      "task": "Distinguish imposed labels from self identification in the story",
      "searchIntent": {
        "primary": "Complete the task: Distinguish imposed labels from self identification in the story",
        "queryHypothesis": "invented colonization name policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish imposed labels from self identification in the story?",
        "When should invented colonization name policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish imposed labels from self identification in the story",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish imposed labels from self identification in the story. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Distinguish imposed labels from self identification in the story versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-construct-creator-assigned-name",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Distinguish imposed labels from self identification in the story versus Contrast creator labels with the construct's self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish imposed labels from self identification in the story versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish imposed labels from self identification in the story",
        "outline": [
          "Explain the specific decision: Distinguish imposed labels from self identification in the story",
          "Define the applicable contract and limits for Invented colonization name policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish imposed labels from self identification in the story; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish imposed labels from self identification in the story",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:547",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-resistance-names",
      "slug": "invented-resistance-names",
      "name": "Invented resistance names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-resistance-names/",
        "ja": "/ja/tools/invented-resistance-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Link chosen forms to authored political acts without real group claims",
      "task": "Link chosen forms to authored political acts without real group claims",
      "searchIntent": {
        "primary": "Complete the task: Link chosen forms to authored political acts without real group claims",
        "queryHypothesis": "invented resistance names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link chosen forms to authored political acts without real group claims?",
        "When should invented resistance names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link chosen forms to authored political acts without real group claims",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link chosen forms to authored political acts without real group claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-naming-ceremony",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Link chosen forms to authored political acts without real group claims versus Link name assignment to authored social rituals and timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Link chosen forms to authored political acts without real group claims versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Link chosen forms to authored political acts without real group claims versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link chosen forms to authored political acts without real group claims",
        "outline": [
          "Explain the specific decision: Link chosen forms to authored political acts without real group claims",
          "Define the applicable contract and limits for Invented resistance names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link chosen forms to authored political acts without real group claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link chosen forms to authored political acts without real group claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:548",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-religious-personal-names",
      "slug": "invented-religious-personal-names",
      "name": "Invented religious personal names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-religious-personal-names/",
        "ja": "/ja/tools/invented-religious-personal-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define devotional components within a fictional belief system",
      "task": "Define devotional components within a fictional belief system",
      "searchIntent": {
        "primary": "Complete the task: Define devotional components within a fictional belief system",
        "queryHypothesis": "invented religious personal names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define devotional components within a fictional belief system?",
        "When should invented religious personal names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define devotional components within a fictional belief system",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define devotional components within a fictional belief system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Define devotional components within a fictional belief system versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alien-personal-name-anatomy",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define devotional components within a fictional belief system versus Define meaningful components within an invented species grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Define devotional components within a fictional belief system versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define devotional components within a fictional belief system",
        "outline": [
          "Explain the specific decision: Define devotional components within a fictional belief system",
          "Define the applicable contract and limits for Invented religious personal names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define devotional components within a fictional belief system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define devotional components within a fictional belief system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:549",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-secular-name-reform",
      "slug": "invented-secular-name-reform",
      "name": "Invented secular name reform",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-secular-name-reform/",
        "ja": "/ja/tools/invented-secular-name-reform/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Model a culture changing its naming institutions over time",
      "task": "Model a culture changing its naming institutions over time",
      "searchIntent": {
        "primary": "Complete the task: Model a culture changing its naming institutions over time",
        "queryHypothesis": "invented secular name reform",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model a culture changing its naming institutions over time?",
        "When should invented secular name reform be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model a culture changing its naming institutions over time",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model a culture changing its naming institutions over time. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-citizenship-name-reform",
          "score": 0.26477272727272727,
          "sharedProfile": false,
          "difference": "Model a culture changing its naming institutions over time versus Model policy change and individual exceptions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-spelling-reform",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Model a culture changing its naming institutions over time versus Map old and new spellings while retaining character identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Model a culture changing its naming institutions over time versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model a culture changing its naming institutions over time",
        "outline": [
          "Explain the specific decision: Model a culture changing its naming institutions over time",
          "Define the applicable contract and limits for Invented secular name reform",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model a culture changing its naming institutions over time; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model a culture changing its naming institutions over time",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:550",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-posthumous-name-rules",
      "slug": "invented-posthumous-name-rules",
      "name": "Invented posthumous name rules",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-posthumous-name-rules/",
        "ja": "/ja/tools/invented-posthumous-name-rules/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Keep living and memorial references consistent",
      "task": "Keep living and memorial references consistent",
      "searchIntent": {
        "primary": "Complete the task: Keep living and memorial references consistent",
        "queryHypothesis": "invented posthumous name rules",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep living and memorial references consistent?",
        "When should invented posthumous name rules be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep living and memorial references consistent",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep living and memorial references consistent. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-settlement-pronunciation",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep living and memorial references consistent versus Keep place derived character references consistent at the table; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-mourning-name-ritual",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep living and memorial references consistent versus Tie memorial references to authored relationships and beliefs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-lineage-chain",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Keep living and memorial references consistent versus Build multigeneration references with a readable shortening policy; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep living and memorial references consistent",
        "outline": [
          "Explain the specific decision: Keep living and memorial references consistent",
          "Define the applicable contract and limits for Invented posthumous name rules",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep living and memorial references consistent; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep living and memorial references consistent",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:551",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-commoner-register",
      "slug": "invented-commoner-register",
      "name": "Invented commoner register",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-commoner-register/",
        "ja": "/ja/tools/invented-commoner-register/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define structural differences without equating status and virtue",
      "task": "Define structural differences without equating status and virtue",
      "searchIntent": {
        "primary": "Complete the task: Define structural differences without equating status and virtue",
        "queryHypothesis": "invented commoner register",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define structural differences without equating status and virtue?",
        "When should invented commoner register be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define structural differences without equating status and virtue",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define structural differences without equating status and virtue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-social-register-naming",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Define structural differences without equating status and virtue versus Compare public formality with private address without stereotyping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Define structural differences without equating status and virtue versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-resistance-names",
          "score": 0.13083333333333333,
          "sharedProfile": true,
          "difference": "Define structural differences without equating status and virtue versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define structural differences without equating status and virtue",
        "outline": [
          "Explain the specific decision: Define structural differences without equating status and virtue",
          "Define the applicable contract and limits for Invented commoner register",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define structural differences without equating status and virtue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define structural differences without equating status and virtue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:553",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-multilingual-household",
      "slug": "invented-multilingual-household",
      "name": "Invented multilingual household",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-multilingual-household/",
        "ja": "/ja/tools/invented-multilingual-household/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Combine two rule systems through declared family choices",
      "task": "Combine two rule systems through declared family choices",
      "searchIntent": {
        "primary": "Complete the task: Combine two rule systems through declared family choices",
        "queryHypothesis": "invented multilingual household",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to combine two rule systems through declared family choices?",
        "When should invented multilingual household be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Combine two rule systems through declared family choices",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Combine two rule systems through declared family choices. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-foster-household-naming",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Combine two rule systems through declared family choices versus Preserve separate legal and informal family relationships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Combine two rule systems through declared family choices versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Combine two rule systems through declared family choices versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Combine two rule systems through declared family choices",
        "outline": [
          "Explain the specific decision: Combine two rule systems through declared family choices",
          "Define the applicable contract and limits for Invented multilingual household",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Combine two rule systems through declared family choices; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Combine two rule systems through declared family choices",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:554",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-border-culture-names",
      "slug": "invented-border-culture-names",
      "name": "Invented border culture names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-border-culture-names/",
        "ja": "/ja/tools/invented-border-culture-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Model mixed conventions without treating them as random blends",
      "task": "Model mixed conventions without treating them as random blends",
      "searchIntent": {
        "primary": "Complete the task: Model mixed conventions without treating them as random blends",
        "queryHypothesis": "invented border culture names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model mixed conventions without treating them as random blends?",
        "When should invented border culture names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model mixed conventions without treating them as random blends",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model mixed conventions without treating them as random blends. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-resistance-names",
          "score": 0.128125,
          "sharedProfile": true,
          "difference": "Model mixed conventions without treating them as random blends versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-occupation-surnames",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Model mixed conventions without treating them as random blends versus Model when an occupational label becomes hereditary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-surname-inheritance",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Model mixed conventions without treating them as random blends versus Model family transmission independently of given name generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model mixed conventions without treating them as random blends",
        "outline": [
          "Explain the specific decision: Model mixed conventions without treating them as random blends",
          "Define the applicable contract and limits for Invented border culture names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model mixed conventions without treating them as random blends; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model mixed conventions without treating them as random blends",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:555",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-name-loan-adaptation",
      "slug": "invented-name-loan-adaptation",
      "name": "Invented name loan adaptation",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-name-loan-adaptation/",
        "ja": "/ja/tools/invented-name-loan-adaptation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Apply explicit sound substitutions to borrowed names",
      "task": "Apply explicit sound substitutions to borrowed names",
      "searchIntent": {
        "primary": "Complete the task: Apply explicit sound substitutions to borrowed names",
        "queryHypothesis": "invented name loan adaptation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply explicit sound substitutions to borrowed names?",
        "When should invented name loan adaptation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply explicit sound substitutions to borrowed names",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply explicit sound substitutions to borrowed names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Apply explicit sound substitutions to borrowed names versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-house-name-particles",
          "score": 0.16285714285714287,
          "sharedProfile": true,
          "difference": "Apply explicit sound substitutions to borrowed names versus Apply particles and capitalization consistently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-historical-sound-change",
          "score": 0.08928571428571427,
          "sharedProfile": true,
          "difference": "Apply explicit sound substitutions to borrowed names versus Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply explicit sound substitutions to borrowed names",
        "outline": [
          "Explain the specific decision: Apply explicit sound substitutions to borrowed names",
          "Define the applicable contract and limits for Invented name loan adaptation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply explicit sound substitutions to borrowed names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply explicit sound substitutions to borrowed names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:556",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-historical-sound-change",
      "slug": "invented-historical-sound-change",
      "name": "Invented historical sound change",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-historical-sound-change/",
        "ja": "/ja/tools/invented-historical-sound-change/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fantasy and speculative-fiction writers building related names across generations of one invented language.",
      "scenario": "Two formerly distinct personal names converge after a declared change; an author needs the transformation history without treating the shared spelling as shared identity.",
      "task": "Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation.",
      "searchIntent": {
        "primary": "Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation.",
        "queryHypothesis": "invented historical sound change",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What does a derived historical form actually prove?",
        "When can two older names converge without becoming one identity?"
      ],
      "inputs": [
        {
          "key": "roots",
          "use": "Stable root/person IDs, original display and explicitly segmented symbols; symbols are authored units, not inferred phonetics."
        },
        {
          "key": "checkpoints",
          "use": "Ordered era IDs and labels that choose which dated rules have taken effect."
        },
        {
          "key": "rules",
          "use": "Unique chronological rule positions; literal source/target token sequences, left/right adjacent contexts and optional word boundaries."
        },
        {
          "key": "exceptions",
          "use": "Explicit root/rule skip with expected pre-rule tokens and an authored reason; stale exceptions fail rather than silently exempt a changed form."
        }
      ],
      "rules": [
        "Never infer a root’s pronunciation, attestation, historical language or etymology from spelling.",
        "Keep roots and person identities stable as derived displays change.",
        "Apply rules by explicit era/order, not input row order; reject ambiguous positions.",
        "Use a finite left-to-right non-overlapping pass within each rule; output from one match is not recursively processed by that same rule. Later rules see the previous result.",
        "Evaluate contexts against the pre-rule token sequence. Deletion can create an empty form, which is unresolved rather than replaced with a convenient token.",
        "Check exception expectations against the actual pre-rule state; a reason is a declared exception, not scholarly evidence.",
        "Group equal derived displays at each checkpoint without merging identities or inferring kinship.",
        "Enforce worksheet, token, rule and output limits with explicit failures; no partial trace described as complete."
      ],
      "requiredData": [
        {
          "description": "Original segmented-root lexicon and fictional era/rule fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Creator-authored unit inventories and contexts; no real phonetic or historical dataset planned",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Never infer a root’s pronunciation, attestation, historical language or etymology from spelling.",
        "Keep roots and person identities stable as derived displays change.",
        "Apply rules by explicit era/order, not input row order; reject ambiguous positions.",
        "Use a finite left-to-right non-overlapping pass within each rule; output from one match is not recursively processed by that same rule. Later rules see the previous result.",
        "Evaluate contexts against the pre-rule token sequence. Deletion can create an empty form, which is unresolved rather than replaced with a convenient token.",
        "Check exception expectations against the actual pre-rule state; a reason is a declared exception, not scholarly evidence.",
        "Group equal derived displays at each checkpoint without merging identities or inferring kinship.",
        "Enforce worksheet, token, rule and output limits with explicit failures; no partial trace described as complete."
      ],
      "outputs": [
        "Root-by-era derived forms with exact token traces, rule matches and skipped exceptions",
        "Convergence groups retaining every source identity",
        "Private derivation handoff and a comparison of altered rule ordering"
      ],
      "capabilities": [
        "Trace context-conditioned changes and one-pass overlap through several explicit eras.",
        "Reveal two distinct roots converging in one era while keeping their original identities and exception provenance."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "This is a diachronic derivation audit of an existing named lexicon, rather than a component generator or an exact alias-knowledge view. It consumes explicit segments, era checkpoints and dated context rules, outputs all intermediate forms and convergence groups, and compares a changed rule order without resampling roots.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "world-naming-grammar-builder",
          "difference": "The current grammar workbench combines components and applies literal transforms for newly constructed names. The proposed tool transforms supplied identity-scoped roots through dated contextual token rules, distinguishes one-pass overlap from recursive rewriting and compares convergence per era. These differences are demonstrated within the recorded local implementation and browser evidence."
        }
      },
      "nearestTools": [
        {
          "id": "nw-invented-seasonal-name-change",
          "score": 0.19652173913043477,
          "sharedProfile": true,
          "difference": "Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation. versus Define repeatable seasonal forms with stable identity underneath; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-dialect-name-variation",
          "score": 0.12023809523809523,
          "sharedProfile": true,
          "difference": "Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation. versus Derive regional forms from a documented fictional mapping; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation. versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A plausible-looking historical form needs an authored derivation; a shared later spelling is not proof of a shared person or ancestor.",
        "outline": [
          "The awakened speaker and the choir’s inherited refrain",
          "Choose symbols without claiming a historical phonology",
          "Read one context-bound pass",
          "Inspect converging roots before choosing a modern display",
          "Separate deliberate retention from an unexplained exception"
        ],
        "story": "A long-sleeping singer returns to a choir that has changed the form used in an inherited refrain. The singer chooses which form to perform; tracing how two names converged prevents the director from merging two roles in the score.",
        "storyAnalysis": "An older form can remain a chosen performance identity while a derived community form is used in the refrain. Replacing every source root with its modern surface would erase the distinction the derivation revealed.",
        "evidence": "Original complete EN/JA choir guides, unit derivation fixtures, HIST tests and observed browser workflows.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/historical.md",
        "localizedBodies": {
          "en": "content/en/historical.md",
          "ja": "content/ja/historical.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A context edit changes only matches in the declared environment.",
        "Changing the order of noncommuting rules changes actual derived forms and exposes the trace.",
        "Permuting input rows preserves outputs when explicit positions remain the same.",
        "A stale exception, unknown token or ambiguous rule position fails visibly.",
        "Convergent outputs remain separate in comparisons, favorites and exports.",
        "Deletion and unsupported size bounds never produce an invented attested name."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:557",
      "profileSource": "data/profiles.json#world-grammar",
      "specBatch": "batch-06",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Task-specific state/trace rules, ambiguity handling and original bilingual explanation; not a measured effort estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "historical",
        "engineFiles": [
          "web/historical-sound-change.mjs",
          "web/historical-view.mjs",
          "web/historical-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/historical.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "units",
          "label": [
            "Exact authored units · JSON",
            "作者が定義した単位・JSON"
          ],
          "type": "textarea",
          "default": "[\n  \"K\",\n  \"a\",\n  \"v\",\n  \"e\",\n  \"n\",\n  \"b\",\n  \"i\"\n]",
          "help": [
            "1–60 exact strings; at most 16 UTF-16 units each. These are authored symbols, not inferred phonetic values. No Unicode normalization is applied.",
            "1〜60の正確な文字列、各16単位以内。作者の記号であり、発音を推測しません。Unicodeの正規化もしません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "roots",
          "label": [
            "Identity-scoped roots · JSON",
            "人物別の元の名・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"older\",\n    \"person\": \"singer\",\n    \"original\": \"Kavena\",\n    \"segments\": [\n      \"K\",\n      \"a\",\n      \"v\",\n      \"e\",\n      \"n\",\n      \"a\"\n    ]\n  },\n  {\n    \"id\": \"other\",\n    \"person\": \"gardener\",\n    \"original\": \"Kabena\",\n    \"segments\": [\n      \"K\",\n      \"a\",\n      \"b\",\n      \"e\",\n      \"n\",\n      \"a\"\n    ]\n  }\n]",
          "help": [
            "id, person, original display, and 1–64 declared segments. An original spelling is retained independently of the joined segments. Up to 20 roots.",
            "id、person、original、指定したsegmentsを1〜64個。元の表示は単位を結合した表記と別に保持します。元の名は20件まで。"
          ],
          "maxLength": 150000
        },
        {
          "key": "checkpoints",
          "label": [
            "Era checkpoints · JSON",
            "時代の確認点・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"early\",\n    \"label\": \"Early form\",\n    \"at\": 0\n  },\n  {\n    \"id\": \"middle\",\n    \"label\": \"Middle form\",\n    \"at\": 1\n  },\n  {\n    \"id\": \"late\",\n    \"label\": \"Late form\",\n    \"at\": 2\n  }\n]",
          "help": [
            "1–4 unique id/label/at records. at is an authored integer 0–10000, not a historical date. Root-by-checkpoint outputs are limited to 80.",
            "id/label/atは1〜4件で、位置も重複させません。atは0〜10000の作者の整数で、史実の日付ではありません。元の名と時代の組は80件以内。"
          ],
          "maxLength": 150000
        },
        {
          "key": "rules",
          "label": [
            "Ordered context rules · JSON",
            "順序と文脈の規則・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"shift-v\",\n    \"at\": 1,\n    \"order\": 0,\n    \"from\": [\n      \"v\"\n    ],\n    \"to\": [\n      \"b\"\n    ],\n    \"left\": [\n      \"a\"\n    ],\n    \"right\": [\n      \"e\"\n    ],\n    \"start\": false,\n    \"end\": false\n  },\n  {\n    \"id\": \"raise-e\",\n    \"at\": 1,\n    \"order\": 1,\n    \"from\": [\n      \"e\"\n    ],\n    \"to\": [\n      \"i\"\n    ],\n    \"left\": [\n      \"b\"\n    ],\n    \"right\": [\n      \"n\"\n    ],\n    \"start\": false,\n    \"end\": false\n  },\n  {\n    \"id\": \"drop-a\",\n    \"at\": 2,\n    \"order\": 0,\n    \"from\": [\n      \"a\"\n    ],\n    \"to\": [],\n    \"left\": [],\n    \"right\": [],\n    \"start\": false,\n    \"end\": true\n  }\n]",
          "help": [
            "0–50 rules. from is nonempty; to/left/right can be empty. All tokens must be declared units. start/end anchor the outer edge of the complete context. One non-overlapping left-to-right pass per rule; intermediate forms ≤128 units.",
            "0〜50件。fromは空不可、to/left/rightは空可。全て登録した単位を使います。start/endは文脈全体の外側の境界。各規則を左から重複なしで一度適用し、途中の形は128単位以内。"
          ],
          "maxLength": 150000
        },
        {
          "key": "exceptions",
          "label": [
            "Explicit retained forms · JSON",
            "明示的に保持する例外・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "root/rule/expected/reason. expected is the exact pre-rule token array. The rule is skipped only for that root, with potential match sites still shown. A stale expectation fails the affected derivation.",
            "root/rule/expected/reason。expectedは適用前の正確な単位配列。その元の名だけ規則を省き、候補の一致位置も示します。期待した形と違う例外では対象の推導を止めます。"
          ],
          "maxLength": 150000
        },
        {
          "key": "orderProposal",
          "label": [
            "Unapplied alternate order · JSON",
            "未適用の別の順序案・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"rule\": \"shift-v\",\n    \"order\": 1\n  },\n  {\n    \"rule\": \"raise-e\",\n    \"order\": 0\n  }\n]",
          "help": [
            "Known rule ID and new order only; era and roots stay fixed. This computes another trace, without editing working rules. A conflicting order or stale exception in the proposal leaves the current derivation available. Use [] for no comparison.",
            "既存のruleと新しいorderだけ。時代と元の名を固定し、現在の規則を編集せず別の経路を計算します。順序の衝突や案の例外不一致でも現在の推導は残します。比較しない場合は[]。"
          ],
          "maxLength": 150000
        }
      ]
    },
    {
      "id": "nw-invented-spelling-reform",
      "slug": "invented-spelling-reform",
      "name": "Invented spelling reform",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-spelling-reform/",
        "ja": "/ja/tools/invented-spelling-reform/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Map old and new spellings while retaining character identity",
      "task": "Map old and new spellings while retaining character identity",
      "searchIntent": {
        "primary": "Complete the task: Map old and new spellings while retaining character identity",
        "queryHypothesis": "invented spelling reform",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map old and new spellings while retaining character identity?",
        "When should invented spelling reform be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map old and new spellings while retaining character identity",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map old and new spellings while retaining character identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-secular-name-reform",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Map old and new spellings while retaining character identity versus Model a culture changing its naming institutions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Map old and new spellings while retaining character identity versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Map old and new spellings while retaining character identity versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map old and new spellings while retaining character identity",
        "outline": [
          "Explain the specific decision: Map old and new spellings while retaining character identity",
          "Define the applicable contract and limits for Invented spelling reform",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map old and new spellings while retaining character identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map old and new spellings while retaining character identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:558",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-dialect-name-variation",
      "slug": "invented-dialect-name-variation",
      "name": "Invented dialect name variation",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-dialect-name-variation/",
        "ja": "/ja/tools/invented-dialect-name-variation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Derive regional forms from a documented fictional mapping",
      "task": "Derive regional forms from a documented fictional mapping",
      "searchIntent": {
        "primary": "Complete the task: Derive regional forms from a documented fictional mapping",
        "queryHypothesis": "invented dialect name variation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive regional forms from a documented fictional mapping?",
        "When should invented dialect name variation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive regional forms from a documented fictional mapping",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive regional forms from a documented fictional mapping. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-achievement-names",
          "score": 0.23194444444444443,
          "sharedProfile": true,
          "difference": "Derive regional forms from a documented fictional mapping versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.15125,
          "sharedProfile": true,
          "difference": "Derive regional forms from a documented fictional mapping versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-resistance-names",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Derive regional forms from a documented fictional mapping versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive regional forms from a documented fictional mapping",
        "outline": [
          "Explain the specific decision: Derive regional forms from a documented fictional mapping",
          "Define the applicable contract and limits for Invented dialect name variation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive regional forms from a documented fictional mapping; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive regional forms from a documented fictional mapping",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:559",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-sacred-name-avoidance",
      "slug": "invented-sacred-name-avoidance",
      "name": "Invented sacred name avoidance",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-sacred-name-avoidance/",
        "ja": "/ja/tools/invented-sacred-name-avoidance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define who may speak which name in which context",
      "task": "Define who may speak which name in which context",
      "searchIntent": {
        "primary": "Complete the task: Define who may speak which name in which context",
        "queryHypothesis": "invented sacred name avoidance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define who may speak which name in which context?",
        "When should invented sacred name avoidance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define who may speak which name in which context",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define who may speak which name in which context. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Define who may speak which name in which context versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Define who may speak which name in which context versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Define who may speak which name in which context versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define who may speak which name in which context",
        "outline": [
          "Explain the specific decision: Define who may speak which name in which context",
          "Define the applicable contract and limits for Invented sacred name avoidance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define who may speak which name in which context; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define who may speak which name in which context",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:560",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-legal-name-layers",
      "slug": "invented-legal-name-layers",
      "name": "Invented legal name layers",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-legal-name-layers/",
        "ja": "/ja/tools/invented-legal-name-layers/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Separate citizenship, household and personal chosen components",
      "task": "Separate citizenship, household and personal chosen components",
      "searchIntent": {
        "primary": "Complete the task: Separate citizenship, household and personal chosen components",
        "queryHypothesis": "invented legal name layers",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate citizenship, household and personal chosen components?",
        "When should invented legal name layers be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate citizenship, household and personal chosen components",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate citizenship, household and personal chosen components. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-space-colony-name-registry",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Separate citizenship, household and personal chosen components versus Separate habitat citizenship from personal and household identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Separate citizenship, household and personal chosen components versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.15125,
          "sharedProfile": true,
          "difference": "Separate citizenship, household and personal chosen components versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate citizenship, household and personal chosen components",
        "outline": [
          "Explain the specific decision: Separate citizenship, household and personal chosen components",
          "Define the applicable contract and limits for Invented legal name layers",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate citizenship, household and personal chosen components; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate citizenship, household and personal chosen components",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:561",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-names-without-surnames",
      "slug": "invented-names-without-surnames",
      "name": "Invented names without surnames",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-names-without-surnames/",
        "ja": "/ja/tools/invented-names-without-surnames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Design a reference system that does not assume family names",
      "task": "Design a reference system that does not assume family names",
      "searchIntent": {
        "primary": "Complete the task: Design a reference system that does not assume family names",
        "queryHypothesis": "invented names without surnames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a reference system that does not assume family names?",
        "When should invented names without surnames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a reference system that does not assume family names",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a reference system that does not assume family names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Design a reference system that does not assume family names versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-occupation-surnames",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Design a reference system that does not assume family names versus Model when an occupational label becomes hereditary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-mishearing",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Design a reference system that does not assume family names versus Design recoverable mishearings that do not depend on false phonetics; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a reference system that does not assume family names",
        "outline": [
          "Explain the specific decision: Design a reference system that does not assume family names",
          "Define the applicable contract and limits for Invented names without surnames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a reference system that does not assume family names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a reference system that does not assume family names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:562",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-collective-identity-names",
      "slug": "invented-collective-identity-names",
      "name": "Invented collective identity names",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-collective-identity-names/",
        "ja": "/ja/tools/invented-collective-identity-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Name members whose society treats identity as shared",
      "task": "Name members whose society treats identity as shared",
      "searchIntent": {
        "primary": "Complete the task: Name members whose society treats identity as shared",
        "queryHypothesis": "invented collective identity names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to name members whose society treats identity as shared?",
        "When should invented collective identity names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Name members whose society treats identity as shared",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Name members whose society treats identity as shared. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-swarm-character-continuity",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Name members whose society treats identity as shared versus Preserve identity when constituent members change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-name-succession",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Name members whose society treats identity as shared versus Transfer a communal identity without erasing individual histories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-confession-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Name members whose society treats identity as shared versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Name members whose society treats identity as shared",
        "outline": [
          "Explain the specific decision: Name members whose society treats identity as shared",
          "Define the applicable contract and limits for Invented collective identity names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Name members whose society treats identity as shared; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Name members whose society treats identity as shared",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:563",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-seasonal-name-change",
      "slug": "invented-seasonal-name-change",
      "name": "Invented seasonal name change",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-seasonal-name-change/",
        "ja": "/ja/tools/invented-seasonal-name-change/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Define repeatable seasonal forms with stable identity underneath",
      "task": "Define repeatable seasonal forms with stable identity underneath",
      "searchIntent": {
        "primary": "Complete the task: Define repeatable seasonal forms with stable identity underneath",
        "queryHypothesis": "invented seasonal name change",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define repeatable seasonal forms with stable identity underneath?",
        "When should invented seasonal name change be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define repeatable seasonal forms with stable identity underneath",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define repeatable seasonal forms with stable identity underneath. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Define repeatable seasonal forms with stable identity underneath versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-historical-sound-change",
          "score": 0.19652173913043477,
          "sharedProfile": true,
          "difference": "Define repeatable seasonal forms with stable identity underneath versus Derive era-specific name forms from supplied tokenized roots through ordered, context-bound fictional sound-change rules, preserving every identity and intermediate derivation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-plant-person-seasonal-identity",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Define repeatable seasonal forms with stable identity underneath versus Link seasonal forms to continuity in an invented biology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define repeatable seasonal forms with stable identity underneath",
        "outline": [
          "Explain the specific decision: Define repeatable seasonal forms with stable identity underneath",
          "Define the applicable contract and limits for Invented seasonal name change",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define repeatable seasonal forms with stable identity underneath; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define repeatable seasonal forms with stable identity underneath",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:564",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-numerical-name-grammar",
      "slug": "invented-numerical-name-grammar",
      "name": "Invented numerical name grammar",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-numerical-name-grammar/",
        "ja": "/ja/tools/invented-numerical-name-grammar/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Explain how sequence and individuality coexist in names",
      "task": "Explain how sequence and individuality coexist in names",
      "searchIntent": {
        "primary": "Complete the task: Explain how sequence and individuality coexist in names",
        "queryHypothesis": "invented numerical name grammar",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain how sequence and individuality coexist in names?",
        "When should invented numerical name grammar be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain how sequence and individuality coexist in names",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain how sequence and individuality coexist in names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-achievement-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Explain how sequence and individuality coexist in names versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-ceremony",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Explain how sequence and individuality coexist in names versus Link name assignment to authored social rituals and timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Explain how sequence and individuality coexist in names versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain how sequence and individuality coexist in names",
        "outline": [
          "Explain the specific decision: Explain how sequence and individuality coexist in names",
          "Define the applicable contract and limits for Invented numerical name grammar",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain how sequence and individuality coexist in names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain how sequence and individuality coexist in names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:565",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-sensory-name-translation",
      "slug": "invented-sensory-name-translation",
      "name": "Invented sensory name translation",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-sensory-name-translation/",
        "ja": "/ja/tools/invented-sensory-name-translation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Translate nonspoken identity cues into readable narrative labels",
      "task": "Translate nonspoken identity cues into readable narrative labels",
      "searchIntent": {
        "primary": "Complete the task: Translate nonspoken identity cues into readable narrative labels",
        "queryHypothesis": "invented sensory name translation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to translate nonspoken identity cues into readable narrative labels?",
        "When should invented sensory name translation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Translate nonspoken identity cues into readable narrative labels",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Translate nonspoken identity cues into readable narrative labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nonhuman-identity-translation",
          "score": 0.3063636363636364,
          "sharedProfile": false,
          "difference": "Translate nonspoken identity cues into readable narrative labels versus Convert an authored sensory identity system into readable labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonverbal-character-naming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Translate nonspoken identity cues into readable narrative labels versus Separate communicated identity from other characters' labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-collective-identity-names",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Translate nonspoken identity cues into readable narrative labels versus Name members whose society treats identity as shared; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Translate nonspoken identity cues into readable narrative labels",
        "outline": [
          "Explain the specific decision: Translate nonspoken identity cues into readable narrative labels",
          "Define the applicable contract and limits for Invented sensory name translation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Translate nonspoken identity cues into readable narrative labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Translate nonspoken identity cues into readable narrative labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:566",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-name-corpus-consistency",
      "slug": "invented-name-corpus-consistency",
      "name": "Invented name corpus consistency",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-name-corpus-consistency/",
        "ja": "/ja/tools/invented-name-corpus-consistency/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Check a supplied corpus against authored grammar rules",
      "task": "Check a supplied corpus against authored grammar rules",
      "searchIntent": {
        "primary": "Complete the task: Check a supplied corpus against authored grammar rules",
        "queryHypothesis": "invented name corpus consistency",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check a supplied corpus against authored grammar rules?",
        "When should invented name corpus consistency be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check a supplied corpus against authored grammar rules",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check a supplied corpus against authored grammar rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-family-continuity",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Check a supplied corpus against authored grammar rules versus Check new relatives against established family naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-system-reader-load",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Check a supplied corpus against authored grammar rules versus Test grammar complexity against reader recall exercises; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-generated-biography-name-fit",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Check a supplied corpus against authored grammar rules versus Check a generated name against explicit biography fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check a supplied corpus against authored grammar rules",
        "outline": [
          "Explain the specific decision: Check a supplied corpus against authored grammar rules",
          "Define the applicable contract and limits for Invented name corpus consistency",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check a supplied corpus against authored grammar rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check a supplied corpus against authored grammar rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:567",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-morphology-collision-audit",
      "slug": "invented-morphology-collision-audit",
      "name": "Invented morphology collision audit",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-morphology-collision-audit/",
        "ja": "/ja/tools/invented-morphology-collision-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Detect when generated forms collapse across grammatical operations",
      "task": "Detect when generated forms collapse across grammatical operations",
      "searchIntent": {
        "primary": "Complete the task: Detect when generated forms collapse across grammatical operations",
        "queryHypothesis": "invented morphology collision audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect when generated forms collapse across grammatical operations?",
        "When should invented morphology collision audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect when generated forms collapse across grammatical operations",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect when generated forms collapse across grammatical operations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-fallback-audit",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Detect when generated forms collapse across grammatical operations versus Detect when a missing translation shows a misleading identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-consistency-audit",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Detect when generated forms collapse across grammatical operations versus Find mismatched author forms across a supplied publication list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-terminology-drift-audit",
          "score": 0.15,
          "sharedProfile": false,
          "difference": "Detect when generated forms collapse across grammatical operations versus Detect one identity translated inconsistently across episodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect when generated forms collapse across grammatical operations",
        "outline": [
          "Explain the specific decision: Detect when generated forms collapse across grammatical operations",
          "Define the applicable contract and limits for Invented morphology collision audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect when generated forms collapse across grammatical operations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect when generated forms collapse across grammatical operations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:568",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-invented-naming-system-reader-load",
      "slug": "invented-naming-system-reader-load",
      "name": "Invented naming system reader load",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-naming-system-reader-load/",
        "ja": "/ja/tools/invented-naming-system-reader-load/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Test grammar complexity against reader recall exercises",
      "task": "Test grammar complexity against reader recall exercises",
      "searchIntent": {
        "primary": "Complete the task: Test grammar complexity against reader recall exercises",
        "queryHypothesis": "invented naming system reader load",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test grammar complexity against reader recall exercises?",
        "When should invented naming system reader load be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test grammar complexity against reader recall exercises",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test grammar complexity against reader recall exercises. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.18833333333333332,
          "sharedProfile": true,
          "difference": "Test grammar complexity against reader recall exercises versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Test grammar complexity against reader recall exercises versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-taboo-system",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Test grammar complexity against reader recall exercises versus Exclude prohibited forms with an explicit cultural rule ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test grammar complexity against reader recall exercises",
        "outline": [
          "Explain the specific decision: Test grammar complexity against reader recall exercises",
          "Define the applicable contract and limits for Invented naming system reader load",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test grammar complexity against reader recall exercises; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test grammar complexity against reader recall exercises",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:571",
      "profileSource": "data/profiles.json#world-grammar"
    },
    {
      "id": "nw-character-epithet-builder",
      "slug": "character-epithet-builder",
      "name": "Character epithet builder",
      "category": "titles",
      "urls": {
        "en": "/en/tools/character-epithet-builder/",
        "ja": "/ja/tools/character-epithet-builder/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Connect an epithet to an authored deed and observer perspective",
      "task": "Resolve reputation-based epithets from authored deeds, witnesses and audience adoption at a selected story point.",
      "searchIntent": {
        "primary": "Complete the task: Connect an epithet to an authored deed and observer perspective",
        "queryHypothesis": "character epithet builder",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect an epithet to an authored deed and observer perspective?",
        "When should character epithet builder be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "deeds",
          "use": "Stable event ID, subject identity, chapter and authored event description."
        },
        {
          "key": "epithets",
          "use": "Proposed epithet ID, literal display and required deed IDs."
        },
        {
          "key": "witnesses",
          "use": "Audience/event knowledge or rumor transmission with dates."
        },
        {
          "key": "adoption",
          "use": "Audience acceptance, rejection or hostile usage and its stated reason."
        }
      ],
      "rules": [
        "Only deeds assigned to the selected person can satisfy that person’s epithet.",
        "Prerequisites and knowledge must exist by the scene chapter.",
        "Keep hostile use, self-rejection and narrator endorsement distinct.",
        "No claimed historical meaning is generated from fictional components.",
        "A revised or withdrawn deed reopens all dependent epithets.",
        "Do not treat a witness report as proof that an event is true outside the authored model.",
        "Hide earned epithet before the deed becomes known"
      ],
      "requiredData": [
        {
          "description": "Original story events and audience knowledge",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Author-supplied epithet forms; no sourced mythology list",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Only deeds assigned to the selected person can satisfy that person’s epithet.",
        "Prerequisites and knowledge must exist by the scene chapter.",
        "Keep hostile use, self-rejection and narrator endorsement distinct.",
        "No claimed historical meaning is generated from fictional components.",
        "A revised or withdrawn deed reopens all dependent epithets.",
        "Do not treat a witness report as proof that an event is true outside the authored model."
      ],
      "outputs": [
        "Available, disputed and blocked epithets per audience",
        "Prerequisite and knowledge trace",
        "Production sheet explaining the cost of using a label",
        "Spoiler warning and allowed reference"
      ],
      "capabilities": [
        "Compare audiences that praise and condemn the same event.",
        "Invalidate dependent reputation labels when an event is rewritten without erasing earlier scene records."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "An earned reputation name depends on events and who has heard or accepted them, rather than office tenure or arbitrary adjective combinations.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "rules",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "fictional-ceremonial-full-style",
          "difference": "Ceremony uses offices and institutional recognition; epithets use deed prerequisites, witness/rumor reach and audience-specific adoption. Neither implies the other."
        }
      },
      "nearestTools": [
        {
          "id": "nw-world-naming-grammar-builder",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Resolve reputation-based epithets from authored deeds, witnesses and audience adoption at a selected story point. versus Define phonotactics and morphology before generating personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-island-community-name-collisions",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Resolve reputation-based epithets from authored deeds, witnesses and audience adoption at a selected story point. versus Resolve a small pool through authored relationship based references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-obituary-clue",
          "score": 0.04642857142857143,
          "sharedProfile": false,
          "difference": "Resolve reputation-based epithets from authored deeds, witnesses and audience adoption at a selected story point. versus Reconcile dates, names and witnesses in fictional records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "An epithet should preserve the viewpoint that gave it force.",
        "outline": [
          "Choose the deed before the label",
          "Map who heard the story",
          "Fictional scene: the bridge saver and the gate breaker",
          "Record rejection without rewriting hostile speech",
          "Reopen reputations after a revised event"
        ],
        "story": "Two neighborhoods name the same character after opening a floodgate. One survived because she opened it; another lost its bridge. Public notices apply praise and accusation to the same person, who declines both labels.",
        "storyAnalysis": "A neutral personal name hides the disagreement; a supposedly objective heroic epithet would erase one community’s loss.",
        "evidence": "Original event/adoption fixtures; no real community or historical epithet claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/epithet.md",
        "localizedBodies": {
          "en": "content/en/epithet.md",
          "ja": "content/ja/epithet.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "An unheard deed does not establish public adoption.",
        "A missing prerequisite blocks an epithet with the missing ID.",
        "Changing one event affects only dependent epithets.",
        "A person’s rejection does not automatically erase a hostile label; output preserves viewpoint.",
        "Office tenure alone never supplies an epithet deed.",
        "Early chapter cannot reveal a future achievement"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:574",
      "profileSource": "data/profiles.json#titles",
      "absorbedModules": [
        {
          "sourceId": "nw-epithet-spoiler-audit",
          "input": "deedChapter; observerKnowledge",
          "rule": "Hide earned epithet before the deed becomes known",
          "output": "Spoiler warning and allowed reference",
          "acceptance": "Early chapter cannot reveal a future achievement",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-battlefield-earned-epithet",
          "input": "Authored identities and versioned deeds; audience knowledge channel and date; explicit adoption intervals; optional personal acceptance/rejection.",
          "rule": "Keep audience use, deed/version prerequisites, knowledge and self-acceptance distinct. Reopen dependencies when the account changes; an audience’s hostile use is not erased by refusal.",
          "output": "Per-audience adopted, unadopted, rejected, unsupported or disputed labels; private dependency traces and chapter comparison. No public spoiler-safe sheet or objective reputation score.",
          "acceptance": "Opposed audiences retain different labels; no knowledge does not imply adoption; new version requires reassessment and new knowledge; earlier scene query remains available; hostile usage survives personal rejection.",
          "evidence": [
            "EPITHET-01",
            "EPITHET-02",
            "EPITHET-03",
            "EPITHET-04",
            "EPITHET-07",
            "reports/epithet-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-hero-reputation-names",
          "input": "Authored identities and versioned deeds; audience knowledge channel and date; explicit adoption intervals; optional personal acceptance/rejection.",
          "rule": "Keep audience use, deed/version prerequisites, knowledge and self-acceptance distinct. Reopen dependencies when the account changes; an audience’s hostile use is not erased by refusal.",
          "output": "Per-audience adopted, unadopted, rejected, unsupported or disputed labels; private dependency traces and chapter comparison. No public spoiler-safe sheet or objective reputation score.",
          "acceptance": "Opposed audiences retain different labels; no knowledge does not imply adoption; new version requires reassessment and new knowledge; earlier scene query remains available; hostile usage survives personal rejection.",
          "evidence": [
            "EPITHET-01",
            "EPITHET-02",
            "EPITHET-03",
            "EPITHET-04",
            "EPITHET-07",
            "reports/epithet-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-defamatory-epithet-perspective",
          "input": "Authored identities and versioned deeds; audience knowledge channel and date; explicit adoption intervals; optional personal acceptance/rejection.",
          "rule": "Keep audience use, deed/version prerequisites, knowledge and self-acceptance distinct. Reopen dependencies when the account changes; an audience’s hostile use is not erased by refusal.",
          "output": "Per-audience adopted, unadopted, rejected, unsupported or disputed labels; private dependency traces and chapter comparison. No public spoiler-safe sheet or objective reputation score.",
          "acceptance": "Opposed audiences retain different labels; no knowledge does not imply adoption; new version requires reassessment and new knowledge; earlier scene query remains available; hostile usage survives personal rejection.",
          "evidence": [
            "EPITHET-01",
            "EPITHET-02",
            "EPITHET-03",
            "EPITHET-04",
            "EPITHET-07",
            "reports/epithet-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-posthumous-epithet-revision",
          "input": "Authored identities and versioned deeds; audience knowledge channel and date; explicit adoption intervals; optional personal acceptance/rejection.",
          "rule": "Keep audience use, deed/version prerequisites, knowledge and self-acceptance distinct. Reopen dependencies when the account changes; an audience’s hostile use is not erased by refusal.",
          "output": "Per-audience adopted, unadopted, rejected, unsupported or disputed labels; private dependency traces and chapter comparison. No public spoiler-safe sheet or objective reputation score.",
          "acceptance": "Opposed audiences retain different labels; no knowledge does not imply adoption; new version requires reassessment and new knowledge; earlier scene query remains available; hostile usage survives personal rejection.",
          "evidence": [
            "EPITHET-01",
            "EPITHET-02",
            "EPITHET-03",
            "EPITHET-04",
            "EPITHET-07",
            "reports/epithet-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "specBatch": "batch-02",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "epithet",
        "engineFiles": [
          "web/reputation-epithets.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/epithet.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "People · JSON",
            "人物・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"a\",\n    \"name\": \"Mira Vale\"\n  }\n]",
          "help": null
        },
        {
          "key": "deeds",
          "label": [
            "Versioned deeds · JSON",
            "出来事の版・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"gate\",\n    \"version\": 1,\n    \"person\": \"a\",\n    \"eventChapter\": 2,\n    \"effectiveChapter\": 2,\n    \"status\": \"affirmed\",\n    \"description\": \"Mira opened the floodgate; the lower quay drained while the old footbridge was lost.\"\n  },\n  {\n    \"id\": \"gate\",\n    \"version\": 2,\n    \"person\": \"a\",\n    \"eventChapter\": 2,\n    \"effectiveChapter\": 7,\n    \"status\": \"affirmed\",\n    \"description\": \"Revised account: the gate was opened jointly, not by Mira alone.\"\n  }\n]",
          "help": [
            "id, version, person, eventChapter, effectiveChapter, affirmed/withdrawn status and description. New revisions preserve subject and event chapter. This is a private author audit.",
            "id、version、person、eventChapter、effectiveChapter、affirmed/withdrawnのstatus、description。改稿でも人物と発生章を保持します。作者用の非公開点検です。"
          ]
        },
        {
          "key": "epithets",
          "label": [
            "Proposed epithets & prerequisites · JSON",
            "異名と条件・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"saver\",\n    \"person\": \"a\",\n    \"display\": \"Quay Saver\",\n    \"requires\": [\n      {\n        \"deed\": \"gate\",\n        \"version\": 1\n      }\n    ]\n  },\n  {\n    \"id\": \"breaker\",\n    \"person\": \"a\",\n    \"display\": \"Bridge Breaker\",\n    \"requires\": [\n      {\n        \"deed\": \"gate\",\n        \"version\": 1\n      }\n    ]\n  }\n]",
          "help": [
            "Every label requires 1–12 explicit deed/version references for the same person. A revised version reopens that dependency.",
            "各異名には同じ人物の出来事と版を1〜12件指定します。版が変わると条件を再点検します。"
          ]
        },
        {
          "key": "knowledge",
          "label": [
            "Audience knowledge · JSON",
            "聴衆の知識・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"audience\": \"quay\",\n    \"deed\": \"gate\",\n    \"version\": 1,\n    \"learnedChapter\": 2,\n    \"channel\": \"witness\"\n  },\n  {\n    \"audience\": \"bridge\",\n    \"deed\": \"gate\",\n    \"version\": 1,\n    \"learnedChapter\": 3,\n    \"channel\": \"report\"\n  }\n]",
          "help": [
            "audience, deed, version, learnedChapter, witness/report/rumor channel; optional note. Knowledge does not automatically update to a later deed revision.",
            "audience、deed、version、learnedChapter、witness/report/rumorのchannel、任意のnote。新しい版の知識へ自動更新しません。"
          ]
        },
        {
          "key": "adoption",
          "label": [
            "Audience adoption intervals · JSON",
            "聴衆の採用期間・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"audience\": \"quay\",\n    \"epithet\": \"saver\",\n    \"from\": 3,\n    \"to\": null,\n    \"stance\": \"praise\",\n    \"reason\": \"The saved homes organize the quay account.\"\n  },\n  {\n    \"audience\": \"bridge\",\n    \"epithet\": \"breaker\",\n    \"from\": 3,\n    \"to\": null,\n    \"stance\": \"hostile\",\n    \"reason\": \"The missing crossing organizes the bridge account.\"\n  }\n]",
          "help": [
            "Inclusive from/to; null means no end. stance is praise, hostile or reject. Overlap for one audience and label is a conflict.",
            "from/toは両端を含み、nullは終わりなし。stanceはpraise、hostile、reject。同じ聴衆と異名の重複期間は矛盾です。"
          ]
        },
        {
          "key": "stances",
          "label": [
            "Personal stance · JSON",
            "本人の態度・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"epithet\": \"saver\",\n    \"from\": 3,\n    \"to\": null,\n    \"stance\": \"reject\",\n    \"reason\": \"Mira declines sole credit.\"\n  },\n  {\n    \"epithet\": \"breaker\",\n    \"from\": 3,\n    \"to\": null,\n    \"stance\": \"reject\",\n    \"reason\": \"Mira rejects being reduced to the bridge loss.\"\n  }\n]",
          "help": [
            "accept/reject by epithet and interval. The person’s rejection does not erase another audience’s hostile use.",
            "異名と期間にaccept/rejectを指定。本人の拒否で別の聴衆の敵意による使用は消えません。"
          ]
        },
        {
          "key": "audiences",
          "label": [
            "Audience IDs · 1–4",
            "聴衆ID・1〜4件"
          ],
          "type": "text",
          "default": "quay, bridge",
          "help": null
        },
        {
          "key": "chapter",
          "label": [
            "Scene chapter",
            "場面の章"
          ],
          "type": "number",
          "default": 4,
          "help": null
        },
        {
          "key": "compareChapter",
          "label": [
            "Compare with chapter · optional",
            "比較する章・任意"
          ],
          "type": "text",
          "default": "",
          "help": null
        }
      ]
    },
    {
      "id": "nw-earned-title-progression",
      "slug": "earned-title-progression",
      "name": "Earned title progression",
      "category": "titles",
      "urls": {
        "en": "/en/tools/earned-title-progression/",
        "ja": "/ja/tools/earned-title-progression/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Sequence titles across actual narrative achievements",
      "task": "Sequence titles across actual narrative achievements",
      "searchIntent": {
        "primary": "Complete the task: Sequence titles across actual narrative achievements",
        "queryHypothesis": "earned title progression",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to sequence titles across actual narrative achievements?",
        "When should earned title progression be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Sequence titles across actual narrative achievements",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Sequence titles across actual narrative achievements. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Sequence titles across actual narrative achievements versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-recurring-villain-title-chain",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Sequence titles across actual narrative achievements versus Track changing epithets across encounters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-title-reward",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Sequence titles across actual narrative achievements versus Create earned titles tied to actual in game actions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Sequence titles across actual narrative achievements",
        "outline": [
          "Explain the specific decision: Sequence titles across actual narrative achievements",
          "Define the applicable contract and limits for Earned title progression",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Sequence titles across actual narrative achievements; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Sequence titles across actual narrative achievements",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:575",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-regnal-numbering-consistency",
      "slug": "regnal-numbering-consistency",
      "name": "Regnal numbering consistency",
      "category": "titles",
      "urls": {
        "en": "/en/tools/regnal-numbering-consistency/",
        "ja": "/ja/tools/regnal-numbering-consistency/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fantasy, alternate-world, comic and game creators maintaining reused reign names and chronicle props.",
      "scenario": "One person inherits two crowns with different numbered histories; a disputed earlier holder changes which numeral belongs in a letter.",
      "task": "Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions.",
      "searchIntent": {
        "primary": "Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions.",
        "queryHypothesis": "regnal numbering consistency",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Which earlier holders actually count in this fictional chronicle?",
        "Does a ruler returning to the same throne keep or advance the numeral?"
      ],
      "inputs": [
        {
          "key": "people",
          "use": "Stable person IDs and exact personal/birth-name labels, distinct from reign forms."
        },
        {
          "key": "series",
          "use": "Named crown/chronicle series and explicit count-by-person or count-by-accession rule."
        },
        {
          "key": "baselines",
          "use": "Per-series/name-key declared prior accession count, ordered prior people or unknown history; no implicit zero."
        },
        {
          "key": "decisions",
          "use": "Linked include/exclude/unresolved decisions shared by specified entries; no inference from legitimacy or gender."
        },
        {
          "key": "accessions",
          "use": "Dated, tie-ordered entries with person, series, exact equivalence key, reign display, inclusion decision and optional claimed numeral."
        },
        {
          "key": "numeralStyle",
          "use": "Decimal or explicitly described Roman rendering of a computed number; presentation is separate from counting."
        }
      ],
      "rules": [
        "Preserve personal identity independently of reign form and crown series.",
        "Order by declared time and tie order, never by incidental input-row order.",
        "Require a baseline for every used series/name key; null means unknown, not zero.",
        "An accession-count rule counts each included event; a person-count rule retains a previously assigned ordinal for that person/key/series.",
        "Treat exact equivalence keys as author declarations, not inferred linguistic relationships.",
        "Enumerate at most ten linked unresolved decisions and preserve all resulting ordinal possibilities; exceeding the bound stops rather than selecting an arbitrary history.",
        "An excluded entry gets no assigned ordinal; a conditionally included entry is explicitly conditional.",
        "An entered claimed ordinal is matched, contradicted, conditional or unverifiable against the declared histories; no objective historical legitimacy is certified."
      ],
      "requiredData": [
        {
          "description": "Original two-crown, reaccession, tie-order, disputed-holder and unknown-baseline fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Creator-supplied prior-holder lists; no real-world dynasty list imported",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Preserve personal identity independently of reign form and crown series.",
        "Order by declared time and tie order, never by incidental input-row order.",
        "Require a baseline for every used series/name key; null means unknown, not zero.",
        "An accession-count rule counts each included event; a person-count rule retains a previously assigned ordinal for that person/key/series.",
        "Treat exact equivalence keys as author declarations, not inferred linguistic relationships.",
        "Enumerate at most ten linked unresolved decisions and preserve all resulting ordinal possibilities; exceeding the bound stops rather than selecting an arbitrary history.",
        "An excluded entry gets no assigned ordinal; a conditionally included entry is explicitly conditional.",
        "An entered claimed ordinal is matched, contradicted, conditional or unverifiable against the declared histories; no objective historical legitimacy is certified."
      ],
      "outputs": [
        "Per-entry ordinal candidates, inclusion possibilities, predecessor traces and exact rendered styles",
        "A claimed-number check with unknown/conditional states",
        "Alternative-history summary and a private numbering handoff"
      ],
      "capabilities": [
        "Compare person-count and accession-count effects on a returning ruler without merging their crowns.",
        "Show linked disputed inclusion changing several later numerals without pretending one historical claim is correct."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is an ordinal succession calculation, not resolving who currently holds an office or making a personal-name candidate. Counting by accession versus by person, unknown earlier history and disputed inclusion produce different numbers for the same supplied name.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "fictional-ceremonial-full-style",
          "difference": "Office tenure and audience recognition resolve a style at a scene. This tool counts prior included holders/events per series and explicit equivalence key, retaining one ordinal on reaccession only when the declared policy says so. Alternative disputed histories are enumerated, not resolved through an observer’s allegiance."
        }
      },
      "nearestTools": [
        {
          "id": "nw-regnal-number-clue",
          "score": 0.10421052631578948,
          "sharedProfile": false,
          "difference": "Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions. versus Base a deduction on a disclosed fictional succession system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-signature-consistency",
          "score": 0.1025,
          "sharedProfile": false,
          "difference": "Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions. versus Keep a drawn signature recognizable across localized editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-consistency-audit",
          "score": 0.10095238095238095,
          "sharedProfile": false,
          "difference": "Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions. versus Find mismatched author forms across a supplied publication list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A reign numeral records a counting contract; it is not a decorative suffix or a verdict about legitimate identity.",
        "outline": [
          "Original scene: two seals for one sovereign",
          "Define what a chronicle counts",
          "Reaccession and a shared name are different events",
          "Work through a disputed predecessor",
          "Read an unverified number on a prop"
        ],
        "story": "A courier brings one letter to a sovereign whose two crowns use different numbered histories. The mismatch is resolved by reading the series and inclusion rule, not by inventing another person or declaring one crown’s chronicle universally correct.",
        "storyAnalysis": "If the reign display changes but the equivalence key is retained, the counter stays connected; if the key changes deliberately, it opens another declared history. A numeral can expose which chronicle a prop follows without proving the author of a real document.",
        "evidence": "Original invented ledger and deterministic enumeration fixtures; no historical usage or corpus facts claimed.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/regnal.md",
        "localizedBodies": {
          "en": "content/en/regnal.md",
          "ja": "content/ja/regnal.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Permuting input rows does not change outputs when time and tie order stay fixed.",
        "The same person/key retains one ordinal on reaccession under person counting and advances under accession counting.",
        "The same reign form in different series can receive different numbers.",
        "Unresolved linked inclusion yields all bounded alternatives and never chooses the lowest as fact.",
        "Missing baselines or ambiguous same-time ordering fail explicitly; unknown baselines produce unverifiable claims.",
        "Changing an author’s exact name-equivalence key changes only its declared count scope.",
        "Dedicated previews, copies and private exports retain uncertainty rather than printing one unqualified numeral."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:577",
      "profileSource": "data/profiles.json#titles",
      "specBatch": "batch-04",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Explicit task states, scoped rules, traceable alternatives and bilingual original content; no time/cost estimate invented."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-royal-regnal-name",
          "input": "Stable personal IDs/names, explicit crown series and name-equivalence keys, dated accessions, known or unknown baselines and linked inclusion decisions.",
          "rule": "Do not infer a person from a reign display, linguistic equivalence from spelling, or legitimacy from a number. Keep crown counters separate and apply the declared person/accession policy; enumerate bounded unresolved inclusion.",
          "output": "Exact qualified numbered forms, claimed-number checks, hypothetical predecessor traces and a private all-history handoff.",
          "acceptance": "One person in two crowns can have different ordinals; returns keep or advance the ordinal under an actual policy change; unknown history is not zero; hypothetical inspection does not commit a history.",
          "evidence": [
            "REGNAL-01",
            "REGNAL-02",
            "REGNAL-05",
            "REGNAL-06",
            "REGNAL-07",
            "REGNAL-12",
            "reports/regnal-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-invented-royal-personal-grammar",
          "input": "Stable personal IDs/names, explicit crown series and name-equivalence keys, dated accessions, known or unknown baselines and linked inclusion decisions.",
          "rule": "Do not infer a person from a reign display, linguistic equivalence from spelling, or legitimacy from a number. Keep crown counters separate and apply the declared person/accession policy; enumerate bounded unresolved inclusion.",
          "output": "Exact qualified numbered forms, claimed-number checks, hypothetical predecessor traces and a private all-history handoff.",
          "acceptance": "One person in two crowns can have different ordinals; returns keep or advance the ordinal under an actual policy change; unknown history is not zero; hypothetical inspection does not commit a history.",
          "evidence": [
            "REGNAL-01",
            "REGNAL-02",
            "REGNAL-05",
            "REGNAL-06",
            "REGNAL-07",
            "REGNAL-12",
            "reports/regnal-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "regnal",
        "engineFiles": [
          "web/regnal-ledger.mjs",
          "web/regnal-history-ui.mjs",
          "web/regnal-view.mjs",
          "web/regnal-policy.js",
          "scripts/render-regnal-policy.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/regnal.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "Personal identities · JSON",
            "個人の身元・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"earlier\",\n    \"personalName\": \"Eren\"\n  },\n  {\n    \"id\": \"disputed\",\n    \"personalName\": \"Meral\"\n  },\n  {\n    \"id\": \"sovereign\",\n    \"personalName\": \"Sela\"\n  }\n]",
          "help": [
            "id and exact personalName. A reign display does not replace the person ID. Fictional fixtures, not real dynastic facts.",
            "idと正確なpersonalName。在位名で人物IDを置き換えません。創作例で、実在の王朝の事実ではありません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "series",
          "label": [
            "Numbering series · JSON",
            "番号の系統・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"north\",\n    \"label\": \"North Crown\",\n    \"unit\": \"people\"\n  },\n  {\n    \"id\": \"south\",\n    \"label\": \"South Crown\",\n    \"unit\": \"accessions\"\n  }\n]",
          "help": [
            "id, label, unit: people or accessions. Counters are separate for each series and name key.",
            "id、label、unitはpeopleかaccessions。系統と名のkeyごとに別に数えます。"
          ],
          "maxLength": 150000
        },
        {
          "key": "baselines",
          "label": [
            "Earlier histories · JSON",
            "以前の履歴・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"series\": \"north\",\n    \"key\": \"vela\",\n    \"priorCount\": 1,\n    \"priorPeople\": [\n      \"earlier\"\n    ]\n  },\n  {\n    \"series\": \"south\",\n    \"key\": \"vela\",\n    \"priorCount\": 3,\n    \"priorPeople\": null\n  }\n]",
          "help": [
            "Each series/key needs priorCount 0–3000 or null. priorPeople is null or a complete ordered list of exactly priorCount known people. People counting requires that list; unknown never becomes zero.",
            "各series/keyに0〜3000かnullのpriorCountを指定します。priorPeopleはnullか、priorCountと同数の既知の人物を並べた完全な順序です。peopleではその一覧が必要です。不明を0にしません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "decisions",
          "label": [
            "Linked inclusion decisions · JSON",
            "連動する算入判断・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"settled\",\n    \"label\": \"Included in this invented chronicle\",\n    \"state\": \"include\"\n  },\n  {\n    \"id\": \"claim\",\n    \"label\": \"Disputed earlier holder\",\n    \"state\": \"unresolved\"\n  },\n  {\n    \"id\": \"outside\",\n    \"label\": \"Not counted in this series\",\n    \"state\": \"exclude\"\n  }\n]",
          "help": [
            "include/exclude/unresolved. Entries sharing an ID share its inclusion choice in every hypothetical history. At most 10 used unresolved decisions; no legitimacy is inferred.",
            "include/exclude/unresolved。同じ判断IDを持つ記録は各仮定の履歴で一緒に算入・除外します。使用中の未解決判断は10件まで。正統性は推定しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "accessions",
          "label": [
            "Dated accession records · JSON",
            "日付付きの即位記録・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"n-claim\",\n    \"person\": \"disputed\",\n    \"series\": \"north\",\n    \"key\": \"vela\",\n    \"regnalName\": \"Vela\",\n    \"at\": 2,\n    \"order\": 0,\n    \"decision\": \"claim\",\n    \"claimed\": 2\n  },\n  {\n    \"id\": \"n-first\",\n    \"person\": \"sovereign\",\n    \"series\": \"north\",\n    \"key\": \"vela\",\n    \"regnalName\": \"Vela\",\n    \"at\": 4,\n    \"order\": 0,\n    \"decision\": \"settled\",\n    \"claimed\": 2\n  },\n  {\n    \"id\": \"s-first\",\n    \"person\": \"sovereign\",\n    \"series\": \"south\",\n    \"key\": \"vela\",\n    \"regnalName\": \"Vela\",\n    \"at\": 4,\n    \"order\": 0,\n    \"decision\": \"settled\",\n    \"claimed\": 4\n  },\n  {\n    \"id\": \"n-return\",\n    \"person\": \"sovereign\",\n    \"series\": \"north\",\n    \"key\": \"vela\",\n    \"regnalName\": \"Véla\",\n    \"at\": 7,\n    \"order\": 0,\n    \"decision\": \"settled\",\n    \"claimed\": 2\n  },\n  {\n    \"id\": \"n-outside\",\n    \"person\": \"disputed\",\n    \"series\": \"north\",\n    \"key\": \"vela\",\n    \"regnalName\": \"Vela\",\n    \"at\": 8,\n    \"order\": 0,\n    \"decision\": \"outside\",\n    \"claimed\": null\n  }\n]",
          "help": [
            "id/person/series/key/regnalName/at/order/decision/claimed. Dates are authored integers; order breaks ties inside the same series/key. Exact keys declare name equivalence; no linguistic matching is inferred. claimed is an integer or null.",
            "id/person/series/key/regnalName/at/order/decision/claimed。atは作者の整数時点、orderは同じseries/keyの同時点の順序です。keyで名の同等性を明示し、言語的な一致を推測しません。claimedは整数かnullです。"
          ],
          "maxLength": 150000
        },
        {
          "key": "numeralStyle",
          "label": [
            "Computed numeral display",
            "計算した番号の表示"
          ],
          "type": "select",
          "default": "roman",
          "help": [
            "Presentation only. The guide defines the conversion table; it does not establish a real royal naming custom.",
            "表示だけの選択です。変換表はガイドで定義し、実在の王室の慣習は認定しません。"
          ],
          "options": [
            [
              "roman",
              [
                "Roman numerals · I, II, III",
                "ローマ数字・I、II、III"
              ]
            ],
            [
              "decimal",
              [
                "Decimal · 1, 2, 3",
                "十進表記・1、2、3"
              ]
            ]
          ]
        }
      ]
    },
    {
      "id": "nw-royal-title-address-matrix",
      "slug": "royal-title-address-matrix",
      "name": "Royal title address matrix",
      "category": "titles",
      "urls": {
        "en": "/en/tools/royal-title-address-matrix/",
        "ja": "/ja/tools/royal-title-address-matrix/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Resolve forms by office, speaker and political recognition",
      "task": "Resolve forms by office, speaker and political recognition",
      "searchIntent": {
        "primary": "Complete the task: Resolve forms by office, speaker and political recognition",
        "queryHypothesis": "royal title address matrix",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve forms by office, speaker and political recognition?",
        "When should royal title address matrix be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve forms by office, speaker and political recognition",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve forms by office, speaker and political recognition. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-title-evidence-file",
          "score": 0.2125,
          "sharedProfile": false,
          "difference": "Resolve forms by office, speaker and political recognition versus Separate attested office forms from fictional inventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-relationship-graph",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Resolve forms by office, speaker and political recognition versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Resolve forms by office, speaker and political recognition versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve forms by office, speaker and political recognition",
        "outline": [
          "Explain the specific decision: Resolve forms by office, speaker and political recognition",
          "Define the applicable contract and limits for Royal title address matrix",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve forms by office, speaker and political recognition; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve forms by office, speaker and political recognition",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:578",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-disputed-throne-titles",
      "slug": "disputed-throne-titles",
      "name": "Disputed throne titles",
      "category": "titles",
      "urls": {
        "en": "/en/tools/disputed-throne-titles/",
        "ja": "/ja/tools/disputed-throne-titles/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Track rival claims without treating a title as verified legitimacy",
      "task": "Track rival claims without treating a title as verified legitimacy",
      "searchIntent": {
        "primary": "Complete the task: Track rival claims without treating a title as verified legitimacy",
        "queryHypothesis": "disputed throne titles",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track rival claims without treating a title as verified legitimacy?",
        "When should disputed throne titles be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track rival claims without treating a title as verified legitimacy",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track rival claims without treating a title as verified legitimacy. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track rival claims without treating a title as verified legitimacy versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track rival claims without treating a title as verified legitimacy versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-forgives-misnaming",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track rival claims without treating a title as verified legitimacy versus Show response and boundaries without treating forgiveness as required; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track rival claims without treating a title as verified legitimacy",
        "outline": [
          "Explain the specific decision: Track rival claims without treating a title as verified legitimacy",
          "Define the applicable contract and limits for Disputed throne titles",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track rival claims without treating a title as verified legitimacy; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track rival claims without treating a title as verified legitimacy",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:579",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-abdicated-ruler-reference",
      "slug": "abdicated-ruler-reference",
      "name": "Abdicated ruler reference",
      "category": "titles",
      "urls": {
        "en": "/en/tools/abdicated-ruler-reference/",
        "ja": "/ja/tools/abdicated-ruler-reference/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Distinguish retained courtesy forms from current authority",
      "task": "Distinguish retained courtesy forms from current authority",
      "searchIntent": {
        "primary": "Complete the task: Distinguish retained courtesy forms from current authority",
        "queryHypothesis": "abdicated ruler reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish retained courtesy forms from current authority?",
        "When should abdicated ruler reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish retained courtesy forms from current authority",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish retained courtesy forms from current authority. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-migration-naming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Distinguish retained courtesy forms from current authority versus Track retained, adapted and imposed forms across a journey; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-honorific-policy",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Distinguish retained courtesy forms from current authority versus Compare retained, translated and omitted forms with scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-in-records",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Distinguish retained courtesy forms from current authority versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish retained courtesy forms from current authority",
        "outline": [
          "Explain the specific decision: Distinguish retained courtesy forms from current authority",
          "Define the applicable contract and limits for Abdicated ruler reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish retained courtesy forms from current authority; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish retained courtesy forms from current authority",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:580",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-heir-courtesy-title",
      "slug": "heir-courtesy-title",
      "name": "Heir courtesy title",
      "category": "titles",
      "urls": {
        "en": "/en/tools/heir-courtesy-title/",
        "ja": "/ja/tools/heir-courtesy-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate an heir's style from the ruler's actual office",
      "task": "Separate an heir's style from the ruler's actual office",
      "searchIntent": {
        "primary": "Complete the task: Separate an heir's style from the ruler's actual office",
        "queryHypothesis": "heir courtesy title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate an heir's style from the ruler's actual office?",
        "When should heir courtesy title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate an heir's style from the ruler's actual office",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate an heir's style from the ruler's actual office. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-title-versus-personal-name",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Separate an heir's style from the ruler's actual office versus Choose references when office and individual interests conflict; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-title-drift",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Separate an heir's style from the ruler's actual office versus Compare office references against character promotions and succession; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Separate an heir's style from the ruler's actual office versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate an heir's style from the ruler's actual office",
        "outline": [
          "Explain the specific decision: Separate an heir's style from the ruler's actual office",
          "Define the applicable contract and limits for Heir courtesy title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate an heir's style from the ruler's actual office; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate an heir's style from the ruler's actual office",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:581",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-fictional-noble-title-system",
      "slug": "fictional-noble-title-system",
      "name": "Fictional noble title system",
      "category": "titles",
      "urls": {
        "en": "/en/tools/fictional-noble-title-system/",
        "ja": "/ja/tools/fictional-noble-title-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Define ranked titles using authored rules rather than historical claims",
      "task": "Define ranked titles using authored rules rather than historical claims",
      "searchIntent": {
        "primary": "Complete the task: Define ranked titles using authored rules rather than historical claims",
        "queryHypothesis": "fictional noble title system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define ranked titles using authored rules rather than historical claims?",
        "When should fictional noble title system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define ranked titles using authored rules rather than historical claims",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define ranked titles using authored rules rather than historical claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Define ranked titles using authored rules rather than historical claims versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-utopian-naming-institutions",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Define ranked titles using authored rules rather than historical claims versus Specify actual rules and exceptions rather than a positive style adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-uploaded-person-identity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define ranked titles using authored rules rather than historical claims versus Model continuity claims as story positions rather than scientific fact; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define ranked titles using authored rules rather than historical claims",
        "outline": [
          "Explain the specific decision: Define ranked titles using authored rules rather than historical claims",
          "Define the applicable contract and limits for Fictional noble title system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define ranked titles using authored rules rather than historical claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define ranked titles using authored rules rather than historical claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:582",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-noble-house-personal-reference",
      "slug": "noble-house-personal-reference",
      "name": "Noble house personal reference",
      "category": "titles",
      "urls": {
        "en": "/en/tools/noble-house-personal-reference/",
        "ja": "/ja/tools/noble-house-personal-reference/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Avoid confusing a house, estate and individual holder",
      "task": "Avoid confusing a house, estate and individual holder",
      "searchIntent": {
        "primary": "Complete the task: Avoid confusing a house, estate and individual holder",
        "queryHypothesis": "noble house personal reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid confusing a house, estate and individual holder?",
        "When should noble house personal reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid confusing a house, estate and individual holder",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid confusing a house, estate and individual holder. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-house-identity-system",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Avoid confusing a house, estate and individual holder versus Define house membership and inherited personal components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-former-name-reference-policy",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Avoid confusing a house, estate and individual holder versus Mark necessary historical references and avoid accidental exposure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Avoid confusing a house, estate and individual holder versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid confusing a house, estate and individual holder",
        "outline": [
          "Explain the specific decision: Avoid confusing a house, estate and individual holder",
          "Define the applicable contract and limits for Noble house personal reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid confusing a house, estate and individual holder; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid confusing a house, estate and individual holder",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:583",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-military-callsign-design",
      "slug": "military-callsign-design",
      "name": "Military callsign design",
      "category": "titles",
      "urls": {
        "en": "/en/tools/military-callsign-design/",
        "ja": "/ja/tools/military-callsign-design/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Derive fictional callsigns from unit practice and character history",
      "task": "Derive fictional callsigns from unit practice and character history",
      "searchIntent": {
        "primary": "Complete the task: Derive fictional callsigns from unit practice and character history",
        "queryHypothesis": "military callsign design",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive fictional callsigns from unit practice and character history?",
        "When should military callsign design be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive fictional callsigns from unit practice and character history",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive fictional callsigns from unit practice and character history. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-military-unit-callsign-roster",
          "score": 0.3025,
          "sharedProfile": false,
          "difference": "Derive fictional callsigns from unit practice and character history versus Keep unit identifiers distinct from individual callsigns; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mononym-character-design",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Derive fictional callsigns from unit practice and character history versus Maintain referential clarity for a character with one public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-locality-surnames",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Derive fictional callsigns from unit practice and character history versus Derive a surname from a supplied fictional place grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive fictional callsigns from unit practice and character history",
        "outline": [
          "Explain the specific decision: Derive fictional callsigns from unit practice and character history",
          "Define the applicable contract and limits for Military callsign design",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive fictional callsigns from unit practice and character history; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive fictional callsigns from unit practice and character history",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:584",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-religious-office-name",
      "slug": "religious-office-name",
      "name": "Religious office name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/religious-office-name/",
        "ja": "/ja/tools/religious-office-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate chosen religious identity from institutional rank",
      "task": "Separate chosen religious identity from institutional rank",
      "searchIntent": {
        "primary": "Complete the task: Separate chosen religious identity from institutional rank",
        "queryHypothesis": "religious office name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate chosen religious identity from institutional rank?",
        "When should religious office name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate chosen religious identity from institutional rank",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate chosen religious identity from institutional rank. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-society-member-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate chosen religious identity from institutional rank versus Separate rank, ceremonial name and outside identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate chosen religious identity from institutional rank versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate chosen religious identity from institutional rank versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate chosen religious identity from institutional rank",
        "outline": [
          "Explain the specific decision: Separate chosen religious identity from institutional rank",
          "Define the applicable contract and limits for Religious office name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate chosen religious identity from institutional rank; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate chosen religious identity from institutional rank",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:586",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-monastic-fictional-name-change",
      "slug": "monastic-fictional-name-change",
      "name": "Monastic fictional name change",
      "category": "titles",
      "urls": {
        "en": "/en/tools/monastic-fictional-name-change/",
        "ja": "/ja/tools/monastic-fictional-name-change/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Tie name adoption to an invented order's explicit practice",
      "task": "Tie name adoption to an invented order's explicit practice",
      "searchIntent": {
        "primary": "Complete the task: Tie name adoption to an invented order's explicit practice",
        "queryHypothesis": "monastic fictional name change",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie name adoption to an invented order's explicit practice?",
        "When should monastic fictional name change be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie name adoption to an invented order's explicit practice",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie name adoption to an invented order's explicit practice. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-naming-law-conflict",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Tie name adoption to an invented order's explicit practice versus Compare individual preference with an invented institution's demands; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-adoption-naming",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Tie name adoption to an invented order's explicit practice versus Integrate an outsider into an invented clan's explicit rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Tie name adoption to an invented order's explicit practice versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie name adoption to an invented order's explicit practice",
        "outline": [
          "Explain the specific decision: Tie name adoption to an invented order's explicit practice",
          "Define the applicable contract and limits for Monastic fictional name change",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie name adoption to an invented order's explicit practice; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie name adoption to an invented order's explicit practice",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:587",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-saint-like-fictional-title",
      "slug": "saint-like-fictional-title",
      "name": "Saint like fictional title",
      "category": "titles",
      "urls": {
        "en": "/en/tools/saint-like-fictional-title/",
        "ja": "/ja/tools/saint-like-fictional-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Model veneration within invented religion without asserting real canonization",
      "task": "Model veneration within invented religion without asserting real canonization",
      "searchIntent": {
        "primary": "Complete the task: Model veneration within invented religion without asserting real canonization",
        "queryHypothesis": "saint like fictional title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model veneration within invented religion without asserting real canonization?",
        "When should saint like fictional title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model veneration within invented religion without asserting real canonization",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model veneration within invented religion without asserting real canonization. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Model veneration within invented religion without asserting real canonization versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-forged-byline-clue",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Model veneration within invented religion without asserting real canonization versus Compare fictional attribution patterns without asserting real authentication expertise; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-guild-mastery-title",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Model veneration within invented religion without asserting real canonization versus Resolve titles by certification events in an invented guild; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model veneration within invented religion without asserting real canonization",
        "outline": [
          "Explain the specific decision: Model veneration within invented religion without asserting real canonization",
          "Define the applicable contract and limits for Saint like fictional title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model veneration within invented religion without asserting real canonization; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model veneration within invented religion without asserting real canonization",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:588",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-prophetic-name-restraint",
      "slug": "prophetic-name-restraint",
      "name": "Prophetic name restraint",
      "category": "titles",
      "urls": {
        "en": "/en/tools/prophetic-name-restraint/",
        "ja": "/ja/tools/prophetic-name-restraint/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Design an ambiguous epithet without making prophecy self proving",
      "task": "Design an ambiguous epithet without making prophecy self proving",
      "searchIntent": {
        "primary": "Complete the task: Design an ambiguous epithet without making prophecy self proving",
        "queryHypothesis": "prophetic name restraint",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design an ambiguous epithet without making prophecy self proving?",
        "When should prophetic name restraint be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design an ambiguous epithet without making prophecy self proving",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design an ambiguous epithet without making prophecy self proving. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rival-character-name-pairing",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Design an ambiguous epithet without making prophecy self proving versus Express opposition without making names indistinguishable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-motif-restraint",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Design an ambiguous epithet without making prophecy self proving versus Limit symbolic signals so a name does not announce the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-witness-protection-fiction-names",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Design an ambiguous epithet without making prophecy self proving versus Design fictional continuity without offering real evasion procedures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design an ambiguous epithet without making prophecy self proving",
        "outline": [
          "Explain the specific decision: Design an ambiguous epithet without making prophecy self proving",
          "Define the applicable contract and limits for Prophetic name restraint",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design an ambiguous epithet without making prophecy self proving; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design an ambiguous epithet without making prophecy self proving",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:589",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-villain-public-moniker",
      "slug": "villain-public-moniker",
      "name": "Villain public moniker",
      "category": "titles",
      "urls": {
        "en": "/en/tools/villain-public-moniker/",
        "ja": "/ja/tools/villain-public-moniker/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Track who coined the name and who rejects it",
      "task": "Track who coined the name and who rejects it",
      "searchIntent": {
        "primary": "Complete the task: Track who coined the name and who rejects it",
        "queryHypothesis": "villain public moniker",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track who coined the name and who rejects it?",
        "When should villain public moniker be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track who coined the name and who rejects it",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track who coined the name and who rejects it. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alien-human-nickname-negotiation",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track who coined the name and who rejects it versus Track who chooses a translated name and who accepts it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-betrayal",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track who coined the name and who rejects it versus Map who retains or rejects earlier intimate forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-corrects-public-record",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track who coined the name and who rejects it versus Trace the cost and story consequences of correction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track who coined the name and who rejects it",
        "outline": [
          "Explain the specific decision: Track who coined the name and who rejects it",
          "Define the applicable contract and limits for Villain public moniker",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track who coined the name and who rejects it; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track who coined the name and who rejects it",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:590",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-outlaw-bounty-poster-name",
      "slug": "outlaw-bounty-poster-name",
      "name": "Outlaw bounty poster name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/outlaw-bounty-poster-name/",
        "ja": "/ja/tools/outlaw-bounty-poster-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate official accusation, nickname and actual identity",
      "task": "Separate official accusation, nickname and actual identity",
      "searchIntent": {
        "primary": "Complete the task: Separate official accusation, nickname and actual identity",
        "queryHypothesis": "outlaw bounty poster name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate official accusation, nickname and actual identity?",
        "When should outlaw bounty poster name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate official accusation, nickname and actual identity",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate official accusation, nickname and actual identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-in-records",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate official accusation, nickname and actual identity versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate official accusation, nickname and actual identity versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-detective-notebook-identity-map",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate official accusation, nickname and actual identity versus Separate hypothesis, testimony and corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate official accusation, nickname and actual identity",
        "outline": [
          "Explain the specific decision: Separate official accusation, nickname and actual identity",
          "Define the applicable contract and limits for Outlaw bounty poster name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate official accusation, nickname and actual identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate official accusation, nickname and actual identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:592",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-arena-fighter-ring-name",
      "slug": "arena-fighter-ring-name",
      "name": "Arena fighter ring name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/arena-fighter-ring-name/",
        "ja": "/ja/tools/arena-fighter-ring-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Connect public persona, announcer readability and private identity",
      "task": "Connect public persona, announcer readability and private identity",
      "searchIntent": {
        "primary": "Complete the task: Connect public persona, announcer readability and private identity",
        "queryHypothesis": "arena fighter ring name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect public persona, announcer readability and private identity?",
        "When should arena fighter ring name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect public persona, announcer readability and private identity",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect public persona, announcer readability and private identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.26,
          "sharedProfile": false,
          "difference": "Connect public persona, announcer readability and private identity versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-idol-group-fictional-identities",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Connect public persona, announcer readability and private identity versus Keep stage persona and private identity relationships explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-outgrows-stage-identity",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Connect public persona, announcer readability and private identity versus Connect public persona change to career and self understanding; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect public persona, announcer readability and private identity",
        "outline": [
          "Explain the specific decision: Connect public persona, announcer readability and private identity",
          "Define the applicable contract and limits for Arena fighter ring name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect public persona, announcer readability and private identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect public persona, announcer readability and private identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:593",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-stage-character-performance-name",
      "slug": "stage-character-performance-name",
      "name": "Stage character performance name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/stage-character-performance-name/",
        "ja": "/ja/tools/stage-character-performance-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate a fictional performer from the role they play",
      "task": "Separate a fictional performer from the role they play",
      "searchIntent": {
        "primary": "Complete the task: Separate a fictional performer from the role they play",
        "queryHypothesis": "stage character performance name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a fictional performer from the role they play?",
        "When should stage character performance name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a fictional performer from the role they play",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a fictional performer from the role they play. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate a fictional performer from the role they play versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-outgrows-stage-identity",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate a fictional performer from the role they play versus Connect public persona change to career and self understanding; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate a fictional performer from the role they play versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a fictional performer from the role they play",
        "outline": [
          "Explain the specific decision: Separate a fictional performer from the role they play",
          "Define the applicable contract and limits for Stage character performance name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a fictional performer from the role they play; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a fictional performer from the role they play",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:594",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-wizard-order-name",
      "slug": "wizard-order-name",
      "name": "Wizard order name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/wizard-order-name/",
        "ja": "/ja/tools/wizard-order-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Apply fictional rank and initiation rules to a personal identity",
      "task": "Apply fictional rank and initiation rules to a personal identity",
      "searchIntent": {
        "primary": "Complete the task: Apply fictional rank and initiation rules to a personal identity",
        "queryHypothesis": "wizard order name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply fictional rank and initiation rules to a personal identity?",
        "When should wizard order name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply fictional rank and initiation rules to a personal identity",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply fictional rank and initiation rules to a personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-order-initiation-names",
          "score": 0.3952380952380952,
          "sharedProfile": false,
          "difference": "Apply fictional rank and initiation rules to a personal identity versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Apply fictional rank and initiation rules to a personal identity versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-society-member-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Apply fictional rank and initiation rules to a personal identity versus Separate rank, ceremonial name and outside identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply fictional rank and initiation rules to a personal identity",
        "outline": [
          "Explain the specific decision: Apply fictional rank and initiation rules to a personal identity",
          "Define the applicable contract and limits for Wizard order name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply fictional rank and initiation rules to a personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply fictional rank and initiation rules to a personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:595",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-knight-oath-name",
      "slug": "knight-oath-name",
      "name": "Knight oath name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/knight-oath-name/",
        "ja": "/ja/tools/knight-oath-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Tie a formal name to a specific fictional oath and sponsor",
      "task": "Tie a formal name to a specific fictional oath and sponsor",
      "searchIntent": {
        "primary": "Complete the task: Tie a formal name to a specific fictional oath and sponsor",
        "queryHypothesis": "knight oath name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie a formal name to a specific fictional oath and sponsor?",
        "When should knight oath name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie a formal name to a specific fictional oath and sponsor",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie a formal name to a specific fictional oath and sponsor. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-oath-name-contract",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Tie a formal name to a specific fictional oath and sponsor versus Define invented magical name permissions in player readable terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-bound-oath-breach",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Tie a formal name to a specific fictional oath and sponsor versus Define breach detection and consequences under authored rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-mourning-name-ritual",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Tie a formal name to a specific fictional oath and sponsor versus Tie memorial references to authored relationships and beliefs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie a formal name to a specific fictional oath and sponsor",
        "outline": [
          "Explain the specific decision: Tie a formal name to a specific fictional oath and sponsor",
          "Define the applicable contract and limits for Knight oath name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie a formal name to a specific fictional oath and sponsor; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie a formal name to a specific fictional oath and sponsor",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:596",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-guild-mastery-title",
      "slug": "guild-mastery-title",
      "name": "Guild mastery title",
      "category": "titles",
      "urls": {
        "en": "/en/tools/guild-mastery-title/",
        "ja": "/ja/tools/guild-mastery-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Resolve titles by certification events in an invented guild",
      "task": "Resolve titles by certification events in an invented guild",
      "searchIntent": {
        "primary": "Complete the task: Resolve titles by certification events in an invented guild",
        "queryHypothesis": "guild mastery title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve titles by certification events in an invented guild?",
        "When should guild mastery title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve titles by certification events in an invented guild",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve titles by certification events in an invented guild. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-guild-apprentice-names",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Resolve titles by certification events in an invented guild versus Track entry, mastery and departure forms under authored guild rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-earned-title-progression",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Resolve titles by certification events in an invented guild versus Sequence titles across actual narrative achievements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Resolve titles by certification events in an invented guild versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve titles by certification events in an invented guild",
        "outline": [
          "Explain the specific decision: Resolve titles by certification events in an invented guild",
          "Define the applicable contract and limits for Guild mastery title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve titles by certification events in an invented guild; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve titles by certification events in an invented guild",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:597",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-academic-fictional-honorific",
      "slug": "academic-fictional-honorific",
      "name": "Academic fictional honorific",
      "category": "titles",
      "urls": {
        "en": "/en/tools/academic-fictional-honorific/",
        "ja": "/ja/tools/academic-fictional-honorific/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate a fictional qualification from personal name fields",
      "task": "Separate a fictional qualification from personal name fields",
      "searchIntent": {
        "primary": "Complete the task: Separate a fictional qualification from personal name fields",
        "queryHypothesis": "academic fictional honorific",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a fictional qualification from personal name fields?",
        "When should academic fictional honorific be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a fictional qualification from personal name fields",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a fictional qualification from personal name fields. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-name-record",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate a fictional qualification from personal name fields versus Keep kanji, kana and approved pronunciation as separate fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-generated-biography-name-fit",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Separate a fictional qualification from personal name fields versus Check a generated name against explicit biography fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-honorific-policy-for-fiction",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate a fictional qualification from personal name fields versus Define a consistent policy using sourced language guidance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a fictional qualification from personal name fields",
        "outline": [
          "Explain the specific decision: Separate a fictional qualification from personal name fields",
          "Define the applicable contract and limits for Academic fictional honorific",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a fictional qualification from personal name fields; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a fictional qualification from personal name fields",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:598",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-investigator-public-reputation",
      "slug": "investigator-public-reputation",
      "name": "Investigator public reputation",
      "category": "titles",
      "urls": {
        "en": "/en/tools/investigator-public-reputation/",
        "ja": "/ja/tools/investigator-public-reputation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Contrast newspaper label, professional title and self identification",
      "task": "Contrast newspaper label, professional title and self identification",
      "searchIntent": {
        "primary": "Complete the task: Contrast newspaper label, professional title and self identification",
        "queryHypothesis": "investigator public reputation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast newspaper label, professional title and self identification?",
        "When should investigator public reputation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast newspaper label, professional title and self identification",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast newspaper label, professional title and self identification. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-construct-creator-assigned-name",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Contrast newspaper label, professional title and self identification versus Contrast creator labels with the construct's self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Contrast newspaper label, professional title and self identification versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mentor-public-private-address",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Contrast newspaper label, professional title and self identification versus Contrast training scenes and formal gatherings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast newspaper label, professional title and self identification",
        "outline": [
          "Explain the specific decision: Contrast newspaper label, professional title and self identification",
          "Define the applicable contract and limits for Investigator public reputation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast newspaper label, professional title and self identification; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast newspaper label, professional title and self identification",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:599",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-pirate-captain-sobriquet",
      "slug": "pirate-captain-sobriquet",
      "name": "Pirate captain sobriquet",
      "category": "titles",
      "urls": {
        "en": "/en/tools/pirate-captain-sobriquet/",
        "ja": "/ja/tools/pirate-captain-sobriquet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Keep reputation names attached to a specific holder and era",
      "task": "Keep reputation names attached to a specific holder and era",
      "searchIntent": {
        "primary": "Complete the task: Keep reputation names attached to a specific holder and era",
        "queryHypothesis": "pirate captain sobriquet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep reputation names attached to a specific holder and era?",
        "When should pirate captain sobriquet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep reputation names attached to a specific holder and era",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep reputation names attached to a specific holder and era. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Keep reputation names attached to a specific holder and era versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-coming-of-age-chosen-name",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Keep reputation names attached to a specific holder and era versus Connect a name decision to a specific act of agency; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Keep reputation names attached to a specific holder and era versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep reputation names attached to a specific holder and era",
        "outline": [
          "Explain the specific decision: Keep reputation names attached to a specific holder and era",
          "Define the applicable contract and limits for Pirate captain sobriquet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep reputation names attached to a specific holder and era; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep reputation names attached to a specific holder and era",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:600",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-shipboard-rank-reference",
      "slug": "shipboard-rank-reference",
      "name": "Shipboard rank reference",
      "category": "titles",
      "urls": {
        "en": "/en/tools/shipboard-rank-reference/",
        "ja": "/ja/tools/shipboard-rank-reference/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Handle promotions without replacing personal identity",
      "task": "Handle promotions without replacing personal identity",
      "searchIntent": {
        "primary": "Complete the task: Handle promotions without replacing personal identity",
        "queryHypothesis": "shipboard rank reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to handle promotions without replacing personal identity?",
        "When should shipboard rank reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Handle promotions without replacing personal identity",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Handle promotions without replacing personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-occupation-name-separation",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Handle promotions without replacing personal identity versus Keep role titles from replacing individual identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-downtime-household-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Handle promotions without replacing personal identity versus Extend a household without replacing established members; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Handle promotions without replacing personal identity versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Handle promotions without replacing personal identity",
        "outline": [
          "Explain the specific decision: Handle promotions without replacing personal identity",
          "Define the applicable contract and limits for Shipboard rank reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Handle promotions without replacing personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Handle promotions without replacing personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:601",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-inherited-mantle-identity",
      "slug": "inherited-mantle-identity",
      "name": "Inherited mantle identity",
      "category": "titles",
      "urls": {
        "en": "/en/tools/inherited-mantle-identity/",
        "ja": "/ja/tools/inherited-mantle-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Track successive people using one hero title",
      "task": "Track successive people using one hero title",
      "searchIntent": {
        "primary": "Complete the task: Track successive people using one hero title",
        "queryHypothesis": "inherited mantle identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track successive people using one hero title?",
        "When should inherited mantle identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track successive people using one hero title",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track successive people using one hero title. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-shared-alias-conspiracy",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Track successive people using one hero title versus Track multiple people using one handle across a timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-royal-identity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Track successive people using one hero title versus Manage birth title, assumed name and recognition triggers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-identity-ambiguity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Track successive people using one hero title versus Avoid merging different people solely because names match; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track successive people using one hero title",
        "outline": [
          "Explain the specific decision: Track successive people using one hero title",
          "Define the applicable contract and limits for Inherited mantle identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track successive people using one hero title; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track successive people using one hero title",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:602",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-shared-champion-title",
      "slug": "shared-champion-title",
      "name": "Shared champion title",
      "category": "titles",
      "urls": {
        "en": "/en/tools/shared-champion-title/",
        "ja": "/ja/tools/shared-champion-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Avoid assuming a title identifies a single person",
      "task": "Avoid assuming a title identifies a single person",
      "searchIntent": {
        "primary": "Complete the task: Avoid assuming a title identifies a single person",
        "queryHypothesis": "shared champion title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid assuming a title identifies a single person?",
        "When should shared champion title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid assuming a title identifies a single person",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid assuming a title identifies a single person. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-title-forgery-clue",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Avoid assuming a title identifies a single person versus Design verifiable fictional inconsistencies in a claimed title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prophecy-title-spoiler",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Avoid assuming a title identifies a single person versus Avoid exposing the future role in early character labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-city-district-surname-distribution",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid assuming a title identifies a single person versus Avoid equating every district with a single ethnicity or class; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid assuming a title identifies a single person",
        "outline": [
          "Explain the specific decision: Avoid assuming a title identifies a single person",
          "Define the applicable contract and limits for Shared champion title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid assuming a title identifies a single person; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid assuming a title identifies a single person",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:603",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-reclaimed-insult-name",
      "slug": "reclaimed-insult-name",
      "name": "Reclaimed insult name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/reclaimed-insult-name/",
        "ja": "/ja/tools/reclaimed-insult-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Trace who may use a reclaimed label and when",
      "task": "Trace who may use a reclaimed label and when",
      "searchIntent": {
        "primary": "Complete the task: Trace who may use a reclaimed label and when",
        "queryHypothesis": "reclaimed insult name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace who may use a reclaimed label and when?",
        "When should reclaimed insult name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace who may use a reclaimed label and when",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace who may use a reclaimed label and when. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-consent-map",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Trace who may use a reclaimed label and when versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace who may use a reclaimed label and when versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Trace who may use a reclaimed label and when versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace who may use a reclaimed label and when",
        "outline": [
          "Explain the specific decision: Trace who may use a reclaimed label and when",
          "Define the applicable contract and limits for Reclaimed insult name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace who may use a reclaimed label and when; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace who may use a reclaimed label and when",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:605",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-title-translation-ambiguity",
      "slug": "title-translation-ambiguity",
      "name": "Title translation ambiguity",
      "category": "titles",
      "urls": {
        "en": "/en/tools/title-translation-ambiguity/",
        "ja": "/ja/tools/title-translation-ambiguity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Preserve office function when a target language term is imperfect",
      "task": "Preserve office function when a target language term is imperfect",
      "searchIntent": {
        "primary": "Complete the task: Preserve office function when a target language term is imperfect",
        "queryHypothesis": "title translation ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve office function when a target language term is imperfect?",
        "When should title translation ambiguity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve office function when a target language term is imperfect",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve office function when a target language term is imperfect. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-title-versus-personal-name",
          "score": 0.1875,
          "sharedProfile": false,
          "difference": "Preserve office function when a target language term is imperfect versus Choose references when office and individual interests conflict; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-heir-courtesy-title",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Preserve office function when a target language term is imperfect versus Separate an heir's style from the ruler's actual office; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-title-drift",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Preserve office function when a target language term is imperfect versus Compare office references against character promotions and succession; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve office function when a target language term is imperfect",
        "outline": [
          "Explain the specific decision: Preserve office function when a target language term is imperfect",
          "Define the applicable contract and limits for Title translation ambiguity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve office function when a target language term is imperfect; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve office function when a target language term is imperfect",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:607",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-fictional-ceremonial-full-style",
      "slug": "fictional-ceremonial-full-style",
      "name": "Fictional ceremonial full style",
      "category": "titles",
      "urls": {
        "en": "/en/tools/fictional-ceremonial-full-style/",
        "ja": "/ja/tools/fictional-ceremonial-full-style/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Construct long styles with a short reference policy",
      "task": "Construct long styles with a short reference policy",
      "searchIntent": {
        "primary": "Complete the task: Construct long styles with a short reference policy",
        "queryHypothesis": "fictional ceremonial full style",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to construct long styles with a short reference policy?",
        "When should fictional ceremonial full style be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "offices",
          "use": "Stable office IDs, rank order and mutually exclusive tenure intervals."
        },
        {
          "key": "holders",
          "use": "Person IDs and accession or removal events."
        },
        {
          "key": "audience",
          "use": "Whose recognition rules govern the scene."
        },
        {
          "key": "lengthPolicy",
          "use": "Choose full ceremonial or context-relevant short reference."
        }
      ],
      "rules": [
        "Resolve holders by scene date, not by the last entered name.",
        "Reject overlapping exclusive tenures unless a disputed-claim state is explicit.",
        "Courtesy styles require an authored rule; do not infer historical practice.",
        "Shorten by declared priority without changing the holder's personal identity.",
        "Resolve full style and contextual short style from one office ledger"
      ],
      "requiredData": [
        {
          "description": "Original fictional office charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Authored succession and recognition ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Resolve holders by scene date, not by the last entered name.",
        "Reject overlapping exclusive tenures unless a disputed-claim state is explicit.",
        "Courtesy styles require an authored rule; do not infer historical practice.",
        "Shorten by declared priority without changing the holder's personal identity."
      ],
      "outputs": [
        "Resolved holder and tenure",
        "Full and short reference",
        "Excluded or disputed styles with reasons",
        "Full and short forms with recognition"
      ],
      "capabilities": [
        "Compare two audiences recognizing different claimants.",
        "Show how removal from office changes a short reference without rewriting earlier scenes."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Resolve office holders and audience-recognized styles at a dated scene; concatenating honorifics cannot decide who currently holds an office.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "character-epithet-builder",
          "difference": "An epithet follows reputation and deeds; this solver follows office tenure, recognition and explicitly permitted courtesy styles."
        }
      },
      "nearestTools": [
        {
          "id": "nw-character-select-name-cards",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Construct long styles with a short reference policy versus Compare full and short names with pronunciation support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-full-name-rhythm",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Construct long styles with a short reference policy versus Compare supplied name-reading variants within an authored prominence grid, count all permitted alignments and inspect minimum-cost traces without inventing pronunciation.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-full-name-overuse",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Construct long styles with a short reference policy versus Flag repetitions using configurable editorial context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A title identifies an office relationship at a moment, not a permanent string attached to a person.",
        "outline": [
          "Build the succession ledger first",
          "Recognized and claimed titles differ",
          "A deposition and two invitations",
          "Shorten for a scene without falsifying office",
          "Audit a regnal announcement"
        ],
        "story": "Fictional example: after an abdication, two delegations send invitations using different styles. The narrator identifies each as a political choice instead of treating both as the uncontested current ruler.",
        "storyAnalysis": "Replacing every title globally would falsify the earlier reign and conceal disagreement. Resolve each scene against time and audience.",
        "evidence": "Original office fixtures only; real royal or legal conventions require separate specialist sources.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/ceremony.md",
        "localizedBodies": {
          "en": "content/en/ceremony.md",
          "ja": "content/ja/ceremony.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A deposed holder receives no current-office style without an explicit courtesy exception.",
        "Overlapping exclusive tenure returns a conflict.",
        "Changing audience can change recognized title but not person ID.",
        "A zero-space budget returns overflow rather than an empty identity.",
        "Deposed holder loses current-office style unless a courtesy rule permits it"
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:610",
      "profileSource": "data/profiles.json#titles",
      "absorbedModules": [
        {
          "sourceId": "nw-title-overload-pruning",
          "input": "officeTimeline; sceneAudience",
          "rule": "Resolve full style and contextual short style from one office ledger",
          "output": "Full and short forms with recognition",
          "acceptance": "Deposed holder loses current-office style unless a courtesy rule permits it",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "redesign": {
        "required": true,
        "sourceId": "nw-title-overload-pruning",
        "mainTask": "Combine full-style construction and scene-appropriate shortening into one title resolution task with a timeline and speaker context.",
        "status": "contract-refined-awaiting-prototype"
      },
      "specBatch": "batch-01",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "ceremony",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs",
          "web/editorial-engines.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/editorial.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "People",
            "人物"
          ],
          "type": "textarea",
          "default": "a | Sela Morrow\nb | Oren Vale",
          "help": [
            "Person ID | unchanged personal name. All examples are invented.",
            "人物ID | 維持する個人名。例はすべて架空です。"
          ]
        },
        {
          "key": "offices",
          "label": [
            "Fictional offices",
            "架空の役職"
          ],
          "type": "textarea",
          "default": "harbor | Warden of the Harbor | 1\ncouncil | Speaker of the Council | 2",
          "help": [
            "Office ID | title | priority, lower first.",
            "役職ID | 称号 | 優先順位・小さい値が先。"
          ]
        },
        {
          "key": "tenures",
          "label": [
            "Tenures and explicit claims",
            "在任と明示した主張"
          ],
          "type": "textarea",
          "default": "harbor | a | 0 | 4 | held\nharbor | b | 5 | | held\nharbor | a | 5 | | claim\ncouncil | a | 2 | 9 | held",
          "help": [
            "Office ID | person ID | first chapter | last chapter, blank = no end | held/claim. Both chapter endpoints count.",
            "役職ID | 人物ID | 開始章 | 終了章・空欄は期限なし | held/claim。両端の章を含みます。"
          ]
        },
        {
          "key": "recognition",
          "label": [
            "Audience recognition rules",
            "聴衆ごとの承認"
          ],
          "type": "textarea",
          "default": "council | harbor | b | 5 |\nloyalists | harbor | a | 5 |\ncouncil | council | a | 2 | 9\nloyalists | council | a | 2 | 9",
          "help": [
            "Audience | office ID | recognized person ID | first chapter | last chapter. No rule means no recognized office style.",
            "聴衆 | 役職ID | 承認する人物ID | 開始章 | 終了章。ルールがなければ在任の称号を付けません。"
          ]
        },
        {
          "key": "personId",
          "label": [
            "Person to address",
            "称号を確認する人物ID"
          ],
          "type": "text",
          "default": "a",
          "help": null
        },
        {
          "key": "chapter",
          "label": [
            "Scene chapter",
            "場面の章"
          ],
          "type": "number",
          "default": 6,
          "help": null
        },
        {
          "key": "audienceA",
          "label": [
            "First audience",
            "第一の聴衆"
          ],
          "type": "text",
          "default": "council",
          "help": null
        },
        {
          "key": "audienceB",
          "label": [
            "Second audience · optional",
            "第二の聴衆・任意"
          ],
          "type": "text",
          "default": "loyalists",
          "help": null
        },
        {
          "key": "lengthPolicy",
          "label": [
            "Reference form",
            "使う表記"
          ],
          "type": "select",
          "default": "full",
          "help": null,
          "options": [
            [
              "full",
              [
                "Full ceremonial form",
                "正式な全称"
              ]
            ],
            [
              "short",
              [
                "Highest-priority style + name",
                "最優先の称号と個人名"
              ]
            ]
          ]
        },
        {
          "key": "budget",
          "label": [
            "Grapheme budget · 0–500",
            "文字単位の上限・0〜500"
          ],
          "type": "number",
          "default": 100,
          "help": null
        },
        {
          "key": "courtesy",
          "label": [
            "Explicit courtesy exceptions",
            "明示した儀礼上の例外"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Audience | person ID | courtesy style | first chapter | last chapter | priority. Never inferred after removal.",
            "聴衆 | 人物ID | 例外の表記 | 開始章 | 終了章 | 優先順位。退任後の例外は推測しません。"
          ]
        }
      ]
    },
    {
      "id": "nw-character-renounces-title",
      "slug": "character-renounces-title",
      "name": "Character renounces title",
      "category": "titles",
      "urls": {
        "en": "/en/tools/character-renounces-title/",
        "ja": "/ja/tools/character-renounces-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Update address and social reactions after rejection",
      "task": "Update address and social reactions after rejection",
      "searchIntent": {
        "primary": "Complete the task: Update address and social reactions after rejection",
        "queryHypothesis": "character renounces title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update address and social reactions after rejection?",
        "When should character renounces title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update address and social reactions after rejection",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update address and social reactions after rejection. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rank-change-address-timeline",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Update address and social reactions after rejection versus Update dialogue after promotions and demotions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Update address and social reactions after rejection versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-passes-on-title",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Update address and social reactions after rejection versus Preserve the outgoing and incoming holders' distinct identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update address and social reactions after rejection",
        "outline": [
          "Explain the specific decision: Update address and social reactions after rejection",
          "Define the applicable contract and limits for Character renounces title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update address and social reactions after rejection; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update address and social reactions after rejection",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:611",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-title-forgery-clue",
      "slug": "title-forgery-clue",
      "name": "Title forgery clue",
      "category": "titles",
      "urls": {
        "en": "/en/tools/title-forgery-clue/",
        "ja": "/ja/tools/title-forgery-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Design verifiable fictional inconsistencies in a claimed title",
      "task": "Design verifiable fictional inconsistencies in a claimed title",
      "searchIntent": {
        "primary": "Complete the task: Design verifiable fictional inconsistencies in a claimed title",
        "queryHypothesis": "title forgery clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design verifiable fictional inconsistencies in a claimed title?",
        "When should title forgery clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design verifiable fictional inconsistencies in a claimed title",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design verifiable fictional inconsistencies in a claimed title. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-outdated-title-clue",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Design verifiable fictional inconsistencies in a claimed title versus Link an obsolete form to what the speaker knows about time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shared-champion-title",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Design verifiable fictional inconsistencies in a claimed title versus Avoid assuming a title identifies a single person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-title-rejection-scene-exercise",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Design verifiable fictional inconsistencies in a claimed title versus Make a rejected title affect subsequent character treatment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design verifiable fictional inconsistencies in a claimed title",
        "outline": [
          "Explain the specific decision: Design verifiable fictional inconsistencies in a claimed title",
          "Define the applicable contract and limits for Title forgery clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design verifiable fictional inconsistencies in a claimed title; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design verifiable fictional inconsistencies in a claimed title",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:612",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-honor-name-pronunciation",
      "slug": "honor-name-pronunciation",
      "name": "Honor name pronunciation",
      "category": "titles",
      "urls": {
        "en": "/en/tools/honor-name-pronunciation/",
        "ja": "/ja/tools/honor-name-pronunciation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Provide approved spoken forms for formal announcements",
      "task": "Provide approved spoken forms for formal announcements",
      "searchIntent": {
        "primary": "Complete the task: Provide approved spoken forms for formal announcements",
        "queryHypothesis": "honor name pronunciation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide approved spoken forms for formal announcements?",
        "When should honor name pronunciation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide approved spoken forms for formal announcements",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide approved spoken forms for formal announcements. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Provide approved spoken forms for formal announcements versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Provide approved spoken forms for formal announcements versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-table-pronunciation-cards",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Provide approved spoken forms for formal announcements versus Provide player approved pronunciations for recurring NPCs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide approved spoken forms for formal announcements",
        "outline": [
          "Explain the specific decision: Provide approved spoken forms for formal announcements",
          "Define the applicable contract and limits for Honor name pronunciation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide approved spoken forms for formal announcements; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide approved spoken forms for formal announcements",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:613",
      "profileSource": "data/profiles.json#titles"
    },
    {
      "id": "nw-nonhuman-identity-translation",
      "slug": "nonhuman-identity-translation",
      "name": "Nonhuman identity translation",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/nonhuman-identity-translation/",
        "ja": "/ja/tools/nonhuman-identity-translation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Convert an authored sensory identity system into readable labels",
      "task": "Convert an authored sensory identity system into readable labels",
      "searchIntent": {
        "primary": "Complete the task: Convert an authored sensory identity system into readable labels",
        "queryHypothesis": "nonhuman identity translation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to convert an authored sensory identity system into readable labels?",
        "When should nonhuman identity translation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Convert an authored sensory identity system into readable labels",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Convert an authored sensory identity system into readable labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-sensory-name-translation",
          "score": 0.3063636363636364,
          "sharedProfile": false,
          "difference": "Convert an authored sensory identity system into readable labels versus Translate nonspoken identity cues into readable narrative labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonverbal-character-naming",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Convert an authored sensory identity system into readable labels versus Separate communicated identity from other characters' labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-confession-identity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Convert an authored sensory identity system into readable labels versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Convert an authored sensory identity system into readable labels",
        "outline": [
          "Explain the specific decision: Convert an authored sensory identity system into readable labels",
          "Define the applicable contract and limits for Nonhuman identity translation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Convert an authored sensory identity system into readable labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Convert an authored sensory identity system into readable labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:616",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-alien-personal-name-anatomy",
      "slug": "alien-personal-name-anatomy",
      "name": "Alien personal name anatomy",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/alien-personal-name-anatomy/",
        "ja": "/ja/tools/alien-personal-name-anatomy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Define meaningful components within an invented species grammar",
      "task": "Define meaningful components within an invented species grammar",
      "searchIntent": {
        "primary": "Complete the task: Define meaningful components within an invented species grammar",
        "queryHypothesis": "alien personal name anatomy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define meaningful components within an invented species grammar?",
        "When should alien personal name anatomy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define meaningful components within an invented species grammar",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define meaningful components within an invented species grammar. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define meaningful components within an invented species grammar versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-house-identity-system",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define meaningful components within an invented species grammar versus Define house membership and inherited personal components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define meaningful components within an invented species grammar versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define meaningful components within an invented species grammar",
        "outline": [
          "Explain the specific decision: Define meaningful components within an invented species grammar",
          "Define the applicable contract and limits for Alien personal name anatomy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define meaningful components within an invented species grammar; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define meaningful components within an invented species grammar",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:617",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-alien-human-nickname-negotiation",
      "slug": "alien-human-nickname-negotiation",
      "name": "Alien human nickname negotiation",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/alien-human-nickname-negotiation/",
        "ja": "/ja/tools/alien-human-nickname-negotiation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Track who chooses a translated name and who accepts it",
      "task": "Track who chooses a translated name and who accepts it",
      "searchIntent": {
        "primary": "Complete the task: Track who chooses a translated name and who accepts it",
        "queryHypothesis": "alien human nickname negotiation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track who chooses a translated name and who accepts it?",
        "When should alien human nickname negotiation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track who chooses a translated name and who accepts it",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track who chooses a translated name and who accepts it. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-villain-public-moniker",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track who chooses a translated name and who accepts it versus Track who coined the name and who rejects it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-private-nickname-clue",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Track who chooses a translated name and who accepts it versus Track the restricted group who could know the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Track who chooses a translated name and who accepts it versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track who chooses a translated name and who accepts it",
        "outline": [
          "Explain the specific decision: Track who chooses a translated name and who accepts it",
          "Define the applicable contract and limits for Alien human nickname negotiation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track who chooses a translated name and who accepts it; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track who chooses a translated name and who accepts it",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:618",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-hive-member-identity",
      "slug": "hive-member-identity",
      "name": "Hive member identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/hive-member-identity/",
        "ja": "/ja/tools/hive-member-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Distinguish collective reference from individual agents",
      "task": "Distinguish collective reference from individual agents",
      "searchIntent": {
        "primary": "Complete the task: Distinguish collective reference from individual agents",
        "queryHypothesis": "hive member identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish collective reference from individual agents?",
        "When should hive member identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish collective reference from individual agents",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish collective reference from individual agents. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-clan-branch-registry",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish collective reference from individual agents versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish collective reference from individual agents versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Distinguish collective reference from individual agents versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish collective reference from individual agents",
        "outline": [
          "Explain the specific decision: Distinguish collective reference from individual agents",
          "Define the applicable contract and limits for Hive member identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish collective reference from individual agents; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish collective reference from individual agents",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:619",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-collective-mind-speaker-labels",
      "slug": "collective-mind-speaker-labels",
      "name": "Collective mind speaker labels",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/collective-mind-speaker-labels/",
        "ja": "/ja/tools/collective-mind-speaker-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Track which voice acts for a distributed consciousness",
      "task": "Track which voice acts for a distributed consciousness",
      "searchIntent": {
        "primary": "Complete the task: Track which voice acts for a distributed consciousness",
        "queryHypothesis": "collective mind speaker labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track which voice acts for a distributed consciousness?",
        "When should collective mind speaker labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track which voice acts for a distributed consciousness",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track which voice acts for a distributed consciousness. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track which voice acts for a distributed consciousness versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cloned-mind-branch-names",
          "score": 0.09083333333333332,
          "sharedProfile": true,
          "difference": "Track which voice acts for a distributed consciousness versus Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-author-credit-governance",
          "score": 0.08611111111111111,
          "sharedProfile": false,
          "difference": "Track which voice acts for a distributed consciousness versus Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track which voice acts for a distributed consciousness",
        "outline": [
          "Explain the specific decision: Track which voice acts for a distributed consciousness",
          "Define the applicable contract and limits for Collective mind speaker labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track which voice acts for a distributed consciousness; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track which voice acts for a distributed consciousness",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:620",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-swarm-character-continuity",
      "slug": "swarm-character-continuity",
      "name": "Swarm character continuity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/swarm-character-continuity/",
        "ja": "/ja/tools/swarm-character-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Preserve identity when constituent members change",
      "task": "Preserve identity when constituent members change",
      "searchIntent": {
        "primary": "Complete the task: Preserve identity when constituent members change",
        "queryHypothesis": "swarm character continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve identity when constituent members change?",
        "When should swarm character continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve identity when constituent members change",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve identity when constituent members change. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-alias-state-machine",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Preserve identity when constituent members change versus Change visible identity only when narrative conditions allow it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-badge-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Preserve identity when constituent members change versus Match art badge text to timeline and identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-erasure-story-continuity",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Preserve identity when constituent members change versus Define how records and memories change after erasure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve identity when constituent members change",
        "outline": [
          "Explain the specific decision: Preserve identity when constituent members change",
          "Define the applicable contract and limits for Swarm character continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve identity when constituent members change; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve identity when constituent members change",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:621",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-shapeshifter-form-names",
      "slug": "shapeshifter-form-names",
      "name": "Shapeshifter form names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/shapeshifter-form-names/",
        "ja": "/ja/tools/shapeshifter-form-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Map physical forms to stable personal identity",
      "task": "Map physical forms to stable personal identity",
      "searchIntent": {
        "primary": "Complete the task: Map physical forms to stable personal identity",
        "queryHypothesis": "shapeshifter form names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map physical forms to stable personal identity?",
        "When should shapeshifter form names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map physical forms to stable personal identity",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map physical forms to stable personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-grandparent-nickname-dialogue",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Map physical forms to stable personal identity versus Map each child's term to a stable character identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-seasonal-name-change",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Map physical forms to stable personal identity versus Define repeatable seasonal forms with stable identity underneath; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Map physical forms to stable personal identity versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map physical forms to stable personal identity",
        "outline": [
          "Explain the specific decision: Map physical forms to stable personal identity",
          "Define the applicable contract and limits for Shapeshifter form names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map physical forms to stable personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map physical forms to stable personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:622",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-dragon-age-name-layers",
      "slug": "dragon-age-name-layers",
      "name": "Dragon age name layers",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/dragon-age-name-layers/",
        "ja": "/ja/tools/dragon-age-name-layers/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Add earned components at authored milestones without arbitrary syllable growth",
      "task": "Add earned components at authored milestones without arbitrary syllable growth",
      "searchIntent": {
        "primary": "Complete the task: Add earned components at authored milestones without arbitrary syllable growth",
        "queryHypothesis": "dragon age name layers",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to add earned components at authored milestones without arbitrary syllable growth?",
        "When should dragon age name layers be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Add earned components at authored milestones without arbitrary syllable growth",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Add earned components at authored milestones without arbitrary syllable growth. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Add earned components at authored milestones without arbitrary syllable growth versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-life-stage-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Add earned components at authored milestones without arbitrary syllable growth versus Transition name components at declared social milestones; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-age-cohort-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Add earned components at authored milestones without arbitrary syllable growth versus Match fictional birth timing to sourced cohort data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Add earned components at authored milestones without arbitrary syllable growth",
        "outline": [
          "Explain the specific decision: Add earned components at authored milestones without arbitrary syllable growth",
          "Define the applicable contract and limits for Dragon age name layers",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Add earned components at authored milestones without arbitrary syllable growth; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Add earned components at authored milestones without arbitrary syllable growth",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:623",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-spirit-place-bound-identity",
      "slug": "spirit-place-bound-identity",
      "name": "Spirit place bound identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/spirit-place-bound-identity/",
        "ja": "/ja/tools/spirit-place-bound-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Connect personal identity to a fictional place without merging records",
      "task": "Connect personal identity to a fictional place without merging records",
      "searchIntent": {
        "primary": "Complete the task: Connect personal identity to a fictional place without merging records",
        "queryHypothesis": "spirit place bound identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect personal identity to a fictional place without merging records?",
        "When should spirit place bound identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect personal identity to a fictional place without merging records",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect personal identity to a fictional place without merging records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-duplicate-identity-mystery",
          "score": 0.20833333333333334,
          "sharedProfile": false,
          "difference": "Connect personal identity to a fictional place without merging records versus Track two records that may refer to one person without prematurely merging; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-immortal-historical-aliases",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Connect personal identity to a fictional place without merging records versus Maintain a dated identity chain without fabricated historical records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Connect personal identity to a fictional place without merging records versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect personal identity to a fictional place without merging records",
        "outline": [
          "Explain the specific decision: Connect personal identity to a fictional place without merging records",
          "Define the applicable contract and limits for Spirit place bound identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect personal identity to a fictional place without merging records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect personal identity to a fictional place without merging records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:624",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-ghost-former-living-name",
      "slug": "ghost-former-living-name",
      "name": "Ghost former living name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/ghost-former-living-name/",
        "ja": "/ja/tools/ghost-former-living-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Separate remembered, forgotten and self chosen identities",
      "task": "Separate remembered, forgotten and self chosen identities",
      "searchIntent": {
        "primary": "Complete the task: Separate remembered, forgotten and self chosen identities",
        "queryHypothesis": "ghost former living name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate remembered, forgotten and self chosen identities?",
        "When should ghost former living name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate remembered, forgotten and self chosen identities",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate remembered, forgotten and self chosen identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Separate remembered, forgotten and self chosen identities versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-ensemble-naming",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate remembered, forgotten and self chosen identities versus Separate institutional labels from self and peer chosen names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate remembered, forgotten and self chosen identities versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate remembered, forgotten and self chosen identities",
        "outline": [
          "Explain the specific decision: Separate remembered, forgotten and self chosen identities",
          "Define the applicable contract and limits for Ghost former living name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate remembered, forgotten and self chosen identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate remembered, forgotten and self chosen identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:625",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-undead-renaming-decision",
      "slug": "undead-renaming-decision",
      "name": "Undead renaming decision",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/undead-renaming-decision/",
        "ja": "/ja/tools/undead-renaming-decision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Tie a name change to character agency rather than species stereotype",
      "task": "Tie a name change to character agency rather than species stereotype",
      "searchIntent": {
        "primary": "Complete the task: Tie a name change to character agency rather than species stereotype",
        "queryHypothesis": "undead renaming decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie a name change to character agency rather than species stereotype?",
        "When should undead renaming decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie a name change to character agency rather than species stereotype",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie a name change to character agency rather than species stereotype. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nonhuman-culture-naming-contrast",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Tie a name change to character agency rather than species stereotype versus Distinguish cultures within a species rather than one species one style; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-renaming-transforms-reality",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Tie a name change to character agency rather than species stereotype versus Test scope, exceptions and competing claims of a name change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Tie a name change to character agency rather than species stereotype versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie a name change to character agency rather than species stereotype",
        "outline": [
          "Explain the specific decision: Tie a name change to character agency rather than species stereotype",
          "Define the applicable contract and limits for Undead renaming decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie a name change to character agency rather than species stereotype; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie a name change to character agency rather than species stereotype",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:626",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-immortal-reputation-names",
      "slug": "immortal-reputation-names",
      "name": "Immortal reputation names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/immortal-reputation-names/",
        "ja": "/ja/tools/immortal-reputation-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Track names across communities and centuries",
      "task": "Track names across communities and centuries",
      "searchIntent": {
        "primary": "Complete the task: Track names across communities and centuries",
        "queryHypothesis": "immortal reputation names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track names across communities and centuries?",
        "When should immortal reputation names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track names across communities and centuries",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track names across communities and centuries. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-changes-surname-after-exile",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Track names across communities and centuries versus Preserve continuity across home and adopted communities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-school-uniform-name-patch",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track names across communities and centuries versus Track prop name changes across character transfers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track names across communities and centuries versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track names across communities and centuries",
        "outline": [
          "Explain the specific decision: Track names across communities and centuries",
          "Define the applicable contract and limits for Immortal reputation names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track names across communities and centuries; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track names across communities and centuries",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:627",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-deity-mortal-avatar-identity",
      "slug": "deity-mortal-avatar-identity",
      "name": "Deity mortal avatar identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/deity-mortal-avatar-identity/",
        "ja": "/ja/tools/deity-mortal-avatar-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Keep an avatar's local name distinct from a divine title",
      "task": "Keep an avatar's local name distinct from a divine title",
      "searchIntent": {
        "primary": "Complete the task: Keep an avatar's local name distinct from a divine title",
        "queryHypothesis": "deity mortal avatar identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep an avatar's local name distinct from a divine title?",
        "When should deity mortal avatar identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep an avatar's local name distinct from a divine title",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep an avatar's local name distinct from a divine title. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-confession-identity",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Keep an avatar's local name distinct from a divine title versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Keep an avatar's local name distinct from a divine title versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-royal-identity",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Keep an avatar's local name distinct from a divine title versus Manage birth title, assumed name and recognition triggers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep an avatar's local name distinct from a divine title",
        "outline": [
          "Explain the specific decision: Keep an avatar's local name distinct from a divine title",
          "Define the applicable contract and limits for Deity mortal avatar identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep an avatar's local name distinct from a divine title; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep an avatar's local name distinct from a divine title",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:628",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-familiar-chosen-name",
      "slug": "familiar-chosen-name",
      "name": "Familiar chosen name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/familiar-chosen-name/",
        "ja": "/ja/tools/familiar-chosen-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Distinguish the creature's preference from a name imposed by a summoner",
      "task": "Distinguish the creature's preference from a name imposed by a summoner",
      "searchIntent": {
        "primary": "Complete the task: Distinguish the creature's preference from a name imposed by a summoner",
        "queryHypothesis": "familiar chosen name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish the creature's preference from a name imposed by a summoner?",
        "When should familiar chosen name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish the creature's preference from a name imposed by a summoner",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish the creature's preference from a name imposed by a summoner. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish the creature's preference from a name imposed by a summoner versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hostile-nickname-perspective",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Distinguish the creature's preference from a name imposed by a summoner versus Distinguish a character's insult from narrator endorsement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-naming-law-conflict",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Distinguish the creature's preference from a name imposed by a summoner versus Compare individual preference with an invented institution's demands; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish the creature's preference from a name imposed by a summoner",
        "outline": [
          "Explain the specific decision: Distinguish the creature's preference from a name imposed by a summoner",
          "Define the applicable contract and limits for Familiar chosen name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish the creature's preference from a name imposed by a summoner; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish the creature's preference from a name imposed by a summoner",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:629",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-sentient-weapon-personal-identity",
      "slug": "sentient-weapon-personal-identity",
      "name": "Sentient weapon personal identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/sentient-weapon-personal-identity/",
        "ja": "/ja/tools/sentient-weapon-personal-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Separate artifact model, owner nickname and self name",
      "task": "Separate artifact model, owner nickname and self name",
      "searchIntent": {
        "primary": "Complete the task: Separate artifact model, owner nickname and self name",
        "queryHypothesis": "sentient weapon personal identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate artifact model, owner nickname and self name?",
        "When should sentient weapon personal identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate artifact model, owner nickname and self name",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate artifact model, owner nickname and self name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Separate artifact model, owner nickname and self name versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Separate artifact model, owner nickname and self name versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-possessed-body-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Separate artifact model, owner nickname and self name versus Distinguish body owner and inhabiting voice in references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate artifact model, owner nickname and self name",
        "outline": [
          "Explain the specific decision: Separate artifact model, owner nickname and self name",
          "Define the applicable contract and limits for Sentient weapon personal identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate artifact model, owner nickname and self name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate artifact model, owner nickname and self name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:630",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-sentient-building-voice-name",
      "slug": "sentient-building-voice-name",
      "name": "Sentient building voice name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/sentient-building-voice-name/",
        "ja": "/ja/tools/sentient-building-voice-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Track identity across renovation, ownership and memory changes",
      "task": "Track identity across renovation, ownership and memory changes",
      "searchIntent": {
        "primary": "Complete the task: Track identity across renovation, ownership and memory changes",
        "queryHypothesis": "sentient building voice name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track identity across renovation, ownership and memory changes?",
        "When should sentient building voice name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track identity across renovation, ownership and memory changes",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track identity across renovation, ownership and memory changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-school-uniform-name-patch",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track identity across renovation, ownership and memory changes versus Track prop name changes across character transfers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-god-loses-worship-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track identity across renovation, ownership and memory changes versus Track changes in reference, power and remembered identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track identity across renovation, ownership and memory changes versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track identity across renovation, ownership and memory changes",
        "outline": [
          "Explain the specific decision: Track identity across renovation, ownership and memory changes",
          "Define the applicable contract and limits for Sentient building voice name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track identity across renovation, ownership and memory changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track identity across renovation, ownership and memory changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:631",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-sentient-ship-character-name",
      "slug": "sentient-ship-character-name",
      "name": "Sentient ship character name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/sentient-ship-character-name/",
        "ja": "/ja/tools/sentient-ship-character-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Separate vessel registry from the onboard intelligence's chosen identity",
      "task": "Separate vessel registry from the onboard intelligence's chosen identity",
      "searchIntent": {
        "primary": "Complete the task: Separate vessel registry from the onboard intelligence's chosen identity",
        "queryHypothesis": "sentient ship character name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate vessel registry from the onboard intelligence's chosen identity?",
        "When should sentient ship character name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate vessel registry from the onboard intelligence's chosen identity",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate vessel registry from the onboard intelligence's chosen identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Separate vessel registry from the onboard intelligence's chosen identity versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate vessel registry from the onboard intelligence's chosen identity versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate vessel registry from the onboard intelligence's chosen identity versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate vessel registry from the onboard intelligence's chosen identity",
        "outline": [
          "Explain the specific decision: Separate vessel registry from the onboard intelligence's chosen identity",
          "Define the applicable contract and limits for Sentient ship character name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate vessel registry from the onboard intelligence's chosen identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate vessel registry from the onboard intelligence's chosen identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:632",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-artificial-intelligence-instance-names",
      "slug": "artificial-intelligence-instance-names",
      "name": "Artificial intelligence instance names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/artificial-intelligence-instance-names/",
        "ja": "/ja/tools/artificial-intelligence-instance-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Distinguish model, instance and self chosen name",
      "task": "Distinguish model, instance and self chosen name",
      "searchIntent": {
        "primary": "Complete the task: Distinguish model, instance and self chosen name",
        "queryHypothesis": "artificial intelligence instance names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish model, instance and self chosen name?",
        "When should artificial intelligence instance names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish model, instance and self chosen name",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish model, instance and self chosen name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish model, instance and self chosen name versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-colonial-registry-renaming-fiction",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish model, instance and self chosen name versus Distinguish coercive records from self identified names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ghost-former-living-name",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Distinguish model, instance and self chosen name versus Separate remembered, forgotten and self chosen identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish model, instance and self chosen name",
        "outline": [
          "Explain the specific decision: Distinguish model, instance and self chosen name",
          "Define the applicable contract and limits for Artificial intelligence instance names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish model, instance and self chosen name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish model, instance and self chosen name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:633",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-robot-serial-to-personal-name",
      "slug": "robot-serial-to-personal-name",
      "name": "Robot serial to personal name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/robot-serial-to-personal-name/",
        "ja": "/ja/tools/robot-serial-to-personal-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Science-fiction, comic and game creators handling artificial-person identities and technical props.",
      "scenario": "A repair order identifies a production batch while dialogue uses an individual’s chosen name; the author needs to know which reference actually identifies a unit.",
      "task": "Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual.",
      "searchIntent": {
        "primary": "Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual.",
        "queryHypothesis": "robot serial to personal name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Why can a batch tag point to several people while a full serial selects one unit?",
        "Can two artificial people keep the same chosen name without merging their technical records?"
      ],
      "inputs": [
        {
          "key": "units",
          "use": "Stable individual IDs, unchanged technical namespace/serial pairs and explicit batch membership."
        },
        {
          "key": "namespaces",
          "use": "Author-defined literal serial prefix and permitted unit-code alphabet/length; no real manufacturing standard is implied."
        },
        {
          "key": "chosenNames",
          "use": "Explicit individual choice and effective intervals, kept separate from production designation."
        },
        {
          "key": "references",
          "use": "Scene/asset records declaring technical serial, batch or personal display reference and its intended individual if known."
        },
        {
          "key": "chapter",
          "use": "Select the scene point for a choice interval and reference audit."
        }
      ],
      "rules": [
        "Technical namespace plus serial identifies at most one declared unit; a duplicated pair is a registry conflict.",
        "A shared batch is not an individual identifier and may resolve to multiple units.",
        "Validate supplied serials against their declared literal grammar, without guessing identity from spelling.",
        "Personal display strings never merge individual IDs, including identical chosen names.",
        "Choice intervals for one unit cannot overlap; absent choice remains unknown rather than generated.",
        "Retain original technical strings and authored choice evidence; a label does not prove a person consented.",
        "Resolve a reference by its declared kind; an unknown or ambiguous reference remains unresolved."
      ],
      "requiredData": [
        {
          "description": "Original finite artificial-unit fixtures and authored serial grammars",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied choice records and scene/asset references; no external identity or manufacturing database",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Technical namespace plus serial identifies at most one declared unit; a duplicated pair is a registry conflict.",
        "A shared batch is not an individual identifier and may resolve to multiple units.",
        "Validate supplied serials against their declared literal grammar, without guessing identity from spelling.",
        "Personal display strings never merge individual IDs, including identical chosen names.",
        "Choice intervals for one unit cannot overlap; absent choice remains unknown rather than generated.",
        "Retain original technical strings and authored choice evidence; a label does not prove a person consented.",
        "Resolve a reference by its declared kind; an unknown or ambiguous reference remains unresolved."
      ],
      "outputs": [
        "Per-unit technical/choice identity sheet",
        "Serial validity and duplicate-reference diagnostics",
        "Batch-reference candidate IDs and intended-target mismatch report",
        "Private production audit preserving exact originals"
      ],
      "capabilities": [
        "Explain a batch tag that cannot select one individual even though it looks like a full name.",
        "Keep two people with identical chosen display names distinct while resolving a technical prop to the right individual."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "This task validates a technical identity registry and resolves machine references, rather than conceal a true name or choose a form of address. A batch-only reference can identify several units even when every chosen name is distinct.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "rules",
          "outputs",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "true-name-alias-bridge",
          "difference": "The alias tool evaluates observer knowledge around personal reference forms. This workbench validates scoped technical identifiers, immutable unit links, batch-only ambiguity and chosen-name intervals without using a display name as a database key."
        }
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-source-contradiction",
          "score": 0.12187500000000001,
          "sharedProfile": false,
          "difference": "Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual. versus Compare conflicting references without silently selecting one; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual. versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-serial-author-handle-migration",
          "score": 0.1061111111111111,
          "sharedProfile": false,
          "difference": "Reconcile technical unit references with chosen personal names without mistaking a shared batch or display string for one individual. versus Reconcile old community handles with a book byline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A name can express agency without becoming the key that technical records use.",
        "outline": [
          "Read a repair tag as a reference, not a person",
          "Choose a namespace before checking serials",
          "Original scene: two units ask for the same name",
          "Trace the wrong spare-part order",
          "Preserve unknown choice and unresolved batch references"
        ],
        "story": "Two artificial workers independently choose the same name. A mechanic insists one must change it after a batch-only repair slip reaches the wrong worker. The author fixes the slip’s technical specificity while allowing both choices to remain.",
        "storyAnalysis": "Renaming one worker can hide a defective reference system. Distinguish the social consequence of a chosen name from the precision of a production tag.",
        "evidence": "Original registry and repair-slip fixtures; no real manufacturer, conscious-machine claim or consent evidence fabricated.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/unitNames.md",
        "localizedBodies": {
          "en": "content/en/unitNames.md",
          "ja": "content/ja/unitNames.md"
        }
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A duplicated namespace/serial pair conflicts; the same serial in different declared namespaces stays distinct.",
        "Changing a batch-only reference to a full serial reduces the candidate set according to actual data.",
        "An undeclared or invalid serial is not repaired by a matching chosen name.",
        "Identical personal displays never merge records.",
        "A future choice does not appear in an earlier scene; absent choice is explicitly unknown.",
        "Export preserves both technical originals and authored choice scope without a consent or legal-rights certification."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:634",
      "profileSource": "data/profiles.json#nonhuman",
      "specBatch": "batch-03",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Dedicated state, scoped references and failure handling; no production time or cost estimate fabricated."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-artificial-person-chosen-identity",
          "input": "Authored namespaces with literal prefix/alphabet/code-point bounds; stable unit IDs and exact serial/batch data; scene-scoped name-choice claims and references.",
          "rule": "Technical pairs are unique only within their declared namespace; batch membership and matching personal names do not merge individuals. Third-party claims do not become established self-choice; intended target is compared, never used to invent a match.",
          "output": "Unit technical/choice sheet, ambiguous/unknown/invalid/intended-mismatch reference candidates, shared displays with separate IDs and private author audit.",
          "acceptance": "Duplicate technical pair conflicts while cross-namespace same serial stays distinct; batch-only slip has two candidates until corrected; both Robin identities remain and can be separately saved; a future or third-party label is not shown as an earlier self-choice.",
          "evidence": [
            "UNIT-01",
            "UNIT-02",
            "UNIT-03",
            "UNIT-04",
            "UNIT-05",
            "UNIT-07",
            "FAVORITE-01",
            "reports/unit-name-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-robot-production-batch-identity",
          "input": "Authored namespaces with literal prefix/alphabet/code-point bounds; stable unit IDs and exact serial/batch data; scene-scoped name-choice claims and references.",
          "rule": "Technical pairs are unique only within their declared namespace; batch membership and matching personal names do not merge individuals. Third-party claims do not become established self-choice; intended target is compared, never used to invent a match.",
          "output": "Unit technical/choice sheet, ambiguous/unknown/invalid/intended-mismatch reference candidates, shared displays with separate IDs and private author audit.",
          "acceptance": "Duplicate technical pair conflicts while cross-namespace same serial stays distinct; batch-only slip has two candidates until corrected; both Robin identities remain and can be separately saved; a future or third-party label is not shown as an earlier self-choice.",
          "evidence": [
            "UNIT-01",
            "UNIT-02",
            "UNIT-03",
            "UNIT-04",
            "UNIT-05",
            "UNIT-07",
            "FAVORITE-01",
            "reports/unit-name-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "unitNames",
        "engineFiles": [
          "web/unit-name-registry.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/unit-name.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "namespaces",
          "label": [
            "Authored serial namespaces · JSON",
            "作者の番号名前空間・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"north\",\n    \"prefix\": \"N-\",\n    \"alphabet\": \"0123456789\",\n    \"minLength\": 3,\n    \"maxLength\": 3\n  },\n  {\n    \"id\": \"south\",\n    \"prefix\": \"N-\",\n    \"alphabet\": \"0123456789\",\n    \"minLength\": 3,\n    \"maxLength\": 3\n  }\n]",
          "help": [
            "Each namespace: id, literal prefix, unique suffix alphabet, minLength and maxLength (1–40 code points). No real manufacturing standard is inferred.",
            "各名前空間はid、固定のprefix、重複しないalphabet、minLengthとmaxLength（1〜40コードポイント）。実在の製造規格は推定しません。"
          ]
        },
        {
          "key": "units",
          "label": [
            "Stable individuals · JSON",
            "安定した個体ID・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"u1\",\n    \"namespace\": \"north\",\n    \"serial\": \"N-041\",\n    \"batch\": \"batch-7\"\n  },\n  {\n    \"id\": \"u2\",\n    \"namespace\": \"north\",\n    \"serial\": \"N-042\",\n    \"batch\": \"batch-7\"\n  },\n  {\n    \"id\": \"u3\",\n    \"namespace\": \"south\",\n    \"serial\": \"N-041\",\n    \"batch\": null\n  }\n]",
          "help": [
            "Each record: stable id, namespace, exact serial and batch string or null for unknown. Different personal displays never change these keys.",
            "各行は安定したid、namespace、正確なserial、batchの文字列または不明のnull。個人名が変わってもキーは変えません。"
          ]
        },
        {
          "key": "chosenNames",
          "label": [
            "Choice records · JSON",
            "名前の選択記録・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"c1\",\n    \"unit\": \"u1\",\n    \"from\": 2,\n    \"to\": null,\n    \"name\": \"Robin\",\n    \"claim\": \"self-reported\",\n    \"evidence\": \"Original fictional scene: u1 states this choice.\"\n  },\n  {\n    \"id\": \"c2\",\n    \"unit\": \"u2\",\n    \"from\": 3,\n    \"to\": null,\n    \"name\": \"Robin\",\n    \"claim\": \"self-reported\",\n    \"evidence\": \"Original fictional scene: u2 independently states the same choice.\"\n  },\n  {\n    \"id\": \"c3\",\n    \"unit\": \"u3\",\n    \"from\": 5,\n    \"to\": null,\n    \"name\": \"Pella\",\n    \"claim\": \"third-party\",\n    \"evidence\": \"A supervisor suggests this label; no personal choice is established.\"\n  }\n]",
          "help": [
            "id, unit, inclusive from/to (null for open), name, self-reported/third-party/unknown claim and evidence note. These are unverified authored claims.",
            "id、unit、両端を含むfrom/to（終わりなしはnull）、name、self-reported/third-party/unknownのclaim、evidenceメモ。未検証の作者の主張です。"
          ]
        },
        {
          "key": "references",
          "label": [
            "Scene and prop references · JSON",
            "場面と小道具の参照・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"repair\",\n    \"kind\": \"batch\",\n    \"namespace\": \"north\",\n    \"value\": \"batch-7\",\n    \"intended\": \"u2\",\n    \"asset\": \"Repair slip uses only the shared batch tag.\"\n  },\n  {\n    \"id\": \"locker\",\n    \"kind\": \"serial\",\n    \"namespace\": \"north\",\n    \"value\": \"N-042\",\n    \"intended\": \"u2\",\n    \"asset\": \"Individual locker label.\"\n  },\n  {\n    \"id\": \"call\",\n    \"kind\": \"chosen-name\",\n    \"namespace\": null,\n    \"value\": \"Robin\",\n    \"intended\": null,\n    \"asset\": \"A spoken call without another distinguishing cue.\"\n  }\n]",
          "help": [
            "id, serial/batch/chosen-name kind, namespace or null, value, intended unit or null, asset note. Intended identity never supplies a missing match.",
            "id、serial/batch/chosen-nameのkind、namespaceまたはnull、value、intended個体またはnull、assetメモ。意図する相手から一致を作りません。"
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Scene chapter",
            "場面の章"
          ],
          "type": "number",
          "default": 4,
          "help": null
        },
        {
          "key": "displayComparison",
          "label": [
            "Chosen-display comparison",
            "選択名の比較"
          ],
          "type": "select",
          "default": "exact",
          "help": null,
          "options": [
            [
              "exact",
              [
                "Exact strings",
                "文字列の完全一致"
              ]
            ],
            [
              "nfc",
              [
                "NFC for comparison only",
                "比較時のみNFC"
              ]
            ]
          ]
        }
      ]
    },
    {
      "id": "nw-android-cover-identity",
      "slug": "android-cover-identity",
      "name": "Android cover identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/android-cover-identity/",
        "ja": "/ja/tools/android-cover-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Keep social display separate from production metadata",
      "task": "Keep social display separate from production metadata",
      "searchIntent": {
        "primary": "Complete the task: Keep social display separate from production metadata",
        "queryHypothesis": "android cover identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep social display separate from production metadata?",
        "When should android cover identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep social display separate from production metadata",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep social display separate from production metadata. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cover-identity-dossier",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Keep social display separate from production metadata versus Keep an alias consistent with a fictional biography and document set; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-audio-subtitle-identity",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Keep social display separate from production metadata versus Align spoken names with subtitle display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-character-id-export",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep social display separate from production metadata versus Produce stable keys and display strings for production pipelines; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep social display separate from production metadata",
        "outline": [
          "Explain the specific decision: Keep social display separate from production metadata",
          "Define the applicable contract and limits for Android cover identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep social display separate from production metadata; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep social display separate from production metadata",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:635",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-cloned-mind-branch-names",
      "slug": "cloned-mind-branch-names",
      "name": "Cloned mind branch names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/cloned-mind-branch-names/",
        "ja": "/ja/tools/cloned-mind-branch-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Speculative-fiction and game writers depicting copied or forked minds.",
      "scenario": "A message addressed to one continuous identity predates a fork; later scenes must distinguish shared provenance from the recipient of a new instruction.",
      "task": "Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant.",
      "searchIntent": {
        "primary": "Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant.",
        "queryHypothesis": "cloned mind branch names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Who receives a reused pre-fork message after one identity branches into two?",
        "Can I resolve one new request without rewriting earlier signatures?"
      ],
      "inputs": [
        {
          "key": "segments",
          "use": "Stable identity segment IDs, chosen display and birth/end points in the authored timeline."
        },
        {
          "key": "forks",
          "use": "Parent segment, split chapter and two or more explicitly created child IDs."
        },
        {
          "key": "references",
          "use": "Message/asset IDs, chapter, recorded target segment or provenance label and later reuse point."
        },
        {
          "key": "resolutions",
          "use": "Optional author-approved branch routing for a specific reused reference, with reason."
        }
      ],
      "rules": [
        "Reject fork cycles, duplicate child creation, unknown parents and overlapping life of a parent segment with its post-fork children under the declared exclusive-segment model.",
        "A shared display or origin is not a unique current target.",
        "Pre-fork records stay linked to the actual pre-fork segment, not rewritten to one descendant.",
        "At reuse, enumerate living descendants when a provenance-only reference cannot select one.",
        "A resolution applies to one reference and branch; a note is not universal inheritance of rights or memories.",
        "Keep a valid historical target separate from an ambiguous current recipient.",
        "Do not infer philosophical personhood, real consciousness or legal identity."
      ],
      "requiredData": [
        {
          "description": "Authored fork graph and exact reference ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Original finite branch/reuse fixtures; no neuroscientific or legal identity claims",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Reject fork cycles, duplicate child creation, unknown parents and overlapping life of a parent segment with its post-fork children under the declared exclusive-segment model.",
        "A shared display or origin is not a unique current target.",
        "Pre-fork records stay linked to the actual pre-fork segment, not rewritten to one descendant.",
        "At reuse, enumerate living descendants when a provenance-only reference cannot select one.",
        "A resolution applies to one reference and branch; a note is not universal inheritance of rights or memories.",
        "Keep a valid historical target separate from an ambiguous current recipient.",
        "Do not infer philosophical personhood, real consciousness or legal identity."
      ],
      "outputs": [
        "Segment lifetime and fork validation",
        "Historical target versus current routing candidate set",
        "Unresolved reuse references and scoped author resolutions",
        "Private continuity handoff"
      ],
      "capabilities": [
        "Expose a command that was unambiguous before a fork but ambiguous when reused afterward.",
        "Resolve one later reference without rewriting the provenance of all earlier documents."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is resolving identity-reference scope through split events. Shared ancestry is insufficient: a pre-fork reference can be valid for the then-existing identity but ambiguous if later reused as a command to one branch.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "family-name-planner",
          "difference": "A family graph propagates naming structure among coexisting people. This model closes a parent identity segment at a fork, creates explicit branch IDs and reports unresolved routing of references that do not select a post-fork segment."
        }
      },
      "nearestTools": [
        {
          "id": "nw-clan-branch-registry",
          "score": 0.10421052631578948,
          "sharedProfile": false,
          "difference": "Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant. versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.10263157894736842,
          "sharedProfile": true,
          "difference": "Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant. versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-branch-differentiation",
          "score": 0.09954545454545455,
          "sharedProfile": false,
          "difference": "Audit which identity a reference can target before and after an authored mind fork, without assigning pre-fork records to an arbitrary descendant. versus Mark branches without treating all cousins as interchangeable; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "Shared origin is a relationship, not an instruction about which descendant a later sentence addresses.",
        "outline": [
          "Keep the old signature at its own date",
          "Fork events create new routing questions",
          "Original scene: a promise delivered to two doorways",
          "Resolve a new request without assigning the old life",
          "The limits of a segment model"
        ],
        "story": "A copied mind’s two descendants receive a reused delivery request bearing the original signature. Both recognize its history, but the present request needs one explicit addressee. The writer identifies the new recipient without declaring that the other branch never shared the past.",
        "storyAnalysis": "Giving the branches very different names may aid reading while leaving the old reference ambiguous. Solve routing and reader distinction separately.",
        "evidence": "Original speculative graph and messages; no external claims about minds or identity.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/forkNames.md",
        "localizedBodies": {
          "en": "content/en/forkNames.md",
          "ja": "content/ja/forkNames.md"
        }
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Two children sharing one display remain two IDs.",
        "A pre-fork reference retains its original segment after branching.",
        "A provenance-only reuse enumerates both living branches instead of picking the first.",
        "A scoped branch resolution affects only its linked message.",
        "Cycles and duplicate creation fail without partial graph acceptance.",
        "Export distinguishes historical validity, current resolution and author-authored assumptions."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:636",
      "profileSource": "data/profiles.json#nonhuman",
      "specBatch": "batch-03",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Dedicated state, scoped references and failure handling; no production time or cost estimate fabricated."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "forkNames",
        "engineFiles": [
          "web/fork-reference-audit.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/fork-reference.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "segments",
          "label": [
            "Identity segments · JSON",
            "身元の区間・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"root\",\n    \"name\": \"Ari\",\n    \"start\": 0,\n    \"end\": 4\n  },\n  {\n    \"id\": \"east\",\n    \"name\": \"Ari\",\n    \"start\": 4,\n    \"end\": null\n  },\n  {\n    \"id\": \"west\",\n    \"name\": \"Ari\",\n    \"start\": 4,\n    \"end\": null\n  }\n]",
          "help": [
            "Half-open [start,end): the end chapter belongs to the new branch. Null end is open. Names do not identify a unique branch.",
            "半開区間[start,end)で、終わりの章は新しい分岐側に属します。nullは終わりなし。名前だけで分岐を特定しません。"
          ]
        },
        {
          "key": "forks",
          "label": [
            "Fork events · JSON",
            "分岐の出来事・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"f1\",\n    \"parent\": \"root\",\n    \"at\": 4,\n    \"children\": [\n      \"east\",\n      \"west\"\n    ]\n  }\n]",
          "help": [
            "Each fork: id, parent, at and 2–6 children. The parent ends and the children begin exactly at at. Cycles and multiple creation are rejected.",
            "各分岐はid、parent、at、2〜6件のchildren。atで親が終わり、子が開始します。循環と複数の作成元は拒否します。"
          ]
        },
        {
          "key": "references",
          "label": [
            "Historical and reused references · JSON",
            "過去と再使用の参照・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"old-letter\",\n    \"createdAt\": 2,\n    \"target\": \"root\",\n    \"kind\": \"segment\",\n    \"reuseAt\": null,\n    \"note\": \"Keep the original signature with its original addressee.\"\n  },\n  {\n    \"id\": \"new-request\",\n    \"createdAt\": 3,\n    \"target\": \"root\",\n    \"kind\": \"segment\",\n    \"reuseAt\": 6,\n    \"note\": \"A request reused after the fork still names the old segment.\"\n  },\n  {\n    \"id\": \"origin-label\",\n    \"createdAt\": 5,\n    \"target\": \"root\",\n    \"kind\": \"origin\",\n    \"reuseAt\": 6,\n    \"note\": \"An origin label describes provenance, not a current recipient.\"\n  }\n]",
          "help": [
            "Each reference: id, createdAt, target, segment/origin kind, reuseAt or null, note. A provenance label is not automatically a current addressee.",
            "各参照はid、createdAt、target、segment/originのkind、reuseAtまたはnull、note。出所の表示を現在の個人宛先に自動では変えません。"
          ],
          "maxLength": 180000
        },
        {
          "key": "resolutions",
          "label": [
            "Explicit reference-specific routing · JSON",
            "参照ごとの明示した宛先・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Each record: referenceId, segmentId, reason. A decision affects one reused reference and must select an active descendant.",
            "各行はreferenceId、segmentId、reason。一つの再使用参照にだけ適用し、活動中の後継区間を選びます。"
          ]
        }
      ]
    },
    {
      "id": "nw-uploaded-person-identity",
      "slug": "uploaded-person-identity",
      "name": "Uploaded person identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/uploaded-person-identity/",
        "ja": "/ja/tools/uploaded-person-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Model continuity claims as story positions rather than scientific fact",
      "task": "Model continuity claims as story positions rather than scientific fact",
      "searchIntent": {
        "primary": "Complete the task: Model continuity claims as story positions rather than scientific fact",
        "queryHypothesis": "uploaded person identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model continuity claims as story positions rather than scientific fact?",
        "When should uploaded person identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model continuity claims as story positions rather than scientific fact",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model continuity claims as story positions rather than scientific fact. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-plant-person-seasonal-identity",
          "score": 0.18642857142857142,
          "sharedProfile": true,
          "difference": "Model continuity claims as story positions rather than scientific fact versus Link seasonal forms to continuity in an invented biology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-assassin-order-fictional-identities",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Model continuity claims as story positions rather than scientific fact versus Focus on narrative continuity and knowledge rather than real evasion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-noble-title-system",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Model continuity claims as story positions rather than scientific fact versus Define ranked titles using authored rules rather than historical claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model continuity claims as story positions rather than scientific fact",
        "outline": [
          "Explain the specific decision: Model continuity claims as story positions rather than scientific fact",
          "Define the applicable contract and limits for Uploaded person identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model continuity claims as story positions rather than scientific fact; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model continuity claims as story positions rather than scientific fact",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:637",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-digital-ghost-account-identity",
      "slug": "digital-ghost-account-identity",
      "name": "Digital ghost account identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/digital-ghost-account-identity/",
        "ja": "/ja/tools/digital-ghost-account-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Separate a deceased person's account from a simulated character",
      "task": "Separate a deceased person's account from a simulated character",
      "searchIntent": {
        "primary": "Complete the task: Separate a deceased person's account from a simulated character",
        "queryHypothesis": "digital ghost account identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a deceased person's account from a simulated character?",
        "When should digital ghost account identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a deceased person's account from a simulated character",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a deceased person's account from a simulated character. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-real-person-name-boundary",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate a deceased person's account from a simulated character versus Separate a fictional character from a real person's biography; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-deity-mortal-avatar-identity",
          "score": 0.11499999999999999,
          "sharedProfile": true,
          "difference": "Separate a deceased person's account from a simulated character versus Keep an avatar's local name distinct from a divine title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-kana-only-character-identity",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Separate a deceased person's account from a simulated character versus Evaluate a supplied kana name in the story's reference system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a deceased person's account from a simulated character",
        "outline": [
          "Explain the specific decision: Separate a deceased person's account from a simulated character",
          "Define the applicable contract and limits for Digital ghost account identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a deceased person's account from a simulated character; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a deceased person's account from a simulated character",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:638",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-program-character-namespace",
      "slug": "program-character-namespace",
      "name": "Program character namespace",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/program-character-namespace/",
        "ja": "/ja/tools/program-character-namespace/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Avoid collisions between display names and technical keys",
      "task": "Avoid collisions between display names and technical keys",
      "searchIntent": {
        "primary": "Complete the task: Avoid collisions between display names and technical keys",
        "queryHypothesis": "program character namespace",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid collisions between display names and technical keys?",
        "When should program character namespace be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid collisions between display names and technical keys",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid collisions between display names and technical keys. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Avoid collisions between display names and technical keys versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-cast-localization-keys",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid collisions between display names and technical keys versus Export stable keys independently of translated display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-engine-name-key-migration",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid collisions between display names and technical keys versus Keep resource keys stable during display name revisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid collisions between display names and technical keys",
        "outline": [
          "Explain the specific decision: Avoid collisions between display names and technical keys",
          "Define the applicable contract and limits for Program character namespace",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid collisions between display names and technical keys; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid collisions between display names and technical keys",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:639",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-time-loop-remembered-names",
      "slug": "time-loop-remembered-names",
      "name": "Time loop remembered names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/time-loop-remembered-names/",
        "ja": "/ja/tools/time-loop-remembered-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Time-loop, speculative-fiction, comic and game writers tracking what a speaker can recognize after an authored reset.",
      "scenario": "An apprentice retains a relation between two names but loses the words themselves. Another observer keeps only a call sign. A sibling repeat retains all memories. Later relearning must not retroactively authorize an earlier naming use.",
      "task": "Audit explicit name and connection memory facts through reset-specific retention, loss and relearning, keeping parent sources, sibling branches and observer states separate.",
      "searchIntent": {
        "primary": "Track which names and identity connections an observer remembers after a time-loop reset.",
        "queryHypothesis": "time loop remembered names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can an observer remember an alias connection but lose the name words?",
        "Does learning a name later repair earlier dialogue?",
        "How can two sibling repeats remain consistent without sharing memories?"
      ],
      "inputs": [
        {
          "key": "people",
          "use": "Private author identity labels; never auto-learned by an observer."
        },
        {
          "key": "forms",
          "use": "Exact stable person/form records; identical text does not merge IDs."
        },
        {
          "key": "facts",
          "use": "One name fact per form, and optional exact two-form connection facts. Connections require the two currently remembered name facts, without inferring those labels or a hidden bearer."
        },
        {
          "key": "observers",
          "use": "Separate fictional memory states, not empirical participant records."
        },
        {
          "key": "passes",
          "use": "2–12 root/parent records forming an acyclic forest. A child inherits only its own parent’s final state."
        },
        {
          "key": "initial",
          "use": "Explicit root-only memory seeds with scoped fact IDs; never silently injected into a child."
        },
        {
          "key": "policies",
          "use": "One reset policy per child/observer; missing policy clears memory. all/clear/only/except do not invent absent parent facts."
        },
        {
          "key": "events",
          "use": "Unique integer positions for learn/forget/use in a pass. use checks before-state and learns nothing; relearning records a new origin."
        },
        {
          "key": "observer",
          "use": "Focuses the comparison on one known observer; full private export retains all observers."
        },
        {
          "key": "viewA",
          "use": "First selected pass and exact unapplied trial reset target."
        },
        {
          "key": "viewB",
          "use": "Second different pass; may be sibling or descendant, with the distinction preserved."
        },
        {
          "key": "trialCarry",
          "use": "Off or a retention operator overriding only the first pass/observer in a separate calculation."
        },
        {
          "key": "trialFacts",
          "use": "Unique known fact IDs for only/except trials; no ignored list for off/all/clear."
        }
      ],
      "rules": [
        "Validate all IDs, exact references, pass acyclicity and unique event positions before calculating.",
        "Process parents before children and events by explicit integer positions, independent of JSON row order.",
        "Keep one mutable stored-fact map per pass/observer; inherit only through its declared parent reset.",
        "Retaining a connection without its name facts leaves it stored but incomplete. Do not add prerequisites as a repair.",
        "Use checks immediately preceding state; later learning does not rewrite earlier event results.",
        "A retained source preserves its origin and reset path. Learning records a new origin; forgetting removes only the selected current fact.",
        "A trial never mutates current policy inputs. Recompute affected descendants but do not borrow sibling memory.",
        "All outputs are private author records. No observer-safe redaction, cognitive measurement, real-world consent or automatic identity inference is claimed."
      ],
      "requiredData": [
        {
          "description": "Original fictional pass/observer/fact fixtures and literal name labels",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-authored reset policies and ordered scenes, not external psychology or historical naming data",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate all IDs, exact references, pass acyclicity and unique event positions before calculating.",
        "Process parents before children and events by explicit integer positions, independent of JSON row order.",
        "Keep one mutable stored-fact map per pass/observer; inherit only through its declared parent reset.",
        "Retaining a connection without its name facts leaves it stored but incomplete. Do not add prerequisites as a repair.",
        "Use checks immediately preceding state; later learning does not rewrite earlier event results.",
        "A retained source preserves its origin and reset path. Learning records a new origin; forgetting removes only the selected current fact.",
        "A trial never mutates current policy inputs. Recompute affected descendants but do not borrow sibling memory.",
        "All outputs are private author records. No observer-safe redaction, cognitive measurement, real-world consent or automatic identity inference is claimed."
      ],
      "outputs": [
        "Current and unapplied-trial entry/final memory checkpoints",
        "Before-event naming-use states with missing prerequisites and inherited source paths",
        "Requested-but-absent retention gaps without invented evidence",
        "Private full source/event audit and meaningful bilingual checkpoint copy text"
      ],
      "capabilities": [
        "Detect stored but ineffective name connections after selective loss and show exactly which subsequent lesson repairs a later use.",
        "Recompute one alternative retention policy through its descendants while preserving baseline input and sibling isolation."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary decision is whether a naming use has effective evidence after a reset, including retained relations with missing name prerequisites. This requires a parent forest, per-observer retention operators, mutable memory, event-before-state checks and inherited provenance. Linear reveal/first-use chapters do not erase or selectively carry memory, and identity-fork routing does not propagate observer memory facts.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "true-name-alias-bridge",
          "difference": "The existing identity bridge gates names and linear first-use connections by observer and chapter. This workbench recomputes initial memory from a parent's final state, supports all/clear/only/except resets, diagnoses a stored but unusable relation, keeps sibling histories isolated and previews one retention change through descendants without applying it. These differences are implemented and checked in the recorded reset/event and browser workflows; the genre label alone was not the reason to retain the page."
        }
      },
      "nearestTools": [
        {
          "id": "nw-time-loop-alias-experiment",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Audit explicit name and connection memory facts through reset-specific retention, loss and relearning, keeping parent sources, sibling branches and observer states separate. versus Record changing aliases and who can detect the pattern; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-time-coverage",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Audit explicit name and connection memory facts through reset-specific retention, loss and relearning, keeping parent sources, sibling branches and observer states separate. versus Track source dates and prohibit unsupported era filtering; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-time-traveler-cover-names",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Audit explicit name and connection memory facts through reset-specific retention, loss and relearning, keeping parent sources, sibling branches and observer states separate. versus Check alias references against story dates and social context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A remembered relation is not a substitute for the words that make a naming use possible after a reset.",
        "outline": [
          "Separate the author’s identity ledger from a speaker’s memory",
          "An original greenhouse repeat and a lost call sign",
          "Declare name facts and exact connection prerequisites",
          "Trace parent memory, selective retention and later learning",
          "Compare an unapplied policy without merging histories",
          "Export a private audit and repair the scene, not the past"
        ],
        "story": "In an invented mechanical greenhouse that repeats dusk, an apprentice retains a call-sign/full-name relation but loses its words. The curator can use a remembered call sign to stop an irrigation arm without needing the full identity connection. Relearning the words supports a later connection, not the earlier failed request. A clear-sky retention alternative stays a separate history.",
        "storyAnalysis": "Giving the apprentice all names back would remove the need for an earned reintroduction; giving everyone the curator’s memory would borrow evidence across observers. The reset policy changes the role a name plays in cooperation and trust. The scene is invented, not a psychological case.",
        "evidence": "Complete original EN/JA greenhouse guides, explicit counterfactuals, LOOP-01–17, initial HTML, 23 actual browser checks and nearest-task review. No psychology or demand evidence is implied.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/loopNames.md",
        "localizedBodies": {
          "en": "content/en/loopNames.md",
          "ja": "content/ja/loopNames.md"
        }
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Retaining only a connection keeps it stored but makes use incomplete until both names are relearned.",
        "Later learning cannot clear an earlier failed use, and use never teaches a fact.",
        "Changing one observer’s policy does not change another observer or an unrelated sibling.",
        "A changed reset source affects descendants and keeps the original source path; no facts are created from an absent request.",
        "Root seeds, all/clear/only/except and explicit forget produce different rule-constrained states.",
        "Cycles, duplicate positions, unsafe IDs, cross-person relations and over-limit input fail without partial commitment.",
        "Copy/export/favorite/compare/project restore, initial HTML and both localized mobile pages require actual checks before counting."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:640",
      "profileSource": "data/profiles.json#nonhuman",
      "specBatch": "batch-08",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Branch-scoped mutable state and provenance, alternative recomputation, careful private outputs and complete original bilingual guidance; no fabricated effort estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "loopNames",
        "engineFiles": [
          "web/loop-memory.mjs",
          "web/loop-tool.mjs",
          "web/loop-view.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/loop-memory.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "people",
          "label": [
            "Author-known people · JSON",
            "作者が知る人物・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"technician\",\n    \"label\": \"Teren Sable\"\n  }\n]",
          "help": [
            "IDs start with an ASCII letter, then letters/digits/_/-, at most 40 characters. Display labels may be Japanese. Private identity labels do not automatically become observer knowledge.",
            "IDは英字で始め、英数字・_・-の40文字以内。表示名は日本語も使えます。非公開の人物名は自動で観察者の知識になりません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "forms",
          "label": [
            "Exact name forms · JSON",
            "正確な名前の表記・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"call\",\n    \"person\": \"technician\",\n    \"text\": \"Moth\"\n  },\n  {\n    \"id\": \"full\",\n    \"person\": \"technician\",\n    \"text\": \"Teren Sable\"\n  }\n]",
          "help": [
            "id/person/text. Shared spelling never merges form or person IDs.",
            "id/person/text。同じ文字列でも表記や人物のIDを統合しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "facts",
          "label": [
            "Authored memory facts · JSON",
            "作者が定める記憶項目・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"heard-call\",\n    \"kind\": \"name\",\n    \"form\": \"call\"\n  },\n  {\n    \"id\": \"heard-full\",\n    \"kind\": \"name\",\n    \"form\": \"full\"\n  },\n  {\n    \"id\": \"same-person\",\n    \"kind\": \"connection\",\n    \"a\": \"call\",\n    \"b\": \"full\"\n  }\n]",
          "help": [
            "name remembers a literal label, not the hidden bearer. connection records two forms of one authored person and requires both name facts to be currently stored. No automatic transitive inference.",
            "nameは文字列の記憶で、隠された持ち主の認定ではありません。connectionは同一人物とした二表記の対応で、両方のname項目が現在必要です。推移的に推論しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "observers",
          "label": [
            "Observers · JSON",
            "観察者・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"apprentice\",\n    \"label\": \"Apprentice\"\n  },\n  {\n    \"id\": \"curator\",\n    \"label\": \"Curator\"\n  }\n]",
          "help": [
            "Separate authored memory states, not real participant records.",
            "架空の記憶状態を分けます。実際の参加者記録ではありません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "passes",
          "label": [
            "Passes and reset parents · JSON",
            "周回とリセット元・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"evening\",\n    \"label\": \"Original evening\",\n    \"parent\": null\n  },\n  {\n    \"id\": \"cloud\",\n    \"label\": \"Clouded repeat\",\n    \"parent\": \"evening\"\n  },\n  {\n    \"id\": \"clear\",\n    \"label\": \"Clear repeat\",\n    \"parent\": \"evening\"\n  }\n]",
          "help": [
            "2–12 passes. A child begins from its parent’s final state only. Siblings never exchange memories; array order is not chronology.",
            "2〜12周回。子は親の終了状態だけを引き継ぎます。兄弟間で記憶を借りず、配列の行順を時系列としません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "initial",
          "label": [
            "Root-only memory seeds · JSON",
            "起点だけの初期記憶・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "id/pass/observer/facts. Seeds are explicit declarations and cannot be attached to child passes.",
            "id/pass/observer/facts。初期記録は明示した宣言で、子の周回には付けられません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "policies",
          "label": [
            "Reset retention policies · JSON",
            "リセット時の保持規則・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"keep-relation\",\n    \"pass\": \"cloud\",\n    \"observer\": \"apprentice\",\n    \"carry\": \"only\",\n    \"facts\": [\n      \"same-person\"\n    ]\n  },\n  {\n    \"id\": \"keep-call\",\n    \"pass\": \"cloud\",\n    \"observer\": \"curator\",\n    \"carry\": \"all\",\n    \"facts\": []\n  },\n  {\n    \"id\": \"keep-everything\",\n    \"pass\": \"clear\",\n    \"observer\": \"apprentice\",\n    \"carry\": \"all\",\n    \"facts\": []\n  }\n]",
          "help": [
            "id/pass/observer/carry/facts. Missing policy clears that observer. all/clear require []; only/except select exact known fact IDs. A requested but absent fact is not created.",
            "id/pass/observer/carry/facts。規則がなければその観察者は全消去。all／clearは[]、only／exceptは正確な項目ID。元にない項目を生成しません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "events",
          "label": [
            "Ordered learn / forget / use events · JSON",
            "順序付きlearn／forget／use・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"hear-call\",\n    \"pass\": \"evening\",\n    \"at\": 0,\n    \"observer\": \"apprentice\",\n    \"action\": \"learn\",\n    \"fact\": \"heard-call\"\n  },\n  {\n    \"id\": \"hear-full\",\n    \"pass\": \"evening\",\n    \"at\": 1,\n    \"observer\": \"apprentice\",\n    \"action\": \"learn\",\n    \"fact\": \"heard-full\"\n  },\n  {\n    \"id\": \"connect\",\n    \"pass\": \"evening\",\n    \"at\": 2,\n    \"observer\": \"apprentice\",\n    \"action\": \"learn\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"curator-call\",\n    \"pass\": \"evening\",\n    \"at\": 3,\n    \"observer\": \"curator\",\n    \"action\": \"learn\",\n    \"fact\": \"heard-call\"\n  },\n  {\n    \"id\": \"first-use\",\n    \"pass\": \"evening\",\n    \"at\": 4,\n    \"observer\": \"apprentice\",\n    \"action\": \"use\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"before-relearning\",\n    \"pass\": \"cloud\",\n    \"at\": 0,\n    \"observer\": \"apprentice\",\n    \"action\": \"use\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"rehear-call\",\n    \"pass\": \"cloud\",\n    \"at\": 1,\n    \"observer\": \"apprentice\",\n    \"action\": \"learn\",\n    \"fact\": \"heard-call\"\n  },\n  {\n    \"id\": \"half-relearned\",\n    \"pass\": \"cloud\",\n    \"at\": 2,\n    \"observer\": \"apprentice\",\n    \"action\": \"use\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"rehear-full\",\n    \"pass\": \"cloud\",\n    \"at\": 3,\n    \"observer\": \"apprentice\",\n    \"action\": \"learn\",\n    \"fact\": \"heard-full\"\n  },\n  {\n    \"id\": \"after-relearning\",\n    \"pass\": \"cloud\",\n    \"at\": 4,\n    \"observer\": \"apprentice\",\n    \"action\": \"use\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"curator-keeps-call\",\n    \"pass\": \"cloud\",\n    \"at\": 5,\n    \"observer\": \"curator\",\n    \"action\": \"use\",\n    \"fact\": \"heard-call\"\n  },\n  {\n    \"id\": \"clear-use\",\n    \"pass\": \"clear\",\n    \"at\": 0,\n    \"observer\": \"apprentice\",\n    \"action\": \"use\",\n    \"fact\": \"same-person\"\n  },\n  {\n    \"id\": \"curator-forgets-call\",\n    \"pass\": \"clear\",\n    \"at\": 1,\n    \"observer\": \"curator\",\n    \"action\": \"use\",\n    \"fact\": \"heard-call\"\n  }\n]",
          "help": [
            "Unique id and integer at 0–10000; positions cannot tie within a pass. use checks the state before the event and teaches nothing. learn records a new source; forget removes only that fact.",
            "固有idと0〜10000の整数at。周回内の同順は禁止。useは直前を確認し、知識を追加しません。learnは新たな出所、forgetはその項目だけを除きます。"
          ],
          "maxLength": 150000
        },
        {
          "key": "observer",
          "label": [
            "Observer to compare",
            "比較する観察者"
          ],
          "type": "text",
          "default": "apprentice",
          "help": null
        },
        {
          "key": "viewA",
          "label": [
            "First pass / trial reset target",
            "第一の周回／試案の対象"
          ],
          "type": "text",
          "default": "cloud",
          "help": null
        },
        {
          "key": "viewB",
          "label": [
            "Second pass",
            "第二の周回"
          ],
          "type": "text",
          "default": "clear",
          "help": null
        },
        {
          "key": "trialCarry",
          "label": [
            "Unapplied retention alternative for first pass",
            "第一の周回の未適用保持案"
          ],
          "type": "select",
          "default": "all",
          "help": [
            "Only this observer’s first selected reset is overridden. Its descendants can change; siblings stay isolated. Current policy inputs remain unchanged.",
            "この観察者の第一選択のリセットだけを仮変更。子孫には影響し得ますが、兄弟は独立。現在の規則入力は変わりません。"
          ],
          "options": [
            [
              "off",
              [
                "No alternative",
                "試案なし"
              ]
            ],
            [
              "all",
              [
                "Retain all parent facts",
                "親の全項目を保持"
              ]
            ],
            [
              "clear",
              [
                "Clear all parent facts",
                "親の全項目を消去"
              ]
            ],
            [
              "only",
              [
                "Retain only listed facts",
                "指定項目だけ保持"
              ]
            ],
            [
              "except",
              [
                "Retain all except listed facts",
                "指定以外を保持"
              ]
            ]
          ]
        },
        {
          "key": "trialFacts",
          "label": [
            "Exact trial fact IDs · JSON",
            "試案の正確な項目ID・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "off/all/clear require []; only/except accept a unique ID list.",
            "off／all／clearは[]。only／exceptは重複しないID一覧です。"
          ],
          "maxLength": 150000
        }
      ]
    },
    {
      "id": "nw-dream-character-mutable-name",
      "slug": "dream-character-mutable-name",
      "name": "Dream character mutable name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/dream-character-mutable-name/",
        "ja": "/ja/tools/dream-character-mutable-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Define stable references across authored dream transformations",
      "task": "Define stable references across authored dream transformations",
      "searchIntent": {
        "primary": "Complete the task: Define stable references across authored dream transformations",
        "queryHypothesis": "dream character mutable name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define stable references across authored dream transformations?",
        "When should dream character mutable name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define stable references across authored dream transformations",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define stable references across authored dream transformations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dream-name-memory-anchor",
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Define stable references across authored dream transformations versus Define which form persists between dream and waking scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-localization-name-map",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define stable references across authored dream transformations versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-seasonal-name-change",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define stable references across authored dream transformations versus Define repeatable seasonal forms with stable identity underneath; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define stable references across authored dream transformations",
        "outline": [
          "Explain the specific decision: Define stable references across authored dream transformations",
          "Define the applicable contract and limits for Dream character mutable name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define stable references across authored dream transformations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define stable references across authored dream transformations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:641",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-elemental-identity-convention",
      "slug": "elemental-identity-convention",
      "name": "Elemental identity convention",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/elemental-identity-convention/",
        "ja": "/ja/tools/elemental-identity-convention/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Build explicit fictional naming rules beyond a single elemental adjective",
      "task": "Build explicit fictional naming rules beyond a single elemental adjective",
      "searchIntent": {
        "primary": "Complete the task: Build explicit fictional naming rules beyond a single elemental adjective",
        "queryHypothesis": "elemental identity convention",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build explicit fictional naming rules beyond a single elemental adjective?",
        "When should elemental identity convention be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build explicit fictional naming rules beyond a single elemental adjective",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build explicit fictional naming rules beyond a single elemental adjective. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Build explicit fictional naming rules beyond a single elemental adjective versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Build explicit fictional naming rules beyond a single elemental adjective versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-merged-identity-systems",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Build explicit fictional naming rules beyond a single elemental adjective versus Reconcile naming rules after two fictional organizations combine; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build explicit fictional naming rules beyond a single elemental adjective",
        "outline": [
          "Explain the specific decision: Build explicit fictional naming rules beyond a single elemental adjective",
          "Define the applicable contract and limits for Elemental identity convention",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build explicit fictional naming rules beyond a single elemental adjective; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build explicit fictional naming rules beyond a single elemental adjective",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:642",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-construct-creator-assigned-name",
      "slug": "construct-creator-assigned-name",
      "name": "Construct creator assigned name",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/construct-creator-assigned-name/",
        "ja": "/ja/tools/construct-creator-assigned-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Contrast creator labels with the construct's self identification",
      "task": "Contrast creator labels with the construct's self identification",
      "searchIntent": {
        "primary": "Complete the task: Contrast creator labels with the construct's self identification",
        "queryHypothesis": "construct creator assigned name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast creator labels with the construct's self identification?",
        "When should construct creator assigned name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast creator labels with the construct's self identification",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast creator labels with the construct's self identification. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Contrast creator labels with the construct's self identification versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-investigator-public-reputation",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Contrast creator labels with the construct's self identification versus Contrast newspaper label, professional title and self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Contrast creator labels with the construct's self identification versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast creator labels with the construct's self identification",
        "outline": [
          "Explain the specific decision: Contrast creator labels with the construct's self identification",
          "Define the applicable contract and limits for Construct creator assigned name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast creator labels with the construct's self identification; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast creator labels with the construct's self identification",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:643",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-plant-person-seasonal-identity",
      "slug": "plant-person-seasonal-identity",
      "name": "Plant person seasonal identity",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/plant-person-seasonal-identity/",
        "ja": "/ja/tools/plant-person-seasonal-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Link seasonal forms to continuity in an invented biology",
      "task": "Link seasonal forms to continuity in an invented biology",
      "searchIntent": {
        "primary": "Complete the task: Link seasonal forms to continuity in an invented biology",
        "queryHypothesis": "plant person seasonal identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link seasonal forms to continuity in an invented biology?",
        "When should plant person seasonal identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link seasonal forms to continuity in an invented biology",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link seasonal forms to continuity in an invented biology. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-uploaded-person-identity",
          "score": 0.18642857142857142,
          "sharedProfile": true,
          "difference": "Link seasonal forms to continuity in an invented biology versus Model continuity claims as story positions rather than scientific fact; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-seasonal-name-change",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Link seasonal forms to continuity in an invented biology versus Define repeatable seasonal forms with stable identity underneath; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-nickname-adoption",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Link seasonal forms to continuity in an invented biology versus Track table invented nicknames separately from in world forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link seasonal forms to continuity in an invented biology",
        "outline": [
          "Explain the specific decision: Link seasonal forms to continuity in an invented biology",
          "Define the applicable contract and limits for Plant person seasonal identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link seasonal forms to continuity in an invented biology; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link seasonal forms to continuity in an invented biology",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:644",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-ocean-species-visual-names",
      "slug": "ocean-species-visual-names",
      "name": "Ocean species visual names",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/ocean-species-visual-names/",
        "ja": "/ja/tools/ocean-species-visual-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Translate authored color patterns into reader usable names",
      "task": "Translate authored color patterns into reader usable names",
      "searchIntent": {
        "primary": "Complete the task: Translate authored color patterns into reader usable names",
        "queryHypothesis": "ocean species visual names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to translate authored color patterns into reader usable names?",
        "When should ocean species visual names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Translate authored color patterns into reader usable names",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Translate authored color patterns into reader usable names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-sensory-name-translation",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Translate authored color patterns into reader usable names versus Translate nonspoken identity cues into readable narrative labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-alias-spoiler-boundary",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Translate authored color patterns into reader usable names versus Export reader facing names by installment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-species-pronoun-name-boundary",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Translate authored color patterns into reader usable names versus Avoid inferring identity or pronouns solely from species naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Translate authored color patterns into reader usable names",
        "outline": [
          "Explain the specific decision: Translate authored color patterns into reader usable names",
          "Define the applicable contract and limits for Ocean species visual names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Translate authored color patterns into reader usable names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Translate authored color patterns into reader usable names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:645",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-telepathic-identity-tokens",
      "slug": "telepathic-identity-tokens",
      "name": "Telepathic identity tokens",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/telepathic-identity-tokens/",
        "ja": "/ja/tools/telepathic-identity-tokens/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Define how shared mental identities appear in prose",
      "task": "Define how shared mental identities appear in prose",
      "searchIntent": {
        "primary": "Complete the task: Define how shared mental identities appear in prose",
        "queryHypothesis": "telepathic identity tokens",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define how shared mental identities appear in prose?",
        "When should telepathic identity tokens be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define how shared mental identities appear in prose",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define how shared mental identities appear in prose. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-frontier-settlement-naming",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define how shared mental identities appear in prose versus Define how newcomers retain or adapt personal identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Define how shared mental identities appear in prose versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clone-identity-differentiation",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Define how shared mental identities appear in prose versus Assign legal, personal and laboratory identities to cloned characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define how shared mental identities appear in prose",
        "outline": [
          "Explain the specific decision: Define how shared mental identities appear in prose",
          "Define the applicable contract and limits for Telepathic identity tokens",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define how shared mental identities appear in prose; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define how shared mental identities appear in prose",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:646",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-nonverbal-character-naming",
      "slug": "nonverbal-character-naming",
      "name": "Nonverbal character naming",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/nonverbal-character-naming/",
        "ja": "/ja/tools/nonverbal-character-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Separate communicated identity from other characters' labels",
      "task": "Separate communicated identity from other characters' labels",
      "searchIntent": {
        "primary": "Complete the task: Separate communicated identity from other characters' labels",
        "queryHypothesis": "nonverbal character naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate communicated identity from other characters' labels?",
        "When should nonverbal character naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate communicated identity from other characters' labels",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate communicated identity from other characters' labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-boss-true-name-reveal",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate communicated identity from other characters' labels versus Coordinate combat labels and later identity discoveries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-identity-translation",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Separate communicated identity from other characters' labels versus Convert an authored sensory identity system into readable labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sensory-name-translation",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate communicated identity from other characters' labels versus Translate nonspoken identity cues into readable narrative labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate communicated identity from other characters' labels",
        "outline": [
          "Explain the specific decision: Separate communicated identity from other characters' labels",
          "Define the applicable contract and limits for Nonverbal character naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate communicated identity from other characters' labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate communicated identity from other characters' labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:647",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-species-pronoun-name-boundary",
      "slug": "species-pronoun-name-boundary",
      "name": "Species pronoun name boundary",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/species-pronoun-name-boundary/",
        "ja": "/ja/tools/species-pronoun-name-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Avoid inferring identity or pronouns solely from species naming rules",
      "task": "Avoid inferring identity or pronouns solely from species naming rules",
      "searchIntent": {
        "primary": "Complete the task: Avoid inferring identity or pronouns solely from species naming rules",
        "queryHypothesis": "species pronoun name boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid inferring identity or pronouns solely from species naming rules?",
        "When should species pronoun name boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid inferring identity or pronouns solely from species naming rules",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid inferring identity or pronouns solely from species naming rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-order-initiation-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid inferring identity or pronouns solely from species naming rules versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wizard-order-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid inferring identity or pronouns solely from species naming rules versus Apply fictional rank and initiation rules to a personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Avoid inferring identity or pronouns solely from species naming rules versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid inferring identity or pronouns solely from species naming rules",
        "outline": [
          "Explain the specific decision: Avoid inferring identity or pronouns solely from species naming rules",
          "Define the applicable contract and limits for Species pronoun name boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid inferring identity or pronouns solely from species naming rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid inferring identity or pronouns solely from species naming rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:648",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-nonhuman-family-transmission",
      "slug": "nonhuman-family-transmission",
      "name": "Nonhuman family transmission",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/nonhuman-family-transmission/",
        "ja": "/ja/tools/nonhuman-family-transmission/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Model kinship rules without assuming human household structures",
      "task": "Model kinship rules without assuming human household structures",
      "searchIntent": {
        "primary": "Complete the task: Model kinship rules without assuming human household structures",
        "queryHypothesis": "nonhuman family transmission",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model kinship rules without assuming human household structures?",
        "When should nonhuman family transmission be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model kinship rules without assuming human household structures",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model kinship rules without assuming human household structures. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-family-generation",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Model kinship rules without assuming human household structures versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-family-repeated-kanji",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Model kinship rules without assuming human household structures versus Track shared characters without assuming universal family practice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-found-family-address-system",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Model kinship rules without assuming human household structures versus Design elective kinship terms without implying blood relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model kinship rules without assuming human household structures",
        "outline": [
          "Explain the specific decision: Model kinship rules without assuming human household structures",
          "Define the applicable contract and limits for Nonhuman family transmission",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model kinship rules without assuming human household structures; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model kinship rules without assuming human household structures",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:649",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-nonhuman-culture-naming-contrast",
      "slug": "nonhuman-culture-naming-contrast",
      "name": "Nonhuman culture naming contrast",
      "category": "nonhuman",
      "urls": {
        "en": "/en/tools/nonhuman-culture-naming-contrast/",
        "ja": "/ja/tools/nonhuman-culture-naming-contrast/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative fiction and game creators",
      "scenario": "Distinguish cultures within a species rather than one species one style",
      "task": "Distinguish cultures within a species rather than one species one style",
      "searchIntent": {
        "primary": "Complete the task: Distinguish cultures within a species rather than one species one style",
        "queryHypothesis": "nonhuman culture naming contrast",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish cultures within a species rather than one species one style?",
        "When should nonhuman culture naming contrast be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored identity model: define continuity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "communication system: constrain readable translation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "self and imposed labels: preserve agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not assume species implies one culture",
        "separate technical designation from chosen identity"
      ],
      "requiredData": [
        {
          "description": "original species and culture grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity transition events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored narrative rendering policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish cultures within a species rather than one species one style",
        "do not assume species implies one culture",
        "separate technical designation from chosen identity",
        "Proposed category workflow: identity assumptions → name layers → transition simulation → reader clarity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity layers",
        "human readable rendering",
        "continuity and assumption warnings"
      ],
      "capabilities": [
        "simulate changes in body or substrate without automatic identity replacement",
        "compare self chosen and observer assigned labels"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish cultures within a species rather than one species one style. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-culture-naming-contrast",
          "score": 0.2833333333333333,
          "sharedProfile": false,
          "difference": "Distinguish cultures within a species rather than one species one style versus Compare two invented cultures using explicit structural rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undead-renaming-decision",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Distinguish cultures within a species rather than one species one style versus Tie a name change to character agency rather than species stereotype; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-utopian-naming-institutions",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Distinguish cultures within a species rather than one species one style versus Specify actual rules and exceptions rather than a positive style adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish cultures within a species rather than one species one style",
        "outline": [
          "Explain the specific decision: Distinguish cultures within a species rather than one species one style",
          "Define the applicable contract and limits for Nonhuman culture naming contrast",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish cultures within a species rather than one species one style; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish cultures within a species rather than one species one style",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:650",
      "profileSource": "data/profiles.json#nonhuman"
    },
    {
      "id": "nw-suspect-name-roster",
      "slug": "suspect-name-roster",
      "name": "Suspect name roster",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/suspect-name-roster/",
        "ja": "/ja/tools/suspect-name-roster/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Distinguish suspects while preserving intentionally misleading associations",
      "task": "Distinguish suspects while preserving intentionally misleading associations",
      "searchIntent": {
        "primary": "Complete the task: Distinguish suspects while preserving intentionally misleading associations",
        "queryHypothesis": "suspect name roster",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish suspects while preserving intentionally misleading associations?",
        "When should suspect name roster be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "suspects",
          "use": "Stable IDs, public forms and hidden links."
        },
        {
          "key": "clueRules",
          "use": "Specify initials, signature or address clues the reader can learn."
        },
        {
          "key": "disclosures",
          "use": "Place evidence at known chapters."
        },
        {
          "key": "solution",
          "use": "Test the intended culprit and all alternatives separately."
        }
      ],
      "rules": [
        "Do not use ethnicity inferred from a name as evidence of guilt.",
        "Enumerate all suspects satisfying each disclosed name clue.",
        "A clue depending on unprovided language knowledge remains unresolved.",
        "Distinguish a narrator's false attribution from the story's established fact.",
        "Reader exports omit solution-only identity fields."
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate the task-specific input contract",
        "Do not use ethnicity inferred from a name as evidence of guilt.",
        "Enumerate all suspects satisfying each disclosed name clue.",
        "A clue depending on unprovided language knowledge remains unresolved.",
        "Distinguish a narrator's false attribution from the story's established fact.",
        "Reader exports omit solution-only identity fields.",
        "Emit structured explanations and unrelaxed conflict status"
      ],
      "outputs": [
        "public suspect roster",
        "clue by suspect satisfaction table",
        "alternative solutions",
        "unearned deduction warnings",
        "spoiler safe recap"
      ],
      "capabilities": [
        "Show the remaining suspects after each disclosed clue.",
        "Recompute fairness after a suspect is renamed."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "A mystery cast must distinguish suspects while controlling clues, red herrings and reader knowledge across a fair solution path.",
        "proposedDifferenceAxes": [
          "inputs",
          "evaluation",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rpg-companion-name-roster",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Distinguish suspects while preserving intentionally misleading associations versus Distinguish companions in dialogue and party UI; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unspoken-name-scene",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Distinguish suspects while preserving intentionally misleading associations versus Keep a name off the page while preserving referential clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-replacement",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Distinguish suspects while preserving intentionally misleading associations versus Replace one established name while preserving story dependencies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A name clue should narrow disclosed possibilities rather than certify an author's intention.",
        "outline": [
          "Make suspects memorable before making them suspicious",
          "Write the clue rule in reader-visible terms",
          "The club register with two matching initials",
          "Keep a red herring possible but defeasible",
          "Recheck every dependent clue after a rename"
        ],
        "story": "Fictional example: a missing club ledger page is signed with initials that match two members. A previously shown private salutation narrows access to one sender, while a third person remains capable of copying it.",
        "storyAnalysis": "Explain why the initials alone are insufficient and how a copyist alternative changes the conclusion. A fair clue supports a bounded deduction.",
        "evidence": "Original suspect and chapter fixtures; no claim of a completed reader study.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/mystery.md",
        "localizedBodies": {
          "en": "content/en/mystery.md",
          "ja": "content/ja/mystery.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "high",
      "acceptance": [
        "An initials clue matching two suspects does not report a unique answer.",
        "A solution identity is omitted from the early-chapter roster.",
        "Renaming one suspect invalidates dependent clues with a precise warning.",
        "A clue with no eligible suspect reports inconsistency rather than inventing evidence."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": true,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Executable task workflows and automated scenarios exist; autonomous checks proceed under the user’s authorization; no human signature is asserted.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:653",
      "profileSource": "data/profiles.json#mystery",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "mystery",
        "engineFiles": [
          "web/engines.mjs",
          "web/advanced.mjs",
          "web/workflows.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "suspects",
          "label": [
            "Suspects",
            "容疑者"
          ],
          "type": "textarea",
          "default": "a | Aven Reed | Quill\nb | Arden Rowe | Rook\nc | Sela Morrow | Vale",
          "help": [
            "ID | full name | supplied nickname. These are fictional examples.",
            "ID | 姓名 | 設定した別名。入力例はすべて創作です。"
          ]
        },
        {
          "key": "clues",
          "label": [
            "Clue rules and disclosure",
            "手掛かりのルールと開示章"
          ],
          "type": "textarea",
          "default": "initials | AR | 1\nnickname | Quill | 4",
          "help": [
            "initials or nickname | matching value | reveal chapter. Matching does not prove guilt.",
            "initials または nickname | 一致させる値 | 開示章。一致は有罪の証明ではありません。"
          ]
        },
        {
          "key": "chapter",
          "label": [
            "Reader chapter",
            "読者が到達した章"
          ],
          "type": "number",
          "default": 1,
          "help": null
        },
        {
          "key": "rename",
          "label": [
            "Counterfactual renames",
            "改名した場合の影響"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "suspect ID | replacement name. Does not alter the original roster.",
            "人物ID | 改名案。元の一覧は変更しません。"
          ]
        }
      ]
    },
    {
      "id": "nw-name-anagram-clue-designer",
      "slug": "name-anagram-clue-designer",
      "name": "Name anagram clue designer",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-anagram-clue-designer/",
        "ja": "/ja/tools/name-anagram-clue-designer/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Generate reversible transformations with a stated clue path",
      "task": "Construct and verify an exact letter-inventory transformation between supplied name candidates and an authored clue path.",
      "searchIntent": {
        "primary": "Complete the task: Generate reversible transformations with a stated clue path",
        "queryHypothesis": "name anagram clue designer",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to generate reversible transformations with a stated clue path?",
        "When should name anagram clue designer be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "candidates",
          "use": "Supplied name IDs and exact strings, without generated historical claims."
        },
        {
          "key": "target",
          "use": "Authored clue token or target text."
        },
        {
          "key": "policy",
          "use": "Declared case, spacing and punctuation treatment; script preservation."
        },
        {
          "key": "operations",
          "use": "Explicit permitted operations and any stated added/removed symbols."
        }
      ],
      "rules": [
        "Preserve raw strings and disclose any comparison normalization.",
        "List each inventory mismatch; do not silently drop inconvenient letters.",
        "A reversible pure-anagram claim requires equal counts under the selected policy.",
        "Added or removed symbols produce a different labeled operation.",
        "Do not invent a linguistic pun, pronunciation or source quotation.",
        "Keep the solution key separate from reader-facing clue material."
      ],
      "requiredData": [
        {
          "description": "User-authored candidates and clue text",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Explicit symbol-inventory policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Preserve raw strings and disclose any comparison normalization.",
        "List each inventory mismatch; do not silently drop inconvenient letters.",
        "A reversible pure-anagram claim requires equal counts under the selected policy.",
        "Added or removed symbols produce a different labeled operation.",
        "Do not invent a linguistic pun, pronunciation or source quotation.",
        "Keep the solution key separate from reader-facing clue material."
      ],
      "outputs": [
        "Per-candidate letter inventory comparison",
        "Reversible operation trace or mismatch report",
        "Separate clue draft and solution-key handoffs"
      ],
      "capabilities": [
        "Show repeated-letter deficits that a set-based comparison would miss.",
        "Distinguish a pure anagram from a transformation that needs an extra symbol or an unprovided convention."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The main task is generating a reversible transformation proof and checking stated puzzle operations; a suspect roster only filters already supplied clue matches.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "suspect-name-roster",
          "difference": "The roster evaluates disclosed initials/nickname rules; this design task traces exact symbol inventories, normalization policy and permitted transformations before drafting the clue."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-acrostic-clue-designer",
          "score": 0.20326086956521738,
          "sharedProfile": true,
          "difference": "Construct and verify an exact letter-inventory transformation between supplied name candidates and an authored clue path. versus Check an authored ordered clue text against name targets while preserving line constraints and reader-available extraction rules.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Construct and verify an exact letter-inventory transformation between supplied name candidates and an authored clue path. versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-designer",
          "score": 0.13083333333333333,
          "sharedProfile": false,
          "difference": "Construct and verify an exact letter-inventory transformation between supplied name candidates and an authored clue path. versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "An anagram clue needs an inspectable transformation, not a suggestive resemblance.",
        "outline": [
          "Count repeated symbols",
          "Name the allowed operation",
          "Fictional scene: a copied museum label",
          "Keep the solution out of the clue sheet",
          "Check fairness after a rename"
        ],
        "story": "A curator copies a label with one repeated letter missing. A draft puzzle still announces an exact anagram. The writer must restore the letter, acknowledge the copying error as an operation or abandon the claimed transformation.",
        "storyAnalysis": "A similar-looking replacement name can retain the set of letters yet change their multiplicity and break the solution.",
        "evidence": "Original symbol fixtures; no copied literary puzzle or real etymology.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/anagram.md",
        "localizedBodies": {
          "en": "content/en/anagram.md",
          "ja": "content/ja/anagram.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Equal symbol sets with different repeated-letter counts fail pure-anagram verification.",
        "Case/spacing changes affect only the chosen policy.",
        "A requested added letter is recorded in the operation trace rather than hidden.",
        "Reader export omits the solution mapping.",
        "Unknown external puns remain unsupported."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:654",
      "profileSource": "data/profiles.json#mystery",
      "specBatch": "batch-02",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "anagram",
        "engineFiles": [
          "web/anagram-proof.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/anagram.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "candidates",
          "label": [
            "Name candidates · JSON",
            "名前の候補・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"mira\",\n    \"name\": \"Mira Vale\"\n  },\n  {\n    \"id\": \"near\",\n    \"name\": \"Mira Vell\"\n  }\n]",
          "help": null
        },
        {
          "key": "target",
          "label": [
            "Visible clue token",
            "手掛かりの文字列"
          ],
          "type": "text",
          "default": "A Rival Me",
          "help": null
        },
        {
          "key": "normalization",
          "label": [
            "Unicode normalization",
            "Unicode正規化"
          ],
          "type": "select",
          "default": "nfc",
          "help": null,
          "options": [
            [
              "raw",
              [
                "Preserve code points",
                "コードポイントを保持"
              ]
            ],
            [
              "nfc",
              [
                "NFC before other policies",
                "ほかの処理の前にNFC"
              ]
            ]
          ]
        },
        {
          "key": "casePolicy",
          "label": [
            "Letter case",
            "大小文字"
          ],
          "type": "select",
          "default": "lower",
          "help": null,
          "options": [
            [
              "exact",
              [
                "Preserve case",
                "大小を保持"
              ]
            ],
            [
              "lower",
              [
                "Unicode lowercase",
                "Unicode小文字化"
              ]
            ]
          ]
        },
        {
          "key": "ignoreWhitespace",
          "label": [
            "Ignore Unicode whitespace in comparison",
            "比較時にUnicode空白を除く"
          ],
          "type": "checkbox",
          "default": true,
          "help": null
        },
        {
          "key": "ignorePunctuation",
          "label": [
            "Ignore Unicode punctuation in comparison",
            "比較時にUnicode句読点を除く"
          ],
          "type": "checkbox",
          "default": false,
          "help": null
        },
        {
          "key": "operation",
          "label": [
            "Permitted operation",
            "許可する操作"
          ],
          "type": "select",
          "default": "pure",
          "help": null,
          "options": [
            [
              "pure",
              [
                "Pure rearrangement",
                "純粋な並べ替え"
              ]
            ],
            [
              "declared-edit",
              [
                "Declared additions/removals, then rearrange",
                "指定した増減の後で並べ替え"
              ]
            ]
          ]
        },
        {
          "key": "added",
          "label": [
            "Explicitly added symbols",
            "明示して追加する文字"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "removed",
          "label": [
            "Explicitly removed symbols",
            "明示して削除する文字"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "clueText",
          "label": [
            "Authored public clue text",
            "作者が書く公開の手掛かり文"
          ],
          "type": "textarea",
          "default": "The copied label reads: A Rival Me.",
          "help": [
            "The public sheet preserves exactly what you write; it does not detect an answer accidentally included in your prose.",
            "公開の表には入力した文章をそのまま残します。文章内に答えを誤って書いた場合は検出しません。"
          ]
        },
        {
          "key": "ruleHint",
          "label": [
            "Authored reader rule hint",
            "作者が書く読者向け規則のヒント"
          ],
          "type": "textarea",
          "default": "Rearrange the letters, ignoring spaces and case.",
          "help": [
            "An inventory match does not prove that this hint fairly teaches the operation. Review it in the story.",
            "文字数の一致だけでは、ヒントが操作を公平に伝えるとは証明しません。物語内で確認してください。"
          ]
        }
      ]
    },
    {
      "id": "nw-name-acrostic-clue-designer",
      "slug": "name-acrostic-clue-designer",
      "name": "Name acrostic clue designer",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-acrostic-clue-designer/",
        "ja": "/ja/tools/name-acrostic-clue-designer/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Fit a name to authored clue text without arbitrary filler",
      "task": "Check an authored ordered clue text against name targets while preserving line constraints and reader-available extraction rules.",
      "searchIntent": {
        "primary": "Complete the task: Fit a name to authored clue text without arbitrary filler",
        "queryHypothesis": "name acrostic clue designer",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to fit a name to authored clue text without arbitrary filler?",
        "When should name acrostic clue designer be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "lines",
          "use": "Stable line ID, authored text and locked/unlocked revision status."
        },
        {
          "key": "target",
          "use": "Exact intended extracted name."
        },
        {
          "key": "extraction",
          "use": "Explicit first/last token/character rule and treatment of blank lines."
        },
        {
          "key": "proposals",
          "use": "Optional author-written line alternatives; no arbitrary generated filler."
        }
      ],
      "rules": [
        "Extract only with a declared position-sensitive rule.",
        "Preserve line order and show line-by-line extracted units.",
        "Never invent unrelated lines merely to meet target letters.",
        "Locked lines cannot be silently replaced.",
        "Ambiguous or empty extraction units remain visible diagnostics.",
        "Reader-facing export states only the intended public clue, not the hidden target or solution path."
      ],
      "requiredData": [
        {
          "description": "Author-owned clue lines",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Authored alternatives and extraction policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Extract only with a declared position-sensitive rule.",
        "Preserve line order and show line-by-line extracted units.",
        "Never invent unrelated lines merely to meet target letters.",
        "Locked lines cannot be silently replaced.",
        "Ambiguous or empty extraction units remain visible diagnostics.",
        "Reader-facing export states only the intended public clue, not the hidden target or solution path."
      ],
      "outputs": [
        "Ordered extraction trace",
        "Target mismatch positions and locked-line conflicts",
        "Separate revised clue text and solution-key handoffs"
      ],
      "capabilities": [
        "Explain why a line reorder breaks the name even though the same letters remain.",
        "Compare author-supplied line alternatives without rewriting locked story facts."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "This task resolves ordered line extraction and revision constraints; an anagram inventory discards order and cannot validate the same puzzle.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "name-anagram-clue-designer",
          "difference": "Acrostic validates position-sensitive ordered extraction and line locks; anagram checks unordered multiplicities and a different reader operation."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-anagram-clue-designer",
          "score": 0.20326086956521738,
          "sharedProfile": true,
          "difference": "Check an authored ordered clue text against name targets while preserving line constraints and reader-available extraction rules. versus Construct and verify an exact letter-inventory transformation between supplied name candidates and an authored clue path.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Check an authored ordered clue text against name targets while preserving line constraints and reader-available extraction rules. versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.15592105263157896,
          "sharedProfile": true,
          "difference": "Check an authored ordered clue text against name targets while preserving line constraints and reader-available extraction rules. versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A line that spells a letter must still belong in the story.",
        "outline": [
          "Declare extraction before revising lines",
          "Preserve locks and meaning",
          "Fictional scene: a garden instruction card",
          "Compare a correct letter with a wrong instruction",
          "Separate clue and solution exports"
        ],
        "story": "A gardening club hides a visitor’s name in an instruction card. Changing a line to force one letter would instruct a character to damage a plant established as important earlier. The writer changes the target or supplies a plausible alternate instruction instead.",
        "storyAnalysis": "The spelling can be formally right while the card becomes narratively wrong; show both checks rather than rewarding a completed target alone.",
        "evidence": "Original clue-line fixtures and authored alternatives only.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/acrostic.md",
        "localizedBodies": {
          "en": "content/en/acrostic.md",
          "ja": "content/ja/acrostic.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Reordering two lines changes extracted order.",
        "A locked mismatch remains unresolved.",
        "Blank/short lines follow the declared policy or fail explicitly.",
        "Author alternatives must satisfy both position and lock constraints.",
        "Reader export contains no hidden target string or extraction-key field."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:655",
      "profileSource": "data/profiles.json#mystery",
      "specBatch": "batch-02",
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "acrostic",
        "engineFiles": [
          "web/ordered-clue.mjs",
          "web/clue-editor.js",
          "scripts/render-clue-editor.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/acrostic.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "lines",
          "label": [
            "Ordered clue lines · JSON",
            "順序付きの行・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"l1\",\n    \"text\": \"Mist the fern tray lightly.\",\n    \"locked\": true\n  },\n  {\n    \"id\": \"l2\",\n    \"text\": \"Inspect the shaded pots.\",\n    \"locked\": false\n  },\n  {\n    \"id\": \"l3\",\n    \"text\": \"Return the labels after watering.\",\n    \"locked\": false\n  },\n  {\n    \"id\": \"l4\",\n    \"text\": \"Keep the rare cutting in shade.\",\n    \"locked\": true\n  }\n]",
          "help": null,
          "maxLength": 150000
        },
        {
          "key": "target",
          "label": [
            "Intended hidden name",
            "意図する隠れた名前"
          ],
          "type": "text",
          "default": "MIRA",
          "help": null
        },
        {
          "key": "extraction",
          "label": [
            "Extraction rule",
            "抽出する規則"
          ],
          "type": "select",
          "default": "first-grapheme",
          "help": null,
          "options": [
            [
              "first-grapheme",
              [
                "First grapheme of each line",
                "各行の先頭書記素"
              ]
            ],
            [
              "last-grapheme",
              [
                "Last grapheme of each line",
                "各行の末尾書記素"
              ]
            ],
            [
              "first-token",
              [
                "First whitespace-delimited token",
                "空白で区切る先頭の語"
              ]
            ],
            [
              "last-token",
              [
                "Last whitespace-delimited token",
                "空白で区切る末尾の語"
              ]
            ]
          ]
        },
        {
          "key": "blankPolicy",
          "label": [
            "Blank-line policy",
            "空行の方針"
          ],
          "type": "select",
          "default": "skip",
          "help": null,
          "options": [
            [
              "skip",
              [
                "Skip in extraction; preserve in clue",
                "抽出から除き、手掛かりには保持"
              ]
            ],
            [
              "reject",
              [
                "Report blank lines as unresolved",
                "空行を未解決として報告"
              ]
            ]
          ]
        },
        {
          "key": "trimEdges",
          "label": [
            "Trim outer whitespace before grapheme extraction",
            "書記素抽出前に前後空白を除く"
          ],
          "type": "checkbox",
          "default": true,
          "help": null
        },
        {
          "key": "comparison",
          "label": [
            "Target comparison",
            "目標との比較"
          ],
          "type": "select",
          "default": "nfc-lower",
          "help": null,
          "options": [
            [
              "exact",
              [
                "Exact extracted text",
                "抽出文の完全一致"
              ]
            ],
            [
              "nfc",
              [
                "NFC",
                "NFC"
              ]
            ],
            [
              "nfc-lower",
              [
                "NFC then Unicode lowercase",
                "NFCの後にUnicode小文字化"
              ]
            ]
          ]
        },
        {
          "key": "separator",
          "label": [
            "Join extracted units with",
            "抽出した単位の区切り"
          ],
          "type": "text",
          "default": "",
          "help": null
        },
        {
          "key": "proposals",
          "label": [
            "Authored alternatives · JSON",
            "作者の代案・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"damaging\",\n    \"lineId\": \"l4\",\n    \"text\": \"Arrange the rare cutting in full sun.\",\n    \"reason\": \"Forces A but contradicts the established shade instruction.\"\n  },\n  {\n    \"id\": \"safe-four\",\n    \"lineId\": \"l4\",\n    \"text\": \"Attend to the shade around the rare cutting.\",\n    \"reason\": \"An authored possibility that still needs a horticultural and story-context review.\"\n  }\n]",
          "help": [
            "id, lineId, text, reason. No text is generated or judged safe. Locks protect text, not ordering.",
            "id、lineId、text、reason。文章を生成せず、安全性も判断しません。固定は本文に対するもので、順序の固定ではありません。"
          ]
        },
        {
          "key": "selectedProposals",
          "label": [
            "Selected alternative IDs · optional",
            "選ぶ代案ID・任意"
          ],
          "type": "text",
          "default": "safe-four",
          "help": [
            "Comma-separated proposal IDs, at most one per line. A selected edit to locked text stays blocked.",
            "カンマ区切りで一行に一案まで。固定した本文への変更は適用しません。"
          ]
        },
        {
          "key": "ruleHint",
          "label": [
            "Authored reader-facing hint",
            "作者の読者向けヒント"
          ],
          "type": "textarea",
          "default": "Read the first letter of each instruction, in order.",
          "help": [
            "The reader sheet omits target and trace fields but cannot detect answers written in your clue lines or hint.",
            "読者表は目標と経路の項目を除きますが、行やヒントに作者が書いた答えは検出しません。"
          ]
        }
      ]
    },
    {
      "id": "nw-initials-clue-fairness",
      "slug": "initials-clue-fairness",
      "name": "Initials clue fairness",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/initials-clue-fairness/",
        "ja": "/ja/tools/initials-clue-fairness/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Check all plausible suspects rather than only the intended solution",
      "task": "Check all plausible suspects rather than only the intended solution",
      "searchIntent": {
        "primary": "Complete the task: Check all plausible suspects rather than only the intended solution",
        "queryHypothesis": "initials clue fairness",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check all plausible suspects rather than only the intended solution?",
        "When should initials clue fairness be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check all plausible suspects rather than only the intended solution",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check all plausible suspects rather than only the intended solution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-initials-clue",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Check all plausible suspects rather than only the intended solution versus Repair initials dependent reveals without changing unrelated character facts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.13083333333333333,
          "sharedProfile": true,
          "difference": "Check all plausible suspects rather than only the intended solution versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-miswritten-clue",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Check all plausible suspects rather than only the intended solution versus Separate plausible graphic confusion from arbitrary substitutions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check all plausible suspects rather than only the intended solution",
        "outline": [
          "Explain the specific decision: Check all plausible suspects rather than only the intended solution",
          "Define the applicable contract and limits for Initials clue fairness",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check all plausible suspects rather than only the intended solution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check all plausible suspects rather than only the intended solution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:656",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-signature-discrepancy-clue",
      "slug": "signature-discrepancy-clue",
      "name": "Signature discrepancy clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/signature-discrepancy-clue/",
        "ja": "/ja/tools/signature-discrepancy-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Compare supplied signatures and plot relevant differences",
      "task": "Compare supplied signatures and plot relevant differences",
      "searchIntent": {
        "primary": "Complete the task: Compare supplied signatures and plot relevant differences",
        "queryHypothesis": "signature discrepancy clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare supplied signatures and plot relevant differences?",
        "When should signature discrepancy clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare supplied signatures and plot relevant differences",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare supplied signatures and plot relevant differences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-signature-legibility",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Compare supplied signatures and plot relevant differences versus Compare supplied signatures at realistic display sizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Compare supplied signatures and plot relevant differences versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-ending-signature",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare supplied signatures and plot relevant differences versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare supplied signatures and plot relevant differences",
        "outline": [
          "Explain the specific decision: Compare supplied signatures and plot relevant differences",
          "Define the applicable contract and limits for Signature discrepancy clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare supplied signatures and plot relevant differences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare supplied signatures and plot relevant differences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:657",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-misfiled-name-clue",
      "slug": "misfiled-name-clue",
      "name": "Misfiled name clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/misfiled-name-clue/",
        "ja": "/ja/tools/misfiled-name-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Mystery novelists, comic creators and puzzle-game writers preparing a visibly ordered name prop.",
      "scenario": "A fictional costume rack violates a posted family-first convention while fitting a given-first alternative; a performer mistakes that violation for proof of hostile interference.",
      "task": "Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction.",
      "searchIntent": {
        "primary": "Design and audit a misfiled-name clue using a rule a reader can inspect.",
        "queryHypothesis": "misfiled name clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can a name order violate one rule while matching another?",
        "What can a tie in two filing parts actually prove?",
        "Does one inverted pair identify who moved a nameplate?"
      ],
      "inputs": [
        {
          "key": "records",
          "use": "2–40 records. id/name/primary/secondary. Declare the filing parts yourself; the tool does not parse names or guess readings. IDs start with an ASCII letter."
        },
        {
          "key": "printedOrder",
          "use": "Every record ID once. This is the prop the reader sees; auditing does not rewrite it."
        },
        {
          "key": "alphabet",
          "use": "Distinct Unicode code points, first to last. Prefixes precede longer keys. This is an authored convention, not a locale sorting standard."
        },
        {
          "key": "ignored",
          "use": "Each literal code point is removed after case folding, from keys only. Nothing is silently trimmed or normalized."
        },
        {
          "key": "fold",
          "use": "Choose exact characters or ASCII-only uppercasing."
        },
        {
          "key": "priority",
          "use": "Select which authored part decides first."
        },
        {
          "key": "alternative",
          "use": "Compare the reverse priority without changing the current model."
        },
        {
          "key": "ruleDisclosure",
          "use": "Authored text, copied as entered into both-language packets. It is not auto-translated or checked for truth. Blank withholds reader packets. Private keys and audit are never added to them."
        }
      ],
      "rules": [
        "Validate a complete 2–40-record permutation; never omit problematic names.",
        "Keep display names distinct from authored primary/secondary filing parts; do not infer a name split or reading.",
        "Use an explicit code-point alphabet, optional ASCII a–z folding and explicitly ignored characters. No Unicode normalization or locale collation.",
        "Compare keys lexicographically with shorter prefixes first and second part only after first-part equality.",
        "Equal two-part keys remain an unordered block; stable ID and printed order never become hidden tiebreaks.",
        "Enumerate every inverted pair and its decisive component, preserving the original printed prop.",
        "Compare the reverse part priority as a separate hypothesis, not an applied revision or an exhaustive explanation search.",
        "Reader packets include only exact authored note and printed labels; private keys, IDs and solution witnesses are omitted. Blank notes withhold packets. Other exports remain private."
      ],
      "requiredData": [
        {
          "description": "Original fictional costume-rack labels and two-part key fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Author-supplied alphabet and filing convention, without a cultural or historical authority claim",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate a complete 2–40-record permutation; never omit problematic names.",
        "Keep display names distinct from authored primary/secondary filing parts; do not infer a name split or reading.",
        "Use an explicit code-point alphabet, optional ASCII a–z folding and explicitly ignored characters. No Unicode normalization or locale collation.",
        "Compare keys lexicographically with shorter prefixes first and second part only after first-part equality.",
        "Equal two-part keys remain an unordered block; stable ID and printed order never become hidden tiebreaks.",
        "Enumerate every inverted pair and its decisive component, preserving the original printed prop.",
        "Compare the reverse part priority as a separate hypothesis, not an applied revision or an exhaustive explanation search.",
        "Reader packets include only exact authored note and printed labels; private keys, IDs and solution witnesses are omitted. Blank notes withhold packets. Other exports remain private."
      ],
      "outputs": [
        "Exact per-part key derivation and removed-character trace",
        "Permitted ordered blocks, tie ranges and all inverted-pair witnesses",
        "Current and alternative compatibility with distinct copy/compare/favorite records",
        "Full private audit and separate reader worksheets with no solution keys"
      ],
      "capabilities": [
        "Diagnose nonadjacent inversions and unresolved equal-key positions without inventing a unique culprit.",
        "Test a counter-explanation using a reversed part priority and prepare a separate reader-facing prop without private solution fields."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is to establish whether the order of a visible name prop supports a deduction. This needs a complete permutation, explicit filing parts and character ranks, key derivation, all inversion witnesses and tie ranges. Suspect resemblance checks do not define ordered keys; anagrams conserve character inventories and acrostics extract line positions rather than compare pairwise filing order.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "suspect-name-roster",
          "difference": "The suspect roster compares authored names and clue thresholds. This tool compares the printed permutation against lexicographic two-part keys, exposes nonadjacent inversion witnesses and tie blocks, calculates a specific alternative rule and exports a reader prop separately from the private solution. These are different decisions, not a sorting style added to the same name-generation task."
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-order-clue",
          "score": 0.17083333333333334,
          "sharedProfile": true,
          "difference": "Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction. versus Establish the convention before making a reversal meaningful; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction. versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-missing-name-record-clue",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction. versus Distinguish absent evidence from evidence of absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A filing violation is evidence about a convention, not proof of a unique person’s intent.",
        "outline": [
          "What the visible prop promises",
          "An invented puppet troupe costume-rack conflict",
          "Reconstruct all printed records and all pairwise witnesses",
          "Declare exact key derivation and unresolved ties",
          "Test a competing priority and the reader’s available rule",
          "Keep the private solution apart from a rehearsal handout",
          "Review changed names and the consequence for relationships"
        ],
        "story": "Before a puppet performance, Cira blames Aven for the changed rack because family-first order is violated. Bela identifies an alternative given-first explanation. The troupe checks actual costumes before performing, then asks what instructions the assistant received.",
        "storyAnalysis": "Renaming Aven to Zerin while keeping Reed preserves family-first placement but can destroy the given-first explanation. Changing Reed to Alder affects the other rule too. Correcting the prop does not automatically repair the accusation.",
        "evidence": "Original complete EN/JA guides, original costume-rack scene and rename counterfactual, FILE-01–19, FILE-HTML and 25 recorded actual browser checks. No external culture, demand or audience-study claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/filing.md",
        "localizedBodies": {
          "en": "content/en/filing.md",
          "ja": "content/ja/filing.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default prop has three primary-first inversion witnesses and zero under secondary-first.",
        "Changing priority, filing keys or character order changes actual results; display-only edits do not silently alter keys.",
        "Tied keys retain separate records and permitted ranges with no hidden tiebreak.",
        "Unknown characters and contradictory rules conflict; missing or duplicate printed IDs never truncate the model.",
        "Reader packets omit keys/audit/IDs, preserve exact note, and disappear for a blank note.",
        "Actual copy, favorites/compare, export/project recovery and mobile/initial-HTML checks before counting."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:658",
      "profileSource": "data/profiles.json#mystery",
      "specBatch": "batch-09",
      "implementationDifficulty": {
        "level": "medium-high",
        "reason": "Exact Unicode boundaries, exhaustive pair witnesses and tie ranges, output privacy separation and original bilingual guide; no invented time estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "filing",
        "engineFiles": [
          "web/filing-order.mjs",
          "web/filing-tool.mjs",
          "web/filing-view.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/filing-order.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "records",
          "label": [
            "Names and authored filing parts · JSON",
            "名前と作者指定の照合形・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"aven\",\n    \"name\": \"Aven Reed\",\n    \"primary\": \"REED\",\n    \"secondary\": \"AVEN\"\n  },\n  {\n    \"id\": \"bela\",\n    \"name\": \"Bela Marsh\",\n    \"primary\": \"MARSH\",\n    \"secondary\": \"BELA\"\n  },\n  {\n    \"id\": \"cira\",\n    \"name\": \"Cira Ash\",\n    \"primary\": \"ASH\",\n    \"secondary\": \"CIRA\"\n  },\n  {\n    \"id\": \"daro\",\n    \"name\": \"Daro Vale\",\n    \"primary\": \"VALE\",\n    \"secondary\": \"DARO\"\n  }\n]",
          "help": [
            "2–40 records. id/name/primary/secondary. Declare the filing parts yourself; the tool does not parse names or guess readings. IDs start with an ASCII letter.",
            "2〜40件。id/name/primary/secondary。照合項目は作者が指定し、姓名の分割や読みは推測しません。IDは英字で始めます。"
          ],
          "maxLength": 60000
        },
        {
          "key": "printedOrder",
          "label": [
            "Order actually printed · JSON IDs",
            "実際に印刷した順序・JSONのID一覧"
          ],
          "type": "textarea",
          "default": "[\n  \"aven\",\n  \"bela\",\n  \"cira\",\n  \"daro\"\n]",
          "help": [
            "Every record ID once. This is the prop the reader sees; auditing does not rewrite it.",
            "全記録のIDを一度ずつ。読者に示す小道具の順序です。監査で入力を書き換えません。"
          ],
          "maxLength": 60000
        },
        {
          "key": "alphabet",
          "label": [
            "Explicit character order",
            "明示する文字の順序"
          ],
          "type": "text",
          "default": "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
          "help": [
            "Distinct Unicode code points, first to last. Prefixes precede longer keys. This is an authored convention, not a locale sorting standard.",
            "異なるUnicodeコードポイントを先頭から順に指定。同じ接頭部なら短いキーが先です。作者の規則であり、実在地域の標準ではありません。"
          ]
        },
        {
          "key": "ignored",
          "label": [
            "Characters deliberately ignored",
            "明示的に無視する文字"
          ],
          "type": "text",
          "default": " '-",
          "help": [
            "Each literal code point is removed after case folding, from keys only. Nothing is silently trimmed or normalized.",
            "各文字を大文字化の後で照合形だけから除きます。無断での空白除去や正規化はしません。"
          ]
        },
        {
          "key": "fold",
          "label": [
            "Case rule",
            "大文字小文字の規則"
          ],
          "type": "select",
          "default": "ascii-upper",
          "help": null,
          "options": [
            [
              "none",
              [
                "Exact characters",
                "文字をそのまま比較"
              ]
            ],
            [
              "ascii-upper",
              [
                "ASCII a–z → A–Z only",
                "ASCIIのa〜zだけA〜Zへ"
              ]
            ]
          ]
        },
        {
          "key": "priority",
          "label": [
            "First filing part",
            "先に比較する項目"
          ],
          "type": "select",
          "default": "primary",
          "help": null,
          "options": [
            [
              "primary",
              [
                "primary, then secondary",
                "primaryの後にsecondary"
              ]
            ],
            [
              "secondary",
              [
                "secondary, then primary",
                "secondaryの後にprimary"
              ]
            ]
          ]
        },
        {
          "key": "alternative",
          "label": [
            "Compare reversed key priority",
            "項目の優先順を逆にした案を比較"
          ],
          "type": "select",
          "default": "on",
          "help": null,
          "options": [
            [
              "on",
              [
                "Compute separate alternative",
                "別案として計算"
              ]
            ],
            [
              "off",
              [
                "Current rule only",
                "現在の規則だけ"
              ]
            ]
          ]
        },
        {
          "key": "ruleDisclosure",
          "label": [
            "Exact note for the reader worksheet",
            "読者用資料に載せる説明そのもの"
          ],
          "type": "textarea",
          "default": "Fictional costume rack: entries should be filed by the family part, then the given part. Compare A–Z; ignore spaces, apostrophes and hyphens. The four printed names appear in the order shown. Consider whether a different convention could explain the order.",
          "help": [
            "Authored text, copied as entered into both-language packets. It is not auto-translated or checked for truth. Blank withholds reader packets. Private keys and audit are never added to them.",
            "作者が書く文章です。両言語の資料へ入力のまま複写し、自動翻訳や正しさの認証はしません。空欄なら読者用資料を出さず、非公開キーと監査を混ぜません。"
          ],
          "maxLength": 4000
        }
      ]
    },
    {
      "id": "nw-duplicate-identity-mystery",
      "slug": "duplicate-identity-mystery",
      "name": "Duplicate identity mystery",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/duplicate-identity-mystery/",
        "ja": "/ja/tools/duplicate-identity-mystery/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Track two records that may refer to one person without prematurely merging",
      "task": "Track two records that may refer to one person without prematurely merging",
      "searchIntent": {
        "primary": "Complete the task: Track two records that may refer to one person without prematurely merging",
        "queryHypothesis": "duplicate identity mystery",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track two records that may refer to one person without prematurely merging?",
        "When should duplicate identity mystery be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track two records that may refer to one person without prematurely merging",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track two records that may refer to one person without prematurely merging. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.20833333333333334,
          "sharedProfile": false,
          "difference": "Track two records that may refer to one person without prematurely merging versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.11333333333333333,
          "sharedProfile": false,
          "difference": "Track two records that may refer to one person without prematurely merging versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-mystery-reveal-name-recap",
          "score": 0.110625,
          "sharedProfile": true,
          "difference": "Track two records that may refer to one person without prematurely merging versus Explain the identity solution without contradicting earlier references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track two records that may refer to one person without prematurely merging",
        "outline": [
          "Explain the specific decision: Track two records that may refer to one person without prematurely merging",
          "Define the applicable contract and limits for Duplicate identity mystery",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track two records that may refer to one person without prematurely merging; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track two records that may refer to one person without prematurely merging",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:659",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-same-name-suspects",
      "slug": "same-name-suspects",
      "name": "Same name suspects",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/same-name-suspects/",
        "ja": "/ja/tools/same-name-suspects/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Preserve deliberate ambiguity with contextual disambiguation",
      "task": "Preserve deliberate ambiguity with contextual disambiguation",
      "searchIntent": {
        "primary": "Complete the task: Preserve deliberate ambiguity with contextual disambiguation",
        "queryHypothesis": "same name suspects",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve deliberate ambiguity with contextual disambiguation?",
        "When should same name suspects be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve deliberate ambiguity with contextual disambiguation",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve deliberate ambiguity with contextual disambiguation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-same-writing-different-reading",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Preserve deliberate ambiguity with contextual disambiguation versus Require explicit readings and ambiguity disclosures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estrangement-address-reversal",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Preserve deliberate ambiguity with contextual disambiguation versus Restore distance through deliberate naming changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-ambiguity-budget",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Preserve deliberate ambiguity with contextual disambiguation versus Track newly introduced collisions and intentional ambiguity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve deliberate ambiguity with contextual disambiguation",
        "outline": [
          "Explain the specific decision: Preserve deliberate ambiguity with contextual disambiguation",
          "Define the applicable contract and limits for Same name suspects",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve deliberate ambiguity with contextual disambiguation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve deliberate ambiguity with contextual disambiguation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:660",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-maiden-surname-reveal-fiction",
      "slug": "maiden-surname-reveal-fiction",
      "name": "Maiden surname reveal fiction",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/maiden-surname-reveal-fiction/",
        "ja": "/ja/tools/maiden-surname-reveal-fiction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Track documentary access and relationship knowledge without legal assumptions",
      "task": "Track documentary access and relationship knowledge without legal assumptions",
      "searchIntent": {
        "primary": "Complete the task: Track documentary access and relationship knowledge without legal assumptions",
        "queryHypothesis": "maiden surname reveal fiction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track documentary access and relationship knowledge without legal assumptions?",
        "When should maiden surname reveal fiction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track documentary access and relationship knowledge without legal assumptions",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track documentary access and relationship knowledge without legal assumptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-surname-construction",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Track documentary access and relationship knowledge without legal assumptions versus Build a family identifier with explicit inheritance assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Track documentary access and relationship knowledge without legal assumptions versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collaborative-fiction-name-proposal",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Track documentary access and relationship knowledge without legal assumptions versus Collect votes and reasons without presenting popularity as quality; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track documentary access and relationship knowledge without legal assumptions",
        "outline": [
          "Explain the specific decision: Track documentary access and relationship knowledge without legal assumptions",
          "Define the applicable contract and limits for Maiden surname reveal fiction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track documentary access and relationship knowledge without legal assumptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track documentary access and relationship knowledge without legal assumptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:661",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-alias-obituary-clue",
      "slug": "alias-obituary-clue",
      "name": "Alias obituary clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/alias-obituary-clue/",
        "ja": "/ja/tools/alias-obituary-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Reconcile dates, names and witnesses in fictional records",
      "task": "Reconcile dates, names and witnesses in fictional records",
      "searchIntent": {
        "primary": "Complete the task: Reconcile dates, names and witnesses in fictional records",
        "queryHypothesis": "alias obituary clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile dates, names and witnesses in fictional records?",
        "When should alias obituary clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile dates, names and witnesses in fictional records",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile dates, names and witnesses in fictional records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Reconcile dates, names and witnesses in fictional records versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Reconcile dates, names and witnesses in fictional records versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Reconcile dates, names and witnesses in fictional records versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile dates, names and witnesses in fictional records",
        "outline": [
          "Explain the specific decision: Reconcile dates, names and witnesses in fictional records",
          "Define the applicable contract and limits for Alias obituary clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile dates, names and witnesses in fictional records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile dates, names and witnesses in fictional records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:662",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-letter-salutation-clue",
      "slug": "letter-salutation-clue",
      "name": "Letter salutation clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/letter-salutation-clue/",
        "ja": "/ja/tools/letter-salutation-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Make an address form reveal a specific relationship",
      "task": "Make an address form reveal a specific relationship",
      "searchIntent": {
        "primary": "Complete the task: Make an address form reveal a specific relationship",
        "queryHypothesis": "letter salutation clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make an address form reveal a specific relationship?",
        "When should letter salutation clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make an address form reveal a specific relationship",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make an address form reveal a specific relationship. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-reconciliation-name-return",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Make an address form reveal a specific relationship versus Make the return of a form of address legible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-gives-another-a-name",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Make an address form reveal a specific relationship versus Make consent, power and relationship explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-shares-secret-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Make an address form reveal a specific relationship versus Make disclosure a meaningful relationship choice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make an address form reveal a specific relationship",
        "outline": [
          "Explain the specific decision: Make an address form reveal a specific relationship",
          "Define the applicable contract and limits for Letter salutation clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make an address form reveal a specific relationship; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make an address form reveal a specific relationship",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:663",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-private-nickname-clue",
      "slug": "private-nickname-clue",
      "name": "Private nickname clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/private-nickname-clue/",
        "ja": "/ja/tools/private-nickname-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Track the restricted group who could know the name",
      "task": "Track the restricted group who could know the name",
      "searchIntent": {
        "primary": "Complete the task: Track the restricted group who could know the name",
        "queryHypothesis": "private nickname clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track the restricted group who could know the name?",
        "When should private nickname clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track the restricted group who could know the name",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track the restricted group who could know the name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alien-human-nickname-negotiation",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Track the restricted group who could know the name versus Track who chooses a translated name and who accepts it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-bargain-witness-ledger",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track the restricted group who could know the name versus Record who witnessed a pact and which terms they know; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Track the restricted group who could know the name versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track the restricted group who could know the name",
        "outline": [
          "Explain the specific decision: Track the restricted group who could know the name",
          "Define the applicable contract and limits for Private nickname clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track the restricted group who could know the name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track the restricted group who could know the name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:664",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-wrong-honorific-clue",
      "slug": "wrong-honorific-clue",
      "name": "Wrong honorific clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/wrong-honorific-clue/",
        "ja": "/ja/tools/wrong-honorific-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Ground the clue in an established in story convention",
      "task": "Ground the clue in an established in story convention",
      "searchIntent": {
        "primary": "Complete the task: Ground the clue in an established in story convention",
        "queryHypothesis": "wrong honorific clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to ground the clue in an established in story convention?",
        "When should wrong honorific clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Ground the clue in an established in story convention",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Ground the clue in an established in story convention. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-order-clue",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Ground the clue in an established in story convention versus Establish the convention before making a reversal meaningful; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Ground the clue in an established in story convention versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-accessibility",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Ground the clue in an established in story convention versus Provide a fair alternative when a clue relies on visual or audio distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Ground the clue in an established in story convention",
        "outline": [
          "Explain the specific decision: Ground the clue in an established in story convention",
          "Define the applicable contract and limits for Wrong honorific clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Ground the clue in an established in story convention; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Ground the clue in an established in story convention",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:665",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-outdated-title-clue",
      "slug": "outdated-title-clue",
      "name": "Outdated title clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/outdated-title-clue/",
        "ja": "/ja/tools/outdated-title-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Link an obsolete form to what the speaker knows about time",
      "task": "Link an obsolete form to what the speaker knows about time",
      "searchIntent": {
        "primary": "Complete the task: Link an obsolete form to what the speaker knows about time",
        "queryHypothesis": "outdated title clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link an obsolete form to what the speaker knows about time?",
        "When should outdated title clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link an obsolete form to what the speaker knows about time",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link an obsolete form to what the speaker knows about time. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-title-forgery-clue",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Link an obsolete form to what the speaker knows about time versus Design verifiable fictional inconsistencies in a claimed title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-letter-salutation-clue",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Link an obsolete form to what the speaker knows about time versus Make an address form reveal a specific relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-royal-title-address-matrix",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Link an obsolete form to what the speaker knows about time versus Resolve forms by office, speaker and political recognition; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link an obsolete form to what the speaker knows about time",
        "outline": [
          "Explain the specific decision: Link an obsolete form to what the speaker knows about time",
          "Define the applicable contract and limits for Outdated title clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link an obsolete form to what the speaker knows about time; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link an obsolete form to what the speaker knows about time",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:666",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-pronunciation-witness-clue",
      "slug": "pronunciation-witness-clue",
      "name": "Pronunciation witness clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/pronunciation-witness-clue/",
        "ja": "/ja/tools/pronunciation-witness-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Use verified pronunciations and avoid impossible sound deductions",
      "task": "Use verified pronunciations and avoid impossible sound deductions",
      "searchIntent": {
        "primary": "Complete the task: Use verified pronunciations and avoid impossible sound deductions",
        "queryHypothesis": "pronunciation witness clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to use verified pronunciations and avoid impossible sound deductions?",
        "When should pronunciation witness clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Use verified pronunciations and avoid impossible sound deductions",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Use verified pronunciations and avoid impossible sound deductions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Use verified pronunciations and avoid impossible sound deductions versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spelling-variant-witness-clue",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Use verified pronunciations and avoid impossible sound deductions versus Separate meaningful discrepancies from ordinary transcription variation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-pronunciation-metadata",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Use verified pronunciations and avoid impossible sound deductions versus Export approved pronunciations with dialogue assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Use verified pronunciations and avoid impossible sound deductions",
        "outline": [
          "Explain the specific decision: Use verified pronunciations and avoid impossible sound deductions",
          "Define the applicable contract and limits for Pronunciation witness clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Use verified pronunciations and avoid impossible sound deductions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Use verified pronunciations and avoid impossible sound deductions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:667",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-spelling-variant-witness-clue",
      "slug": "spelling-variant-witness-clue",
      "name": "Spelling variant witness clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/spelling-variant-witness-clue/",
        "ja": "/ja/tools/spelling-variant-witness-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Separate meaningful discrepancies from ordinary transcription variation",
      "task": "Separate meaningful discrepancies from ordinary transcription variation",
      "searchIntent": {
        "primary": "Complete the task: Separate meaningful discrepancies from ordinary transcription variation",
        "queryHypothesis": "spelling variant witness clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate meaningful discrepancies from ordinary transcription variation?",
        "When should spelling variant witness clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate meaningful discrepancies from ordinary transcription variation",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate meaningful discrepancies from ordinary transcription variation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pronunciation-witness-clue",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Separate meaningful discrepancies from ordinary transcription variation versus Use verified pronunciations and avoid impossible sound deductions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-order-clue",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Separate meaningful discrepancies from ordinary transcription variation versus Establish the convention before making a reversal meaningful; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-shares-secret-name",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Separate meaningful discrepancies from ordinary transcription variation versus Make disclosure a meaningful relationship choice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate meaningful discrepancies from ordinary transcription variation",
        "outline": [
          "Explain the specific decision: Separate meaningful discrepancies from ordinary transcription variation",
          "Define the applicable contract and limits for Spelling variant witness clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate meaningful discrepancies from ordinary transcription variation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate meaningful discrepancies from ordinary transcription variation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:668",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-handwritten-name-ambiguity",
      "slug": "handwritten-name-ambiguity",
      "name": "Handwritten name ambiguity",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/handwritten-name-ambiguity/",
        "ja": "/ja/tools/handwritten-name-ambiguity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Define visible alternatives with an actual prop example",
      "task": "Define visible alternatives with an actual prop example",
      "searchIntent": {
        "primary": "Complete the task: Define visible alternatives with an actual prop example",
        "queryHypothesis": "handwritten name ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define visible alternatives with an actual prop example?",
        "When should handwritten name ambiguity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define visible alternatives with an actual prop example",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define visible alternatives with an actual prop example. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-handwritten-prop",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Define visible alternatives with an actual prop example versus Keep prop spelling, reading and plot knowledge synchronized; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-handwritten-note-clue",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Define visible alternatives with an actual prop example versus Make a name based clue visible and linguistically reviewed; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Define visible alternatives with an actual prop example versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define visible alternatives with an actual prop example",
        "outline": [
          "Explain the specific decision: Define visible alternatives with an actual prop example",
          "Define the applicable contract and limits for Handwritten name ambiguity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define visible alternatives with an actual prop example; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define visible alternatives with an actual prop example",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:669",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-name-order-clue",
      "slug": "name-order-clue",
      "name": "Name order clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-order-clue/",
        "ja": "/ja/tools/name-order-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Establish the convention before making a reversal meaningful",
      "task": "Establish the convention before making a reversal meaningful",
      "searchIntent": {
        "primary": "Complete the task: Establish the convention before making a reversal meaningful",
        "queryHypothesis": "name order clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to establish the convention before making a reversal meaningful?",
        "When should name order clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Establish the convention before making a reversal meaningful",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Establish the convention before making a reversal meaningful. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-misfiled-name-clue",
          "score": 0.17083333333333334,
          "sharedProfile": true,
          "difference": "Establish the convention before making a reversal meaningful versus Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wrong-honorific-clue",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Establish the convention before making a reversal meaningful versus Ground the clue in an established in story convention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spelling-variant-witness-clue",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Establish the convention before making a reversal meaningful versus Separate meaningful discrepancies from ordinary transcription variation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Establish the convention before making a reversal meaningful",
        "outline": [
          "Explain the specific decision: Establish the convention before making a reversal meaningful",
          "Define the applicable contract and limits for Name order clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Establish the convention before making a reversal meaningful; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Establish the convention before making a reversal meaningful",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:670",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-translated-name-clue",
      "slug": "translated-name-clue",
      "name": "Translated name clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/translated-name-clue/",
        "ja": "/ja/tools/translated-name-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Require language evidence accessible to the reader",
      "task": "Require language evidence accessible to the reader",
      "searchIntent": {
        "primary": "Complete the task: Require language evidence accessible to the reader",
        "queryHypothesis": "translated name clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require language evidence accessible to the reader?",
        "When should translated name clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require language evidence accessible to the reader",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require language evidence accessible to the reader. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Require language evidence accessible to the reader versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-missing-name-record-clue",
          "score": 0.19791666666666666,
          "sharedProfile": true,
          "difference": "Require language evidence accessible to the reader versus Distinguish absent evidence from evidence of absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Require language evidence accessible to the reader versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require language evidence accessible to the reader",
        "outline": [
          "Explain the specific decision: Require language evidence accessible to the reader",
          "Define the applicable contract and limits for Translated name clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require language evidence accessible to the reader; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require language evidence accessible to the reader",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:671",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-fictional-genealogy-clue",
      "slug": "fictional-genealogy-clue",
      "name": "Fictional genealogy clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/fictional-genealogy-clue/",
        "ja": "/ja/tools/fictional-genealogy-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Check name evidence against a relationship graph and dated records",
      "task": "Check name evidence against a relationship graph and dated records",
      "searchIntent": {
        "primary": "Complete the task: Check name evidence against a relationship graph and dated records",
        "queryHypothesis": "fictional genealogy clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check name evidence against a relationship graph and dated records?",
        "When should fictional genealogy clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check name evidence against a relationship graph and dated records",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check name evidence against a relationship graph and dated records. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-missing-name-record-clue",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Check name evidence against a relationship graph and dated records versus Distinguish absent evidence from evidence of absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-translated-name-clue",
          "score": 0.17575757575757575,
          "sharedProfile": true,
          "difference": "Check name evidence against a relationship graph and dated records versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Check name evidence against a relationship graph and dated records versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check name evidence against a relationship graph and dated records",
        "outline": [
          "Explain the specific decision: Check name evidence against a relationship graph and dated records",
          "Define the applicable contract and limits for Fictional genealogy clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check name evidence against a relationship graph and dated records; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check name evidence against a relationship graph and dated records",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:672",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-regnal-number-clue",
      "slug": "regnal-number-clue",
      "name": "Regnal number clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/regnal-number-clue/",
        "ja": "/ja/tools/regnal-number-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Base a deduction on a disclosed fictional succession system",
      "task": "Base a deduction on a disclosed fictional succession system",
      "searchIntent": {
        "primary": "Complete the task: Base a deduction on a disclosed fictional succession system",
        "queryHypothesis": "regnal number clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to base a deduction on a disclosed fictional succession system?",
        "When should regnal number clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Base a deduction on a disclosed fictional succession system",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Base a deduction on a disclosed fictional succession system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-misfiled-name-clue",
          "score": 0.11458333333333333,
          "sharedProfile": true,
          "difference": "Base a deduction on a disclosed fictional succession system versus Audit a printed name index against an explicitly authored filing convention, enumerate all inverted pairs and unresolved equal-key blocks, and compare a competing key priority before designing the deduction.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-regnal-numbering-consistency",
          "score": 0.10421052631578948,
          "sharedProfile": false,
          "difference": "Base a deduction on a disclosed fictional succession system versus Assign and audit fictional reign ordinals across declared succession series, exact name-equivalence keys, reaccessions and unresolved inclusion decisions.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Base a deduction on a disclosed fictional succession system versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Base a deduction on a disclosed fictional succession system",
        "outline": [
          "Explain the specific decision: Base a deduction on a disclosed fictional succession system",
          "Define the applicable contract and limits for Regnal number clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Base a deduction on a disclosed fictional succession system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Base a deduction on a disclosed fictional succession system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:673",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-name-red-herring-control",
      "slug": "name-red-herring-control",
      "name": "Name red herring control",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-red-herring-control/",
        "ja": "/ja/tools/name-red-herring-control/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Show why a false association is plausible but not proof",
      "task": "Show why a false association is plausible but not proof",
      "searchIntent": {
        "primary": "Complete the task: Show why a false association is plausible but not proof",
        "queryHypothesis": "name red herring control",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show why a false association is plausible but not proof?",
        "When should name red herring control be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show why a false association is plausible but not proof",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show why a false association is plausible but not proof. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-translation-versus-retention",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Show why a false association is plausible but not proof versus Record why a meaningful name is translated or retained; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-mishearing",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Show why a false association is plausible but not proof versus Design recoverable mishearings that do not depend on false phonetics; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-ruby-layout",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Show why a false association is plausible but not proof versus Prepare an exact segmented name-and-ruby association and compare its rendered horizontal or vertical proof with a declared frame without inferring a reading.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show why a false association is plausible but not proof",
        "outline": [
          "Explain the specific decision: Show why a false association is plausible but not proof",
          "Define the applicable contract and limits for Name red herring control",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show why a false association is plausible but not proof; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show why a false association is plausible but not proof",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:674",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-character-list-spoiler-test",
      "slug": "character-list-spoiler-test",
      "name": "Character list spoiler test",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/character-list-spoiler-test/",
        "ja": "/ja/tools/character-list-spoiler-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Compare cast list entries against mystery disclosure timing",
      "task": "Compare cast list entries against mystery disclosure timing",
      "searchIntent": {
        "primary": "Complete the task: Compare cast list entries against mystery disclosure timing",
        "queryHypothesis": "character list spoiler test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare cast list entries against mystery disclosure timing?",
        "When should character list spoiler test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare cast list entries against mystery disclosure timing",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare cast list entries against mystery disclosure timing. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Compare cast list entries against mystery disclosure timing versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-new-cast-collision",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare cast list entries against mystery disclosure timing versus Compare a proposed cast against previous installments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-spelling-dictation-test",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare cast list entries against mystery disclosure timing versus Compare intended spelling against listener transcriptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare cast list entries against mystery disclosure timing",
        "outline": [
          "Explain the specific decision: Compare cast list entries against mystery disclosure timing",
          "Define the applicable contract and limits for Character list spoiler test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare cast list entries against mystery disclosure timing; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare cast list entries against mystery disclosure timing",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:675",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-detective-notebook-identity-map",
      "slug": "detective-notebook-identity-map",
      "name": "Detective notebook identity map",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/detective-notebook-identity-map/",
        "ja": "/ja/tools/detective-notebook-identity-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Separate hypothesis, testimony and corroborated identity",
      "task": "Separate hypothesis, testimony and corroborated identity",
      "searchIntent": {
        "primary": "Complete the task: Separate hypothesis, testimony and corroborated identity",
        "queryHypothesis": "detective notebook identity map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate hypothesis, testimony and corroborated identity?",
        "When should detective notebook identity map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate hypothesis, testimony and corroborated identity",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate hypothesis, testimony and corroborated identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.2095238095238095,
          "sharedProfile": false,
          "difference": "Separate hypothesis, testimony and corroborated identity versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unreliable-name-attribution",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate hypothesis, testimony and corroborated identity versus Separate a narrator's claim from corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-live-roleplay-identity-badges",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Separate hypothesis, testimony and corroborated identity versus Separate player safety information from fictional identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate hypothesis, testimony and corroborated identity",
        "outline": [
          "Explain the specific decision: Separate hypothesis, testimony and corroborated identity",
          "Define the applicable contract and limits for Detective notebook identity map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate hypothesis, testimony and corroborated identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate hypothesis, testimony and corroborated identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:676",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-witness-name-uncertainty",
      "slug": "witness-name-uncertainty",
      "name": "Witness name uncertainty",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/witness-name-uncertainty/",
        "ja": "/ja/tools/witness-name-uncertainty/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Preserve unknown, misheard and confirmed states explicitly",
      "task": "Preserve unknown, misheard and confirmed states explicitly",
      "searchIntent": {
        "primary": "Complete the task: Preserve unknown, misheard and confirmed states explicitly",
        "queryHypothesis": "witness name uncertainty",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve unknown, misheard and confirmed states explicitly?",
        "When should witness name uncertainty be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve unknown, misheard and confirmed states explicitly",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve unknown, misheard and confirmed states explicitly. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-naming-uncertainty-map",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Preserve unknown, misheard and confirmed states explicitly versus Identify missing research before committing a culturally situated name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-archive-name-uncertainty",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve unknown, misheard and confirmed states explicitly versus Store competing readings and confidence with source images; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pronunciation-uncertainty",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve unknown, misheard and confirmed states explicitly versus Present known limits instead of confident reconstructed audio; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve unknown, misheard and confirmed states explicitly",
        "outline": [
          "Explain the specific decision: Preserve unknown, misheard and confirmed states explicitly",
          "Define the applicable contract and limits for Witness name uncertainty",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve unknown, misheard and confirmed states explicitly; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve unknown, misheard and confirmed states explicitly",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:677",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-pseudonymous-manuscript-mystery",
      "slug": "pseudonymous-manuscript-mystery",
      "name": "Pseudonymous manuscript mystery",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/pseudonymous-manuscript-mystery/",
        "ja": "/ja/tools/pseudonymous-manuscript-mystery/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Track author identity evidence and competing interpretations",
      "task": "Track author identity evidence and competing interpretations",
      "searchIntent": {
        "primary": "Complete the task: Track author identity evidence and competing interpretations",
        "queryHypothesis": "pseudonymous manuscript mystery",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track author identity evidence and competing interpretations?",
        "When should pseudonymous manuscript mystery be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track author identity evidence and competing interpretations",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track author identity evidence and competing interpretations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-confession-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track author identity evidence and competing interpretations versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-pen-name-fiction",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track author identity evidence and competing interpretations versus Track multiple fictional holders of a famous author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track author identity evidence and competing interpretations versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track author identity evidence and competing interpretations",
        "outline": [
          "Explain the specific decision: Track author identity evidence and competing interpretations",
          "Define the applicable contract and limits for Pseudonymous manuscript mystery",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track author identity evidence and competing interpretations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track author identity evidence and competing interpretations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:678",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-forged-byline-clue",
      "slug": "forged-byline-clue",
      "name": "Forged byline clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/forged-byline-clue/",
        "ja": "/ja/tools/forged-byline-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Compare fictional attribution patterns without asserting real authentication expertise",
      "task": "Compare fictional attribution patterns without asserting real authentication expertise",
      "searchIntent": {
        "primary": "Complete the task: Compare fictional attribution patterns without asserting real authentication expertise",
        "queryHypothesis": "forged byline clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare fictional attribution patterns without asserting real authentication expertise?",
        "When should forged byline clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare fictional attribution patterns without asserting real authentication expertise",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare fictional attribution patterns without asserting real authentication expertise. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-saint-like-fictional-title",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Compare fictional attribution patterns without asserting real authentication expertise versus Model veneration within invented religion without asserting real canonization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-publication-byline",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Compare fictional attribution patterns without asserting real authentication expertise versus Compare anonymity language and reader expectations without privacy guarantees; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-author-byline",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Compare fictional attribution patterns without asserting real authentication expertise versus Coordinate English and Japanese forms without counting two tools; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare fictional attribution patterns without asserting real authentication expertise",
        "outline": [
          "Explain the specific decision: Compare fictional attribution patterns without asserting real authentication expertise",
          "Define the applicable contract and limits for Forged byline clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare fictional attribution patterns without asserting real authentication expertise; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare fictional attribution patterns without asserting real authentication expertise",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:679",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-stolen-family-name-motive",
      "slug": "stolen-family-name-motive",
      "name": "Stolen family name motive",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/stolen-family-name-motive/",
        "ja": "/ja/tools/stolen-family-name-motive/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Connect naming conflict to character stakes rather than a puzzle alone",
      "task": "Connect naming conflict to character stakes rather than a puzzle alone",
      "searchIntent": {
        "primary": "Complete the task: Connect naming conflict to character stakes rather than a puzzle alone",
        "queryHypothesis": "stolen family name motive",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect naming conflict to character stakes rather than a puzzle alone?",
        "When should stolen family name motive be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect naming conflict to character stakes rather than a puzzle alone",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect naming conflict to character stakes rather than a puzzle alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-nickname-attestation",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Connect naming conflict to character stakes rather than a puzzle alone versus Require usage evidence rather than modern connotation alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-conflict-outline",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Connect naming conflict to character stakes rather than a puzzle alone versus Build a conflict from specific naming authority and character stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Connect naming conflict to character stakes rather than a puzzle alone versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect naming conflict to character stakes rather than a puzzle alone",
        "outline": [
          "Explain the specific decision: Connect naming conflict to character stakes rather than a puzzle alone",
          "Define the applicable contract and limits for Stolen family name motive",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect naming conflict to character stakes rather than a puzzle alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect naming conflict to character stakes rather than a puzzle alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:680",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-missing-name-record-clue",
      "slug": "missing-name-record-clue",
      "name": "Missing name record clue",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/missing-name-record-clue/",
        "ja": "/ja/tools/missing-name-record-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Distinguish absent evidence from evidence of absence",
      "task": "Distinguish absent evidence from evidence of absence",
      "searchIntent": {
        "primary": "Complete the task: Distinguish absent evidence from evidence of absence",
        "queryHypothesis": "missing name record clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish absent evidence from evidence of absence?",
        "When should missing name record clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish absent evidence from evidence of absence",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish absent evidence from evidence of absence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-translated-name-clue",
          "score": 0.19791666666666666,
          "sharedProfile": true,
          "difference": "Distinguish absent evidence from evidence of absence versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.18166666666666664,
          "sharedProfile": true,
          "difference": "Distinguish absent evidence from evidence of absence versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-anagram-clue",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Distinguish absent evidence from evidence of absence versus Rebuild a name puzzle with solvability evidence in each language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish absent evidence from evidence of absence",
        "outline": [
          "Explain the specific decision: Distinguish absent evidence from evidence of absence",
          "Define the applicable contract and limits for Missing name record clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish absent evidence from evidence of absence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish absent evidence from evidence of absence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:681",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-name-clue-accessibility",
      "slug": "name-clue-accessibility",
      "name": "Name clue accessibility",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-clue-accessibility/",
        "ja": "/ja/tools/name-clue-accessibility/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Provide a fair alternative when a clue relies on visual or audio distinction",
      "task": "Provide a fair alternative when a clue relies on visual or audio distinction",
      "searchIntent": {
        "primary": "Complete the task: Provide a fair alternative when a clue relies on visual or audio distinction",
        "queryHypothesis": "name clue accessibility",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide a fair alternative when a clue relies on visual or audio distinction?",
        "When should name clue accessibility be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide a fair alternative when a clue relies on visual or audio distinction",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide a fair alternative when a clue relies on visual or audio distinction. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-accessibility-labels",
          "score": 0.1875,
          "sharedProfile": false,
          "difference": "Provide a fair alternative when a clue relies on visual or audio distinction versus Provide readable labels alongside compact visual names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Provide a fair alternative when a clue relies on visual or audio distinction versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wrong-honorific-clue",
          "score": 0.1375,
          "sharedProfile": true,
          "difference": "Provide a fair alternative when a clue relies on visual or audio distinction versus Ground the clue in an established in story convention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide a fair alternative when a clue relies on visual or audio distinction",
        "outline": [
          "Explain the specific decision: Provide a fair alternative when a clue relies on visual or audio distinction",
          "Define the applicable contract and limits for Name clue accessibility",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide a fair alternative when a clue relies on visual or audio distinction; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide a fair alternative when a clue relies on visual or audio distinction",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:682",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-puzzle-name-solution-validation",
      "slug": "puzzle-name-solution-validation",
      "name": "Puzzle name solution validation",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/puzzle-name-solution-validation/",
        "ja": "/ja/tools/puzzle-name-solution-validation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fiction, comic and game authors constructing a finite name-changing puzzle with explicitly visible endpoints.",
      "scenario": "A museum exhibit asks visitors to connect LINA to MORA through LIRA. Two siblings supply different three-move solutions, so the curator changes a single-answer invitation to one that acknowledges both routes.",
      "task": "Design and validate shortest single-code-point substitution walks through an authored finite form pool, count all shortest alternatives, require ordered first-arrival checkpoints and separate reader exercises from private solution proofs.",
      "searchIntent": {
        "primary": "Design and verify a finite name-substitution puzzle, including shortest alternate solutions and checkpoints.",
        "queryHypothesis": "name word ladder puzzle shortest solution",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Does showing one route prove that a name puzzle has one shortest answer?",
        "Why can an ordered-checkpoint walk revisit an earlier form?",
        "How can a legal proposed route still fail a shortest-path task?"
      ],
      "inputs": [
        {
          "key": "pool",
          "type": "textarea",
          "purpose": "2–600 authored forms, each 2–24 Unicode code points and ≤48 UTF-16 units. No surrounding whitespace or control characters. Blank lines are ignored; different lengths are explicitly excluded from this puzzle. These are fictional fixtures, not attested names."
        },
        {
          "key": "start",
          "type": "text",
          "purpose": "Declared first form that must resolve to the supplied pool."
        },
        {
          "key": "target",
          "type": "text",
          "purpose": "Both endpoints must resolve to different listed forms of equal comparison length. This puzzle exposes both ends; it does not prove that an unstated identity clue has a unique interpretation."
        },
        {
          "key": "policy",
          "type": "select",
          "purpose": "No Unicode normalization, pronunciation inference or transliteration. Raw spellings remain visible; collisions under the chosen policy are rejected. A code point is not necessarily a visible grapheme."
        },
        {
          "key": "checkpoints",
          "type": "textarea",
          "purpose": "0–6 distinct listed forms, one per line, excluding endpoints. First arrivals must follow this order; later revisits are allowed. A future checkpoint and the target cannot be entered early. This searches walks, not certified no-repeat paths."
        },
        {
          "key": "blocked",
          "type": "textarea",
          "purpose": "0–100 listed forms. Do not block endpoints or checkpoints. The report preserves excluded entries so a smaller pool cannot masquerade as the original scope."
        },
        {
          "key": "maxMoves",
          "type": "number",
          "purpose": "The engine computes the global shortest distance in the declared finite state graph. A route beyond this ceiling is reported as over budget, not unreachable."
        },
        {
          "key": "sampleLimit",
          "type": "number",
          "purpose": "Only limits displayed witnesses. All shortest walks are counted exactly as a decimal string; a truncated sample never means there is only one answer."
        },
        {
          "key": "attempt",
          "type": "textarea",
          "purpose": "Up to 61 forms, one per line. Inspect membership, one-substitution steps, checkpoint order, endpoints, budget and shortestness. An invalid attempt does not erase the separately proved puzzle witnesses."
        },
        {
          "key": "clue",
          "type": "textarea",
          "purpose": "Author the prompt, ≤1200 UTF-16 units. Generated rule disclosures and both endpoints accompany it in the reader sheet. The program does not interpret or certify your prose clue."
        },
        {
          "key": "storyUse",
          "type": "textarea",
          "purpose": "≤1200. Kept in private copying, favorites and audit; omitted from the reader exercise. Names and tile conventions are fictional, not cultural or etymological claims."
        }
      ],
      "rules": [
        "2–600 distinct authored forms, each 2–24 Unicode code points and ≤48 UTF-16 units. Exact or ASCII A–Z folding; preserve raw forms, reject colliding keys, report different-length and blocked exclusions.",
        "A move substitutes exactly one comparison code point. No insertion, deletion, reordering, pronunciation or etymology inference. Every witness exposes listed forms, comparison forms, one-based position and source/target code points.",
        "0–6 required checkpoints have ordered first arrivals; future checkpoints and target cannot be entered early. Revisiting a form after progress is allowed and disclosed. This is a shortest-walk model, not a no-repeat simple-path certificate.",
        "Finite state is a form plus checkpoint progress. Compute global shortest distance and exact BigInt shortest-walk count; display only 1–12 witnesses, never truncate the count. Distinguish unreachable from shortest exceeding the 1–60 move ceiling.",
        "Validate supplied attempts against membership, local edges, ordered progress, endpoints, ceiling and shortest distance. A failed or longer attempt does not erase independent feasible witnesses.",
        "Witness insertion into the attempt field guards current source context. Reader export appears only for feasible scope and contains both endpoints, eligible pool, public prompt and rules, excluding generated paths/counts, attempt and private story note. Authored prompt remains verbatim and needs spoiler checking."
      ],
      "requiredData": [
        {
          "description": "Original fictional museum name-tile pool and shortest-route fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied finite form pool, constraints, reader prompt, private story use and optional proposed route; no attested word/name corpus claim",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "2–600 distinct authored forms, each 2–24 Unicode code points and ≤48 UTF-16 units. Exact or ASCII A–Z folding; preserve raw forms, reject colliding keys, report different-length and blocked exclusions.",
        "A move substitutes exactly one comparison code point. No insertion, deletion, reordering, pronunciation or etymology inference. Every witness exposes listed forms, comparison forms, one-based position and source/target code points.",
        "0–6 required checkpoints have ordered first arrivals; future checkpoints and target cannot be entered early. Revisiting a form after progress is allowed and disclosed. This is a shortest-walk model, not a no-repeat simple-path certificate.",
        "Finite state is a form plus checkpoint progress. Compute global shortest distance and exact BigInt shortest-walk count; display only 1–12 witnesses, never truncate the count. Distinguish unreachable from shortest exceeding the 1–60 move ceiling.",
        "Validate supplied attempts against membership, local edges, ordered progress, endpoints, ceiling and shortest distance. A failed or longer attempt does not erase independent feasible witnesses.",
        "Witness insertion into the attempt field guards current source context. Reader export appears only for feasible scope and contains both endpoints, eligible pool, public prompt and rules, excluding generated paths/counts, attempt and private story note. Authored prompt remains verbatim and needs spoiler checking."
      ],
      "outputs": [
        "Global shortest distance, endpoint-difference lower bound, exact decimal shortest count, sample-truncation disclosure and finite visited-state bound.",
        "Stepwise witnessed routes with comparison-position edits, repeated-form disclosure and explicit pool exclusions.",
        "Attempt findings with raw-to-pool correspondence, local validity versus shortestness, private design/proof files and a public exercise with no automatically attached solutions."
      ],
      "capabilities": [
        "Count all shortest walks independently of witness samples under ordered checkpoint-progress states, including explicit revisits, unreachable and over-budget distinctions.",
        "Validate concrete proposed walks with per-step membership/edit/order/budget errors and a separate shortestness conclusion; populate a guarded current witness as an editable trial.",
        "Export a reader exercise separated from generated routes, counts, attempts and private story context while preserving its authored prompt literally."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Anagram tools compare character inventories; ordered extraction takes characters from rows or positions. This task instead constructs a finite adjacency graph, tracks checkpoint progress, computes exact shortest-walk counts independent of displayed samples, validates a supplied walk and produces a reader exercise without generated paths. A general all-puzzle validator would be unjustified; the candidate is redesigned around this concrete task.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "name-anagram-clue-designer",
          "difference": "The primary decision is whether a permitted sequence of local substitutions connects two declared names, with ordered intermediate obligations and shortest alternatives. Inventory equality or rearrangement cannot answer that question; neither can extracting ordered initials."
        }
      },
      "nearestTools": [
        {
          "id": "nw-game-name-import-validation",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Design and validate shortest single-code-point substitution walks through an authored finite form pool, count all shortest alternatives, require ordered first-arrival checkpoints and separate reader exercises from private solution proofs. versus Reject malformed datasets without silently dropping characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-translated-name-clue",
          "score": 0.04642857142857143,
          "sharedProfile": true,
          "difference": "Design and validate shortest single-code-point substitution walks through an authored finite form pool, count all shortest alternatives, require ordered first-arrival checkpoints and separate reader exercises from private solution proofs. versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.04482758620689655,
          "sharedProfile": false,
          "difference": "Design and validate shortest single-code-point substitution walks through an authored finite form pool, count all shortest alternatives, require ordered first-arrival checkpoints and separate reader exercises from private solution proofs. versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "The route and its alternatives are part of the clue: finite-pool shortestness must not be confused with one displayed sample, repeat-free rules or uniqueness of an unstated identity riddle.",
        "outline": [
          "A route as a naming clue",
          "Original museum exhibit and two equally short answers",
          "Declare a finite authored pool",
          "Read comparison positions and lower bounds",
          "Ordered checkpoint progress and honest revisits",
          "Separate global distance, total count and displayed witnesses",
          "Validate attempts without erasing existence proofs",
          "Reader exercise versus private solution handoffs"
        ],
        "story": "A conservator asks two siblings to prepare LINA-to-MORA paths through LIRA. Both use three moves in different position orders. The curator changes the exhibit’s one-answer card to invite another shortest route and credits both arrangements.",
        "storyAnalysis": "Replacing MORA with added MERA yields one three-move shortest path through LIRA in the revised finite pool. The exhibit invitation and the role of each contribution must change; a bare target edit without pool addition fails rather than inventing an intermediate. The route count does not prove authorship or cultural naming facts.",
        "evidence": "Complete original EN/JA museum-tile guides, endpoint counterfactual, LADDER-01–20, LADDER-HTML, 42 actual persisted browser cases and four bilingual desktop/mobile keyboard submits. No attested-dictionary, prose-clue interpretation, authorship or reader-study claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/nameLadder.md",
        "localizedBodies": {
          "en": "content/en/nameLadder.md",
          "ja": "content/ja/nameLadder.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default pool through LIRA has two three-move shortest walks; no checkpoint gives six, and sampleLimit=1 never changes that total.",
        "Blocking MIRA removes its route; a two-move ceiling reports reachable but over budget, whereas LINA/LIRA/MORA reports no route. No reader handout in either nonfeasible case.",
        "With only LINA/LIRA/MINA/MONA/MORA and LIRA required, five-move shortest witness revisits LINA and explicitly discloses it.",
        "ASCII folding changes actual connectivity while preserving raw spelling. Japanese/astral code points use declared positions; malformed Unicode and scope conflicts clear old results.",
        "Actual reader-file inspection confirms no generated path, count, attempt or private note, while prompt and endpoints remain. Private exports and actual copy retain solution context.",
        "Guarded witness UI, all bounded count/sample examples, invalid and longer attempts, project restore, favorites/compare and four final bilingual viewport submissions require recorded checks."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:683",
      "profileSource": "data/profiles.json#mystery",
      "specBatch": "batch-13",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Finite progress-state graph, exact shortest-route counting with bounded witnesses, code-point traces, supplied-attempt validation and separated solution/public handoffs; no fabricated effort estimate."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "nameLadder",
        "engineFiles": [
          "web/name-ladder.mjs",
          "web/name-ladder-tool.mjs",
          "web/name-ladder-view.mjs",
          "web/name-ladder-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/name-ladder.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "pool",
          "label": [
            "Allowed name forms · one per line",
            "使用できる表記・1行に一つ"
          ],
          "type": "textarea",
          "default": "LINA\nLIRA\nLONA\nLORA\nMINA\nMIRA\nMONA\nMORA",
          "help": [
            "2–600 authored forms, each 2–24 Unicode code points and ≤48 UTF-16 units. No surrounding whitespace or control characters. Blank lines are ignored; different lengths are explicitly excluded from this puzzle. These are fictional fixtures, not attested names.",
            "2〜600件、各2〜24 Unicodeコードポイントかつ48 UTF-16単位以内。前後の空白や制御文字は不可。空行は無視し、長さの違う表記は本問の対象外と明示します。例は架空の素材で、実在名の認定ではありません。"
          ],
          "maxLength": 50000
        },
        {
          "key": "start",
          "label": [
            "Start form",
            "始点の表記"
          ],
          "type": "text",
          "default": "LINA",
          "help": null,
          "maxLength": 48
        },
        {
          "key": "target",
          "label": [
            "Target form · shown to the reader",
            "終点の表記・読者にも表示"
          ],
          "type": "text",
          "default": "MORA",
          "help": [
            "Both endpoints must resolve to different listed forms of equal comparison length. This puzzle exposes both ends; it does not prove that an unstated identity clue has a unique interpretation.",
            "両端は一覧にある異なる表記へ対応し、比較長が同じである必要があります。両端を明示する問題で、暗黙の正体の手掛かりが一意に読めるとは認定しません。"
          ],
          "maxLength": 48
        },
        {
          "key": "policy",
          "label": [
            "Comparison policy",
            "比較規則"
          ],
          "type": "select",
          "default": "exact",
          "help": [
            "No Unicode normalization, pronunciation inference or transliteration. Raw spellings remain visible; collisions under the chosen policy are rejected. A code point is not necessarily a visible grapheme.",
            "Unicode正規化、発音推定、翻字はしません。元表記も表示し、比較規則で重なる表記は拒否します。コードポイントは見た目の一文字と常に同じではありません。"
          ],
          "options": [
            [
              "exact",
              [
                "Exact Unicode code points",
                "Unicodeコードポイントをそのまま比較"
              ]
            ],
            [
              "ascii-fold",
              [
                "ASCII A–Z → a–z only",
                "ASCIIのA〜Zだけa〜zへ"
              ]
            ]
          ]
        },
        {
          "key": "checkpoints",
          "label": [
            "Ordered required checkpoints",
            "指定順に通る表記"
          ],
          "type": "textarea",
          "default": "LIRA",
          "help": [
            "0–6 distinct listed forms, one per line, excluding endpoints. First arrivals must follow this order; later revisits are allowed. A future checkpoint and the target cannot be entered early. This searches walks, not certified no-repeat paths.",
            "両端以外の異なる0〜6件を1行ずつ指定。初回到着をこの順にし、後の再訪は許可します。後の通過点や終点へ先に入れません。再訪禁止の道を認定する探索ではありません。"
          ],
          "maxLength": 50000
        },
        {
          "key": "blocked",
          "label": [
            "Forbidden forms",
            "使用を禁止する表記"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "0–100 listed forms. Do not block endpoints or checkpoints. The report preserves excluded entries so a smaller pool cannot masquerade as the original scope.",
            "一覧内の0〜100件。両端や通過点は禁止できません。除外を記録し、小さくなった一覧を元の全範囲として扱いません。"
          ],
          "maxLength": 50000
        },
        {
          "key": "maxMoves",
          "label": [
            "Move ceiling · 1–60",
            "手数の上限・1〜60"
          ],
          "type": "number",
          "default": 3,
          "help": [
            "The engine computes the global shortest distance in the declared finite state graph. A route beyond this ceiling is reported as over budget, not unreachable.",
            "指定した有限状態グラフ全体で最短距離を計算します。上限超過は到達不能と区別して示します。"
          ]
        },
        {
          "key": "sampleLimit",
          "label": [
            "Witness sample limit · 1–12",
            "表示する検証例・1〜12"
          ],
          "type": "number",
          "default": 4,
          "help": [
            "Only limits displayed witnesses. All shortest walks are counted exactly as a decimal string; a truncated sample never means there is only one answer.",
            "制限するのは表示例だけです。全最短経路数は正確な十進文字列で示し、表示の省略を一意解と扱いません。"
          ]
        },
        {
          "key": "attempt",
          "label": [
            "Proposed route · optional",
            "試行する経路・任意"
          ],
          "type": "textarea",
          "default": "",
          "help": [
            "Up to 61 forms, one per line. Inspect membership, one-substitution steps, checkpoint order, endpoints, budget and shortestness. An invalid attempt does not erase the separately proved puzzle witnesses.",
            "最大61表記を1行ずつ。一覧への所属、一手の置換、通過順、両端、上限、最短性を確認します。不正な試行で、別に証明した問題の経路を消しません。"
          ],
          "maxLength": 50000
        },
        {
          "key": "clue",
          "label": [
            "Reader-facing prompt",
            "読者用の問題文"
          ],
          "type": "textarea",
          "default": "Move from LINA to MORA through LIRA. Use only the displayed forms and find a shortest walk by changing one comparison code point per move.",
          "help": [
            "Author the prompt, ≤1200 UTF-16 units. Generated rule disclosures and both endpoints accompany it in the reader sheet. The program does not interpret or certify your prose clue.",
            "1200 UTF-16単位以内で作者が問題文を書きます。読者用には規則説明と両端も付きます。文章の意味を解釈・認定しません。"
          ],
          "maxLength": 1200
        },
        {
          "key": "storyUse",
          "label": [
            "Private story purpose · optional",
            "非公開の物語上の用途・任意"
          ],
          "type": "textarea",
          "default": "A conservator asks two siblings to demonstrate two equally short paths across the museum’s invented name tiles, so the exhibit credits both contributions.",
          "help": [
            "≤1200. Kept in private copying, favorites and audit; omitted from the reader exercise. Names and tile conventions are fictional, not cultural or etymological claims.",
            "1200以内。非公開のコピー、保存候補、監査に残し、読者用問題には含めません。名前やタイルの慣習は架空で、文化や語源の主張ではありません。"
          ],
          "maxLength": 1200
        }
      ]
    },
    {
      "id": "nw-mystery-reveal-name-recap",
      "slug": "mystery-reveal-name-recap",
      "name": "Mystery reveal name recap",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/mystery-reveal-name-recap/",
        "ja": "/ja/tools/mystery-reveal-name-recap/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Explain the identity solution without contradicting earlier references",
      "task": "Explain the identity solution without contradicting earlier references",
      "searchIntent": {
        "primary": "Complete the task: Explain the identity solution without contradicting earlier references",
        "queryHypothesis": "mystery reveal name recap",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain the identity solution without contradicting earlier references?",
        "When should mystery reveal name recap be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain the identity solution without contradicting earlier references",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain the identity solution without contradicting earlier references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.23249999999999998,
          "sharedProfile": false,
          "difference": "Explain the identity solution without contradicting earlier references versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Explain the identity solution without contradicting earlier references versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Explain the identity solution without contradicting earlier references versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain the identity solution without contradicting earlier references",
        "outline": [
          "Explain the specific decision: Explain the identity solution without contradicting earlier references",
          "Define the applicable contract and limits for Mystery reveal name recap",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain the identity solution without contradicting earlier references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain the identity solution without contradicting earlier references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:684",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-false-name-confession-audit",
      "slug": "false-name-confession-audit",
      "name": "False name confession audit",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/false-name-confession-audit/",
        "ja": "/ja/tools/false-name-confession-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Compare what is confessed with what the story actually establishes",
      "task": "Compare what is confessed with what the story actually establishes",
      "searchIntent": {
        "primary": "Complete the task: Compare what is confessed with what the story actually establishes",
        "queryHypothesis": "false name confession audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare what is confessed with what the story actually establishes?",
        "When should false name confession audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare what is confessed with what the story actually establishes",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare what is confessed with what the story actually establishes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-confession-identity",
          "score": 0.24,
          "sharedProfile": false,
          "difference": "Compare what is confessed with what the story actually establishes versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-in-confession-scene",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Compare what is confessed with what the story actually establishes versus Control who is identified by an emotionally loaded address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-sacrifice-consequence",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare what is confessed with what the story actually establishes versus Specify what identity, memory or relationship is lost; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare what is confessed with what the story actually establishes",
        "outline": [
          "Explain the specific decision: Compare what is confessed with what the story actually establishes",
          "Define the applicable contract and limits for False name confession audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare what is confessed with what the story actually establishes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare what is confessed with what the story actually establishes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:685",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-name-based-alibi-timeline",
      "slug": "name-based-alibi-timeline",
      "name": "Name based alibi timeline",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/name-based-alibi-timeline/",
        "ja": "/ja/tools/name-based-alibi-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Check which form a witness could have heard at a dated event",
      "task": "Check which form a witness could have heard at a dated event",
      "searchIntent": {
        "primary": "Complete the task: Check which form a witness could have heard at a dated event",
        "queryHypothesis": "name based alibi timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check which form a witness could have heard at a dated event?",
        "When should name based alibi timeline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check which form a witness could have heard at a dated event",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check which form a witness could have heard at a dated event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.145,
          "sharedProfile": false,
          "difference": "Check which form a witness could have heard at a dated event versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Check which form a witness could have heard at a dated event versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Check which form a witness could have heard at a dated event versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check which form a witness could have heard at a dated event",
        "outline": [
          "Explain the specific decision: Check which form a witness could have heard at a dated event",
          "Define the applicable contract and limits for Name based alibi timeline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check which form a witness could have heard at a dated event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check which form a witness could have heard at a dated event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:686",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-mystery-naming-sensitivity-review",
      "slug": "mystery-naming-sensitivity-review",
      "name": "Mystery naming sensitivity review",
      "category": "mystery",
      "urls": {
        "en": "/en/tools/mystery-naming-sensitivity-review/",
        "ja": "/ja/tools/mystery-naming-sensitivity-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "mystery authors and puzzle narrative designers",
      "scenario": "Avoid treating ethnicity inferred from a name as evidence of guilt",
      "task": "Avoid treating ethnicity inferred from a name as evidence of guilt",
      "searchIntent": {
        "primary": "Complete the task: Avoid treating ethnicity inferred from a name as evidence of guilt",
        "queryHypothesis": "mystery naming sensitivity review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid treating ethnicity inferred from a name as evidence of guilt?",
        "When should mystery naming sensitivity review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "solution and alternative suspects: test fairness",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "reader knowledge timeline: gate evidence",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "explicit transformation rule: make a clue solvable",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity"
      ],
      "requiredData": [
        {
          "description": "authored suspect ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "verified linguistic evidence where needed",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid treating ethnicity inferred from a name as evidence of guilt",
        "test alternative solutions as well as the intended answer",
        "a name resemblance alone does not establish identity",
        "Proposed category workflow: solution → disclosed rules → alternatives → blind reader test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "clue chain and alternatives",
        "knowledge gaps",
        "spoiler bounded reader test"
      ],
      "capabilities": [
        "enumerate alternative answers under declared rules",
        "audit clues after a suspect rename"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid treating ethnicity inferred from a name as evidence of guilt. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-naming-sensitivity-review",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Avoid treating ethnicity inferred from a name as evidence of guilt versus Require context and native language review for cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Avoid treating ethnicity inferred from a name as evidence of guilt versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-review-handoff",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Avoid treating ethnicity inferred from a name as evidence of guilt versus Package unresolved choices and evidence for a human translator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid treating ethnicity inferred from a name as evidence of guilt",
        "outline": [
          "Explain the specific decision: Avoid treating ethnicity inferred from a name as evidence of guilt",
          "Define the applicable contract and limits for Mystery naming sensitivity review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid treating ethnicity inferred from a name as evidence of guilt; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid treating ethnicity inferred from a name as evidence of guilt",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:687",
      "profileSource": "data/profiles.json#mystery"
    },
    {
      "id": "nw-true-name-spell-contract",
      "slug": "true-name-spell-contract",
      "name": "True name spell contract",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/true-name-spell-contract/",
        "ja": "/ja/tools/true-name-spell-contract/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Define exactly which name form grants which fictional capability",
      "task": "Define exactly which name form grants which fictional capability",
      "searchIntent": {
        "primary": "Complete the task: Define exactly which name form grants which fictional capability",
        "queryHypothesis": "true name spell contract",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define exactly which name form grants which fictional capability?",
        "When should true name spell contract be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define exactly which name form grants which fictional capability",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define exactly which name form grants which fictional capability. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-magical-contract-signatory-names",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Define exactly which name form grants which fictional capability versus Define which identity form a fictional contract recognizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dream-name-memory-anchor",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Define exactly which name form grants which fictional capability versus Define which form persists between dream and waking scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-reconciles-dual-identities",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define exactly which name form grants which fictional capability versus Define which differences remain after integration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define exactly which name form grants which fictional capability",
        "outline": [
          "Explain the specific decision: Define exactly which name form grants which fictional capability",
          "Define the applicable contract and limits for True name spell contract",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define exactly which name form grants which fictional capability; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define exactly which name form grants which fictional capability",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:690",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-curse-transfer",
      "slug": "name-curse-transfer",
      "name": "Name curse transfer",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-curse-transfer/",
        "ja": "/ja/tools/name-curse-transfer/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Model conditions for transferring a curse through an invented name system",
      "task": "Model conditions for transferring a curse through an invented name system",
      "searchIntent": {
        "primary": "Complete the task: Model conditions for transferring a curse through an invented name system",
        "queryHypothesis": "name curse transfer",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model conditions for transferring a curse through an invented name system?",
        "When should name curse transfer be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model conditions for transferring a curse through an invented name system",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model conditions for transferring a curse through an invented name system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Model conditions for transferring a curse through an invented name system versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model conditions for transferring a curse through an invented name system versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-names-as-currency",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Model conditions for transferring a curse through an invented name system versus Model ownership, exchange and personal consequences in an invented economy; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model conditions for transferring a curse through an invented name system",
        "outline": [
          "Explain the specific decision: Model conditions for transferring a curse through an invented name system",
          "Define the applicable contract and limits for Name curse transfer",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model conditions for transferring a curse through an invented name system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model conditions for transferring a curse through an invented name system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:691",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-sacrifice-consequence",
      "slug": "name-sacrifice-consequence",
      "name": "Name sacrifice consequence",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-sacrifice-consequence/",
        "ja": "/ja/tools/name-sacrifice-consequence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Specify what identity, memory or relationship is lost",
      "task": "Specify what identity, memory or relationship is lost",
      "searchIntent": {
        "primary": "Complete the task: Specify what identity, memory or relationship is lost",
        "queryHypothesis": "name sacrifice consequence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to specify what identity, memory or relationship is lost?",
        "When should name sacrifice consequence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Specify what identity, memory or relationship is lost",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Specify what identity, memory or relationship is lost. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-false-name-confession-audit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Specify what identity, memory or relationship is lost versus Compare what is confessed with what the story actually establishes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Specify what identity, memory or relationship is lost versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Specify what identity, memory or relationship is lost versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Specify what identity, memory or relationship is lost",
        "outline": [
          "Explain the specific decision: Specify what identity, memory or relationship is lost",
          "Define the applicable contract and limits for Name sacrifice consequence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Specify what identity, memory or relationship is lost; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Specify what identity, memory or relationship is lost",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:692",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-exchange-pact",
      "slug": "name-exchange-pact",
      "name": "Name exchange pact",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-exchange-pact/",
        "ja": "/ja/tools/name-exchange-pact/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Track reciprocal obligations and what counts as valid consent in fiction",
      "task": "Track reciprocal obligations and what counts as valid consent in fiction",
      "searchIntent": {
        "primary": "Complete the task: Track reciprocal obligations and what counts as valid consent in fiction",
        "queryHypothesis": "name exchange pact",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track reciprocal obligations and what counts as valid consent in fiction?",
        "When should name exchange pact be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track reciprocal obligations and what counts as valid consent in fiction",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track reciprocal obligations and what counts as valid consent in fiction. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-gives-another-a-name",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Track reciprocal obligations and what counts as valid consent in fiction versus Make consent, power and relationship explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-name-tradeoff-exercise",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Track reciprocal obligations and what counts as valid consent in fiction versus Explain what a localization preserves and loses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-romantic-address-progression",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Track reciprocal obligations and what counts as valid consent in fiction versus Tie endearments to story milestones and consent; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track reciprocal obligations and what counts as valid consent in fiction",
        "outline": [
          "Explain the specific decision: Track reciprocal obligations and what counts as valid consent in fiction",
          "Define the applicable contract and limits for Name exchange pact",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track reciprocal obligations and what counts as valid consent in fiction; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track reciprocal obligations and what counts as valid consent in fiction",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:693",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-prophecy-naming-loophole",
      "slug": "prophecy-naming-loophole",
      "name": "Prophecy naming loophole",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/prophecy-naming-loophole/",
        "ja": "/ja/tools/prophecy-naming-loophole/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Test interpretations against the disclosed wording and world rules",
      "task": "Test interpretations against the disclosed wording and world rules",
      "searchIntent": {
        "primary": "Complete the task: Test interpretations against the disclosed wording and world rules",
        "queryHypothesis": "prophecy naming loophole",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test interpretations against the disclosed wording and world rules?",
        "When should prophecy naming loophole be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test interpretations against the disclosed wording and world rules",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test interpretations against the disclosed wording and world rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test interpretations against the disclosed wording and world rules versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test interpretations against the disclosed wording and world rules versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-test-revision-comparison",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test interpretations against the disclosed wording and world rules versus Compare before and after candidates with disclosed test conditions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test interpretations against the disclosed wording and world rules",
        "outline": [
          "Explain the specific decision: Test interpretations against the disclosed wording and world rules",
          "Define the applicable contract and limits for Prophecy naming loophole",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test interpretations against the disclosed wording and world rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test interpretations against the disclosed wording and world rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:694",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-erased-archive",
      "slug": "name-erased-archive",
      "name": "Name erased archive",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-erased-archive/",
        "ja": "/ja/tools/name-erased-archive/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Determine which records survive a fictional erasure event",
      "task": "Determine which records survive a fictional erasure event",
      "searchIntent": {
        "primary": "Complete the task: Determine which records survive a fictional erasure event",
        "queryHypothesis": "name erased archive",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to determine which records survive a fictional erasure event?",
        "When should name erased archive be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Determine which records survive a fictional erasure event",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Determine which records survive a fictional erasure event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-erasure-story-continuity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Determine which records survive a fictional erasure event versus Define how records and memories change after erasure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Determine which records survive a fictional erasure event versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-alibi-timeline",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Determine which records survive a fictional erasure event versus Check which form a witness could have heard at a dated event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Determine which records survive a fictional erasure event",
        "outline": [
          "Explain the specific decision: Determine which records survive a fictional erasure event",
          "Define the applicable contract and limits for Name erased archive",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Determine which records survive a fictional erasure event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Determine which records survive a fictional erasure event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:695",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-forgotten-by-everyone",
      "slug": "name-forgotten-by-everyone",
      "name": "Name forgotten by everyone",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-forgotten-by-everyone/",
        "ja": "/ja/tools/name-forgotten-by-everyone/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Preserve reader orientation while characters lose references",
      "task": "Preserve reader orientation while characters lose references",
      "searchIntent": {
        "primary": "Complete the task: Preserve reader orientation while characters lose references",
        "queryHypothesis": "name forgotten by everyone",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve reader orientation while characters lose references?",
        "When should name forgotten by everyone be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve reader orientation while characters lose references",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve reader orientation while characters lose references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-refuses-name-disclosure",
          "score": 0.2785714285714286,
          "sharedProfile": false,
          "difference": "Preserve reader orientation while characters lose references versus Preserve agency while maintaining reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-doppelganger-cast-labeling",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Preserve reader orientation while characters lose references versus Maintain intended likeness while preserving reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Preserve reader orientation while characters lose references versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve reader orientation while characters lose references",
        "outline": [
          "Explain the specific decision: Preserve reader orientation while characters lose references",
          "Define the applicable contract and limits for Name forgotten by everyone",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve reader orientation while characters lose references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve reader orientation while characters lose references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:696",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-that-cannot-be-spoken",
      "slug": "name-that-cannot-be-spoken",
      "name": "Name that cannot be spoken",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-that-cannot-be-spoken/",
        "ja": "/ja/tools/name-that-cannot-be-spoken/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Provide alternative references with explicit fictional consequences",
      "task": "Provide alternative references with explicit fictional consequences",
      "searchIntent": {
        "primary": "Complete the task: Provide alternative references with explicit fictional consequences",
        "queryHypothesis": "name that cannot be spoken",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to provide alternative references with explicit fictional consequences?",
        "When should name that cannot be spoken be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Provide alternative references with explicit fictional consequences",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Provide alternative references with explicit fictional consequences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Provide alternative references with explicit fictional consequences versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-accessibility",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Provide alternative references with explicit fictional consequences versus Provide a fair alternative when a clue relies on visual or audio distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Provide alternative references with explicit fictional consequences versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Provide alternative references with explicit fictional consequences",
        "outline": [
          "Explain the specific decision: Provide alternative references with explicit fictional consequences",
          "Define the applicable contract and limits for Name that cannot be spoken",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Provide alternative references with explicit fictional consequences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Provide alternative references with explicit fictional consequences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:697",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-spoken-summons",
      "slug": "name-spoken-summons",
      "name": "Name spoken summons",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-spoken-summons/",
        "ja": "/ja/tools/name-spoken-summons/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Define identity targeting and ambiguity in a summoning system",
      "task": "Define identity targeting and ambiguity in a summoning system",
      "searchIntent": {
        "primary": "Complete the task: Define identity targeting and ambiguity in a summoning system",
        "queryHypothesis": "name spoken summons",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define identity targeting and ambiguity in a summoning system?",
        "When should name spoken summons be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define identity targeting and ambiguity in a summoning system",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define identity targeting and ambiguity in a summoning system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define identity targeting and ambiguity in a summoning system versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magical-contract-signatory-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define identity targeting and ambiguity in a summoning system versus Define which identity form a fictional contract recognizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-seasonal-name-change",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define identity targeting and ambiguity in a summoning system versus Define repeatable seasonal forms with stable identity underneath; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define identity targeting and ambiguity in a summoning system",
        "outline": [
          "Explain the specific decision: Define identity targeting and ambiguity in a summoning system",
          "Define the applicable contract and limits for Name spoken summons",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define identity targeting and ambiguity in a summoning system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define identity targeting and ambiguity in a summoning system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:698",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-renaming-transforms-reality",
      "slug": "renaming-transforms-reality",
      "name": "Renaming transforms reality",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/renaming-transforms-reality/",
        "ja": "/ja/tools/renaming-transforms-reality/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Test scope, exceptions and competing claims of a name change",
      "task": "Test scope, exceptions and competing claims of a name change",
      "searchIntent": {
        "primary": "Complete the task: Test scope, exceptions and competing claims of a name change",
        "queryHypothesis": "renaming transforms reality",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test scope, exceptions and competing claims of a name change?",
        "When should renaming transforms reality be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test scope, exceptions and competing claims of a name change",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test scope, exceptions and competing claims of a name change. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test scope, exceptions and competing claims of a name change versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undead-renaming-decision",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Test scope, exceptions and competing claims of a name change versus Tie a name change to character agency rather than species stereotype; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-rename-counterfactual",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Test scope, exceptions and competing claims of a name change versus Test whether a mystery remains fair after a naming change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test scope, exceptions and competing claims of a name change",
        "outline": [
          "Explain the specific decision: Test scope, exceptions and competing claims of a name change",
          "Define the applicable contract and limits for Renaming transforms reality",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test scope, exceptions and competing claims of a name change; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test scope, exceptions and competing claims of a name change",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:699",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-inherited-secret-name",
      "slug": "inherited-secret-name",
      "name": "Inherited secret name",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/inherited-secret-name/",
        "ja": "/ja/tools/inherited-secret-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Track knowledge transfer and failures across generations",
      "task": "Track knowledge transfer and failures across generations",
      "searchIntent": {
        "primary": "Complete the task: Track knowledge transfer and failures across generations",
        "queryHypothesis": "inherited secret name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track knowledge transfer and failures across generations?",
        "When should inherited secret name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track knowledge transfer and failures across generations",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track knowledge transfer and failures across generations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track knowledge transfer and failures across generations versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hyphenated-family-name-limits",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track knowledge transfer and failures across generations versus Resolve accumulated surnames across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track knowledge transfer and failures across generations versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track knowledge transfer and failures across generations",
        "outline": [
          "Explain the specific decision: Track knowledge transfer and failures across generations",
          "Define the applicable contract and limits for Inherited secret name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track knowledge transfer and failures across generations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track knowledge transfer and failures across generations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:700",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-false-true-name-decoy",
      "slug": "false-true-name-decoy",
      "name": "False true name decoy",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/false-true-name-decoy/",
        "ja": "/ja/tools/false-true-name-decoy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Make the decoy plausible under an established magic rule",
      "task": "Make the decoy plausible under an established magic rule",
      "searchIntent": {
        "primary": "Complete the task: Make the decoy plausible under an established magic rule",
        "queryHypothesis": "false true name decoy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make the decoy plausible under an established magic rule?",
        "When should false true name decoy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make the decoy plausible under an established magic rule",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make the decoy plausible under an established magic rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Make the decoy plausible under an established magic rule versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-true-name-magic-access",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Make the decoy plausible under an established magic rule versus Set explicit knowledge and permission rules for a magic system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-genealogy-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Make the decoy plausible under an established magic rule versus Separate forged lineage claims from author known relations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make the decoy plausible under an established magic rule",
        "outline": [
          "Explain the specific decision: Make the decoy plausible under an established magic rule",
          "Define the applicable contract and limits for False true name decoy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make the decoy plausible under an established magic rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make the decoy plausible under an established magic rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:701",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-names-as-currency",
      "slug": "names-as-currency",
      "name": "Names as currency",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/names-as-currency/",
        "ja": "/ja/tools/names-as-currency/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Model ownership, exchange and personal consequences in an invented economy",
      "task": "Model ownership, exchange and personal consequences in an invented economy",
      "searchIntent": {
        "primary": "Complete the task: Model ownership, exchange and personal consequences in an invented economy",
        "queryHypothesis": "names as currency",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model ownership, exchange and personal consequences in an invented economy?",
        "When should names as currency be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model ownership, exchange and personal consequences in an invented economy",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model ownership, exchange and personal consequences in an invented economy. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Model ownership, exchange and personal consequences in an invented economy versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model ownership, exchange and personal consequences in an invented economy versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-curse-transfer",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Model ownership, exchange and personal consequences in an invented economy versus Model conditions for transferring a curse through an invented name system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model ownership, exchange and personal consequences in an invented economy",
        "outline": [
          "Explain the specific decision: Model ownership, exchange and personal consequences in an invented economy",
          "Define the applicable contract and limits for Names as currency",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model ownership, exchange and personal consequences in an invented economy; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model ownership, exchange and personal consequences in an invented economy",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:702",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-names-as-citizenship",
      "slug": "names-as-citizenship",
      "name": "Names as citizenship",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/names-as-citizenship/",
        "ja": "/ja/tools/names-as-citizenship/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Separate state assigned recognition from self identity in a fictional regime",
      "task": "Separate state assigned recognition from self identity in a fictional regime",
      "searchIntent": {
        "primary": "Complete the task: Separate state assigned recognition from self identity in a fictional regime",
        "queryHypothesis": "names as citizenship",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate state assigned recognition from self identity in a fictional regime?",
        "When should names as citizenship be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate state assigned recognition from self identity in a fictional regime",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate state assigned recognition from self identity in a fictional regime. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-citizenship-name-reform",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Separate state assigned recognition from self identity in a fictional regime versus Model policy change and individual exceptions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate state assigned recognition from self identity in a fictional regime versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-ending-signature",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Separate state assigned recognition from self identity in a fictional regime versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate state assigned recognition from self identity in a fictional regime",
        "outline": [
          "Explain the specific decision: Separate state assigned recognition from self identity in a fictional regime",
          "Define the applicable contract and limits for Names as citizenship",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate state assigned recognition from self identity in a fictional regime; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate state assigned recognition from self identity in a fictional regime",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:703",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-rationing-society",
      "slug": "name-rationing-society",
      "name": "Name rationing society",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-rationing-society/",
        "ja": "/ja/tools/name-rationing-society/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Explain allocation rules and social conflicts without a universal cultural claim",
      "task": "Explain allocation rules and social conflicts without a universal cultural claim",
      "searchIntent": {
        "primary": "Complete the task: Explain allocation rules and social conflicts without a universal cultural claim",
        "queryHypothesis": "name rationing society",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain allocation rules and social conflicts without a universal cultural claim?",
        "When should name rationing society be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain allocation rules and social conflicts without a universal cultural claim",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain allocation rules and social conflicts without a universal cultural claim. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-household-servant-address",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Explain allocation rules and social conflicts without a universal cultural claim versus Map speaker status and address without making a universal cultural claim; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-katakana-identity-choice",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Explain allocation rules and social conflicts without a universal cultural claim versus Explain author selected script effects without claiming universal meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-records-mismatch",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Explain allocation rules and social conflicts without a universal cultural claim versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain allocation rules and social conflicts without a universal cultural claim",
        "outline": [
          "Explain the specific decision: Explain allocation rules and social conflicts without a universal cultural claim",
          "Define the applicable contract and limits for Name rationing society",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain allocation rules and social conflicts without a universal cultural claim; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain allocation rules and social conflicts without a universal cultural claim",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:704",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-nameless-rebellion-identity",
      "slug": "nameless-rebellion-identity",
      "name": "Nameless rebellion identity",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/nameless-rebellion-identity/",
        "ja": "/ja/tools/nameless-rebellion-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Coordinate collective and personal identities in an authored movement",
      "task": "Coordinate collective and personal identities in an authored movement",
      "searchIntent": {
        "primary": "Complete the task: Coordinate collective and personal identities in an authored movement",
        "queryHypothesis": "nameless rebellion identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate collective and personal identities in an authored movement?",
        "When should nameless rebellion identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate collective and personal identities in an authored movement",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate collective and personal identities in an authored movement. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-clone-identity-differentiation",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Coordinate collective and personal identities in an authored movement versus Assign legal, personal and laboratory identities to cloned characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hive-member-identity",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Coordinate collective and personal identities in an authored movement versus Distinguish collective reference from individual agents; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sibling-rival-ensemble",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Coordinate collective and personal identities in an authored movement versus Coordinate kinship cues and rival identities across scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate collective and personal identities in an authored movement",
        "outline": [
          "Explain the specific decision: Coordinate collective and personal identities in an authored movement",
          "Define the applicable contract and limits for Nameless rebellion identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate collective and personal identities in an authored movement; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate collective and personal identities in an authored movement",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:705",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-assigned-number-resistance",
      "slug": "assigned-number-resistance",
      "name": "Assigned number resistance",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/assigned-number-resistance/",
        "ja": "/ja/tools/assigned-number-resistance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Track adoption and rejection of institutional numeric labels",
      "task": "Track adoption and rejection of institutional numeric labels",
      "searchIntent": {
        "primary": "Complete the task: Track adoption and rejection of institutional numeric labels",
        "queryHypothesis": "assigned number resistance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track adoption and rejection of institutional numeric labels?",
        "When should assigned number resistance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track adoption and rejection of institutional numeric labels",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track adoption and rejection of institutional numeric labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-prison-ensemble-naming",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track adoption and rejection of institutional numeric labels versus Separate institutional labels from self and peer chosen names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-construct-creator-assigned-name",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Track adoption and rejection of institutional numeric labels versus Contrast creator labels with the construct's self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-resistance-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track adoption and rejection of institutional numeric labels versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track adoption and rejection of institutional numeric labels",
        "outline": [
          "Explain the specific decision: Track adoption and rejection of institutional numeric labels",
          "Define the applicable contract and limits for Assigned number resistance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track adoption and rejection of institutional numeric labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track adoption and rejection of institutional numeric labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:706",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-reincarnation-recognition-clue",
      "slug": "reincarnation-recognition-clue",
      "name": "Reincarnation recognition clue",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/reincarnation-recognition-clue/",
        "ja": "/ja/tools/reincarnation-recognition-clue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Limit a name resemblance to one piece of narrative evidence",
      "task": "Limit a name resemblance to one piece of narrative evidence",
      "searchIntent": {
        "primary": "Complete the task: Limit a name resemblance to one piece of narrative evidence",
        "queryHypothesis": "reincarnation recognition clue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to limit a name resemblance to one piece of narrative evidence?",
        "When should reincarnation recognition clue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Limit a name resemblance to one piece of narrative evidence",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Limit a name resemblance to one piece of narrative evidence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-missing-name-record-clue",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Limit a name resemblance to one piece of narrative evidence versus Distinguish absent evidence from evidence of absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-translated-name-clue",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Limit a name resemblance to one piece of narrative evidence versus Require language evidence accessible to the reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Limit a name resemblance to one piece of narrative evidence versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Limit a name resemblance to one piece of narrative evidence",
        "outline": [
          "Explain the specific decision: Limit a name resemblance to one piece of narrative evidence",
          "Define the applicable contract and limits for Reincarnation recognition clue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Limit a name resemblance to one piece of narrative evidence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Limit a name resemblance to one piece of narrative evidence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:707",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-time-loop-alias-experiment",
      "slug": "time-loop-alias-experiment",
      "name": "Time loop alias experiment",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/time-loop-alias-experiment/",
        "ja": "/ja/tools/time-loop-alias-experiment/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Record changing aliases and who can detect the pattern",
      "task": "Record changing aliases and who can detect the pattern",
      "searchIntent": {
        "primary": "Complete the task: Record changing aliases and who can detect the pattern",
        "queryHypothesis": "time loop alias experiment",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record changing aliases and who can detect the pattern?",
        "When should time loop alias experiment be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record changing aliases and who can detect the pattern",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record changing aliases and who can detect the pattern. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-time-loop-remembered-names",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Record changing aliases and who can detect the pattern versus Audit explicit name and connection memory facts through reset-specific retention, loss and relearning, keeping parent sources, sibling branches and observer states separate.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-naming-power-audit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Record changing aliases and who can detect the pattern versus Identify who can assign, refuse or change a personal label; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-recurring-villain-title-chain",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Record changing aliases and who can detect the pattern versus Track changing epithets across encounters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record changing aliases and who can detect the pattern",
        "outline": [
          "Explain the specific decision: Record changing aliases and who can detect the pattern",
          "Define the applicable contract and limits for Time loop alias experiment",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record changing aliases and who can detect the pattern; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record changing aliases and who can detect the pattern",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:708",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-alternate-history-name-divergence",
      "slug": "alternate-history-name-divergence",
      "name": "Alternate history name divergence",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/alternate-history-name-divergence/",
        "ja": "/ja/tools/alternate-history-name-divergence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Trace the authored divergence rather than invent historical certainty",
      "task": "Trace the authored divergence rather than invent historical certainty",
      "searchIntent": {
        "primary": "Complete the task: Trace the authored divergence rather than invent historical certainty",
        "queryHypothesis": "alternate history name divergence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace the authored divergence rather than invent historical certainty?",
        "When should alternate history name divergence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace the authored divergence rather than invent historical certainty",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace the authored divergence rather than invent historical certainty. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-naming-anachronism-review",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace the authored divergence rather than invent historical certainty versus Flag unsupported forms rather than manufacture certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-noble-title-system",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Trace the authored divergence rather than invent historical certainty versus Define ranked titles using authored rules rather than historical claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stolen-family-name-motive",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Trace the authored divergence rather than invent historical certainty versus Connect naming conflict to character stakes rather than a puzzle alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace the authored divergence rather than invent historical certainty",
        "outline": [
          "Explain the specific decision: Trace the authored divergence rather than invent historical certainty",
          "Define the applicable contract and limits for Alternate history name divergence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace the authored divergence rather than invent historical certainty; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace the authored divergence rather than invent historical certainty",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:709",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-parallel-universe-true-name",
      "slug": "parallel-universe-true-name",
      "name": "Parallel universe true name",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/parallel-universe-true-name/",
        "ja": "/ja/tools/parallel-universe-true-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Separate corresponding identities and world specific reference rules",
      "task": "Separate corresponding identities and world specific reference rules",
      "searchIntent": {
        "primary": "Complete the task: Separate corresponding identities and world specific reference rules",
        "queryHypothesis": "parallel universe true name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate corresponding identities and world specific reference rules?",
        "When should parallel universe true name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate corresponding identities and world specific reference rules",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate corresponding identities and world specific reference rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-parallel-world-cast-correspondence",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Separate corresponding identities and world specific reference rules versus Link counterparts while preserving world specific forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate corresponding identities and world specific reference rules versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-true-name-alias-bridge",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Separate corresponding identities and world specific reference rules versus Design linked identities with an explicit clue strength limit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate corresponding identities and world specific reference rules",
        "outline": [
          "Explain the specific decision: Separate corresponding identities and world specific reference rules",
          "Define the applicable contract and limits for Parallel universe true name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate corresponding identities and world specific reference rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate corresponding identities and world specific reference rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:710",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-dream-name-memory-anchor",
      "slug": "dream-name-memory-anchor",
      "name": "Dream name memory anchor",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/dream-name-memory-anchor/",
        "ja": "/ja/tools/dream-name-memory-anchor/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Define which form persists between dream and waking scenes",
      "task": "Define which form persists between dream and waking scenes",
      "searchIntent": {
        "primary": "Complete the task: Define which form persists between dream and waking scenes",
        "queryHypothesis": "dream name memory anchor",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define which form persists between dream and waking scenes?",
        "When should dream name memory anchor be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define which form persists between dream and waking scenes",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define which form persists between dream and waking scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dream-character-mutable-name",
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Define which form persists between dream and waking scenes versus Define stable references across authored dream transformations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magical-contract-signatory-names",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Define which form persists between dream and waking scenes versus Define which identity form a fictional contract recognizes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-true-name-spell-contract",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Define which form persists between dream and waking scenes versus Define exactly which name form grants which fictional capability; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define which form persists between dream and waking scenes",
        "outline": [
          "Explain the specific decision: Define which form persists between dream and waking scenes",
          "Define the applicable contract and limits for Dream name memory anchor",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define which form persists between dream and waking scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define which form persists between dream and waking scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:711",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-possession-naming-test",
      "slug": "possession-naming-test",
      "name": "Possession naming test",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/possession-naming-test/",
        "ja": "/ja/tools/possession-naming-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "State what a name test can and cannot establish in the fictional rules",
      "task": "State what a name test can and cannot establish in the fictional rules",
      "searchIntent": {
        "primary": "Complete the task: State what a name test can and cannot establish in the fictional rules",
        "queryHypothesis": "possession naming test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to state what a name test can and cannot establish in the fictional rules?",
        "When should possession naming test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: State what a name test can and cannot establish in the fictional rules",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: State what a name test can and cannot establish in the fictional rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-test-revision-comparison",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "State what a name test can and cannot establish in the fictional rules versus Compare before and after candidates with disclosed test conditions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "State what a name test can and cannot establish in the fictional rules versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-delayed-recall-test",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "State what a name test can and cannot establish in the fictional rules versus Test recall after a defined reading passage and delay; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "State what a name test can and cannot establish in the fictional rules",
        "outline": [
          "Explain the specific decision: State what a name test can and cannot establish in the fictional rules",
          "Define the applicable contract and limits for Possession naming test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for State what a name test can and cannot establish in the fictional rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: State what a name test can and cannot establish in the fictional rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:712",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-summoned-entity-misidentification",
      "slug": "summoned-entity-misidentification",
      "name": "Summoned entity misidentification",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/summoned-entity-misidentification/",
        "ja": "/ja/tools/summoned-entity-misidentification/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Design a recoverable targeting mistake with fair setup",
      "task": "Design a recoverable targeting mistake with fair setup",
      "searchIntent": {
        "primary": "Complete the task: Design a recoverable targeting mistake with fair setup",
        "queryHypothesis": "summoned entity misidentification",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a recoverable targeting mistake with fair setup?",
        "When should summoned entity misidentification be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a recoverable targeting mistake with fair setup",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a recoverable targeting mistake with fair setup. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-mistaken-identity-encounter",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Design a recoverable targeting mistake with fair setup versus Design fair recoverable name confusion for a live session; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-name-mistaken-reading-plot",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Design a recoverable targeting mistake with fair setup versus Design a fair clue using verified alternative readings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-mishearing",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Design a recoverable targeting mistake with fair setup versus Design recoverable mishearings that do not depend on false phonetics; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a recoverable targeting mistake with fair setup",
        "outline": [
          "Explain the specific decision: Design a recoverable targeting mistake with fair setup",
          "Define the applicable contract and limits for Summoned entity misidentification",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a recoverable targeting mistake with fair setup; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a recoverable targeting mistake with fair setup",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:713",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-god-loses-worship-name",
      "slug": "god-loses-worship-name",
      "name": "God loses worship name",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/god-loses-worship-name/",
        "ja": "/ja/tools/god-loses-worship-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Track changes in reference, power and remembered identity",
      "task": "Track changes in reference, power and remembered identity",
      "searchIntent": {
        "primary": "Complete the task: Track changes in reference, power and remembered identity",
        "queryHypothesis": "god loses worship name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track changes in reference, power and remembered identity?",
        "When should god loses worship name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track changes in reference, power and remembered identity",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track changes in reference, power and remembered identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-loses-naming-authority",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Track changes in reference, power and remembered identity versus Track who controls labels and how that power shifts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sentient-building-voice-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track changes in reference, power and remembered identity versus Track identity across renovation, ownership and memory changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track changes in reference, power and remembered identity versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track changes in reference, power and remembered identity",
        "outline": [
          "Explain the specific decision: Track changes in reference, power and remembered identity",
          "Define the applicable contract and limits for God loses worship name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track changes in reference, power and remembered identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track changes in reference, power and remembered identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:714",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-character-rewrites-own-myth",
      "slug": "character-rewrites-own-myth",
      "name": "Character rewrites own myth",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/character-rewrites-own-myth/",
        "ja": "/ja/tools/character-rewrites-own-myth/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Coordinate chosen name, public story and skeptical observers",
      "task": "Coordinate chosen name, public story and skeptical observers",
      "searchIntent": {
        "primary": "Complete the task: Coordinate chosen name, public story and skeptical observers",
        "queryHypothesis": "character rewrites own myth",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate chosen name, public story and skeptical observers?",
        "When should character rewrites own myth be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate chosen name, public story and skeptical observers",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate chosen name, public story and skeptical observers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Coordinate chosen name, public story and skeptical observers versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-theater-troupe-stage-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Coordinate chosen name, public story and skeptical observers versus Coordinate public credits and backstage references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-author-note-signoff",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Coordinate chosen name, public story and skeptical observers versus Align informal signoff with the chosen public author identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate chosen name, public story and skeptical observers",
        "outline": [
          "Explain the specific decision: Coordinate chosen name, public story and skeptical observers",
          "Define the applicable contract and limits for Character rewrites own myth",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate chosen name, public story and skeptical observers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate chosen name, public story and skeptical observers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:715",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-bound-oath-breach",
      "slug": "name-bound-oath-breach",
      "name": "Name bound oath breach",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-bound-oath-breach/",
        "ja": "/ja/tools/name-bound-oath-breach/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Define breach detection and consequences under authored rules",
      "task": "Define breach detection and consequences under authored rules",
      "searchIntent": {
        "primary": "Complete the task: Define breach detection and consequences under authored rules",
        "queryHypothesis": "name bound oath breach",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define breach detection and consequences under authored rules?",
        "When should name bound oath breach be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define breach detection and consequences under authored rules",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define breach detection and consequences under authored rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-oath-name-contract",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Define breach detection and consequences under authored rules versus Define invented magical name permissions in player readable terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-guild-apprentice-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define breach detection and consequences under authored rules versus Track entry, mastery and departure forms under authored guild rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-noble-title-system",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Define breach detection and consequences under authored rules versus Define ranked titles using authored rules rather than historical claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define breach detection and consequences under authored rules",
        "outline": [
          "Explain the specific decision: Define breach detection and consequences under authored rules",
          "Define the applicable contract and limits for Name bound oath breach",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define breach detection and consequences under authored rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define breach detection and consequences under authored rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:716",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-collective-name-succession",
      "slug": "collective-name-succession",
      "name": "Collective name succession",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/collective-name-succession/",
        "ja": "/ja/tools/collective-name-succession/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Transfer a communal identity without erasing individual histories",
      "task": "Transfer a communal identity without erasing individual histories",
      "searchIntent": {
        "primary": "Complete the task: Transfer a communal identity without erasing individual histories",
        "queryHypothesis": "collective name succession",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to transfer a communal identity without erasing individual histories?",
        "When should collective name succession be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Transfer a communal identity without erasing individual histories",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Transfer a communal identity without erasing individual histories. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.2363636363636364,
          "sharedProfile": false,
          "difference": "Transfer a communal identity without erasing individual histories versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Transfer a communal identity without erasing individual histories versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-collective-identity-names",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Transfer a communal identity without erasing individual histories versus Name members whose society treats identity as shared; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Transfer a communal identity without erasing individual histories",
        "outline": [
          "Explain the specific decision: Transfer a communal identity without erasing individual histories",
          "Define the applicable contract and limits for Collective name succession",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Transfer a communal identity without erasing individual histories; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Transfer a communal identity without erasing individual histories",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:717",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-magic-privacy-boundary",
      "slug": "name-magic-privacy-boundary",
      "name": "Name magic privacy boundary",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-magic-privacy-boundary/",
        "ja": "/ja/tools/name-magic-privacy-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Define information access without implying real magical practices",
      "task": "Define information access without implying real magical practices",
      "searchIntent": {
        "primary": "Complete the task: Define information access without implying real magical practices",
        "queryHypothesis": "name magic privacy boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define information access without implying real magical practices?",
        "When should name magic privacy boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define information access without implying real magical practices",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define information access without implying real magical practices. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define information access without implying real magical practices versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-real-person-name-boundary",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Define information access without implying real magical practices versus Separate a fictional character from a real person's biography; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-oath-name-contract",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Define information access without implying real magical practices versus Define invented magical name permissions in player readable terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define information access without implying real magical practices",
        "outline": [
          "Explain the specific decision: Define information access without implying real magical practices",
          "Define the applicable contract and limits for Name magic privacy boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define information access without implying real magical practices; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define information access without implying real magical practices",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:718",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-fictional-naming-law-conflict",
      "slug": "fictional-naming-law-conflict",
      "name": "Fictional naming law conflict",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/fictional-naming-law-conflict/",
        "ja": "/ja/tools/fictional-naming-law-conflict/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Compare individual preference with an invented institution's demands",
      "task": "Compare individual preference with an invented institution's demands",
      "searchIntent": {
        "primary": "Complete the task: Compare individual preference with an invented institution's demands",
        "queryHypothesis": "fictional naming law conflict",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare individual preference with an invented institution's demands?",
        "When should fictional naming law conflict be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare individual preference with an invented institution's demands",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare individual preference with an invented institution's demands. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-familiar-chosen-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare individual preference with an invented institution's demands versus Distinguish the creature's preference from a name imposed by a summoner; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastic-fictional-name-change",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare individual preference with an invented institution's demands versus Tie name adoption to an invented order's explicit practice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-adoption-naming",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare individual preference with an invented institution's demands versus Integrate an outsider into an invented clan's explicit rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare individual preference with an invented institution's demands",
        "outline": [
          "Explain the specific decision: Compare individual preference with an invented institution's demands",
          "Define the applicable contract and limits for Fictional naming law conflict",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare individual preference with an invented institution's demands; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare individual preference with an invented institution's demands",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:719",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-restoration-ending",
      "slug": "name-restoration-ending",
      "name": "Name restoration ending",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-restoration-ending/",
        "ja": "/ja/tools/name-restoration-ending/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Trace what restoring a name repairs and what remains changed",
      "task": "Trace what restoring a name repairs and what remains changed",
      "searchIntent": {
        "primary": "Complete the task: Trace what restoring a name repairs and what remains changed",
        "queryHypothesis": "name restoration ending",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace what restoring a name repairs and what remains changed?",
        "When should name restoration ending be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace what restoring a name repairs and what remains changed",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace what restoring a name repairs and what remains changed. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-accepts-unwanted-nickname",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Trace what restoring a name repairs and what remains changed versus Trace changed meaning and remaining boundaries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-ending-signature",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Trace what restoring a name repairs and what remains changed versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-rename-counterfactual",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Trace what restoring a name repairs and what remains changed versus Trace what changes if one major name is replaced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace what restoring a name repairs and what remains changed",
        "outline": [
          "Explain the specific decision: Trace what restoring a name repairs and what remains changed",
          "Define the applicable contract and limits for Name restoration ending",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace what restoring a name repairs and what remains changed; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace what restoring a name repairs and what remains changed",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:720",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-prophecy-title-spoiler",
      "slug": "prophecy-title-spoiler",
      "name": "Prophecy title spoiler",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/prophecy-title-spoiler/",
        "ja": "/ja/tools/prophecy-title-spoiler/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Avoid exposing the future role in early character labels",
      "task": "Avoid exposing the future role in early character labels",
      "searchIntent": {
        "primary": "Complete the task: Avoid exposing the future role in early character labels",
        "queryHypothesis": "prophecy title spoiler",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid exposing the future role in early character labels?",
        "When should prophecy title spoiler be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid exposing the future role in early character labels",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid exposing the future role in early character labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Avoid exposing the future role in early character labels versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Avoid exposing the future role in early character labels versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-chapter-title-name-spoiler",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Avoid exposing the future role in early character labels versus Evaluate a title against the reader's current identity knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid exposing the future role in early character labels",
        "outline": [
          "Explain the specific decision: Avoid exposing the future role in early character labels",
          "Define the applicable contract and limits for Prophecy title spoiler",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid exposing the future role in early character labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid exposing the future role in early character labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:721",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-ritual-viewpoint",
      "slug": "name-ritual-viewpoint",
      "name": "Name ritual viewpoint",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-ritual-viewpoint/",
        "ja": "/ja/tools/name-ritual-viewpoint/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Show how participants interpret the same ceremony differently",
      "task": "Show how participants interpret the same ceremony differently",
      "searchIntent": {
        "primary": "Complete the task: Show how participants interpret the same ceremony differently",
        "queryHypothesis": "name ritual viewpoint",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show how participants interpret the same ceremony differently?",
        "When should name ritual viewpoint be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show how participants interpret the same ceremony differently",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show how participants interpret the same ceremony differently. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-mourning-name-ritual",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Show how participants interpret the same ceremony differently versus Tie memorial references to authored relationships and beliefs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Show how participants interpret the same ceremony differently versus Show how a remembered form reveals relationship history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unnamed-character-viewpoint-exercise",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Show how participants interpret the same ceremony differently versus Compare intimacy and distance without adding a name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show how participants interpret the same ceremony differently",
        "outline": [
          "Explain the specific decision: Show how participants interpret the same ceremony differently",
          "Define the applicable contract and limits for Name ritual viewpoint",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show how participants interpret the same ceremony differently; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show how participants interpret the same ceremony differently",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:722",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-name-bargain-witness-ledger",
      "slug": "name-bargain-witness-ledger",
      "name": "Name bargain witness ledger",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/name-bargain-witness-ledger/",
        "ja": "/ja/tools/name-bargain-witness-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Record who witnessed a pact and which terms they know",
      "task": "Record who witnessed a pact and which terms they know",
      "searchIntent": {
        "primary": "Complete the task: Record who witnessed a pact and which terms they know",
        "queryHypothesis": "name bargain witness ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record who witnessed a pact and which terms they know?",
        "When should name bargain witness ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record who witnessed a pact and which terms they know",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record who witnessed a pact and which terms they know. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-quest-witness-name-ledger",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Record who witnessed a pact and which terms they know versus Prevent logs from revealing identities the player has not learned; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-private-nickname-clue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Record who witnessed a pact and which terms they know versus Track the restricted group who could know the name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sacred-name-avoidance",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Record who witnessed a pact and which terms they know versus Define who may speak which name in which context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record who witnessed a pact and which terms they know",
        "outline": [
          "Explain the specific decision: Record who witnessed a pact and which terms they know",
          "Define the applicable contract and limits for Name bargain witness ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record who witnessed a pact and which terms they know; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record who witnessed a pact and which terms they know",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:723",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-speculative-identity-rule-audit",
      "slug": "speculative-identity-rule-audit",
      "name": "Speculative identity rule audit",
      "category": "speculative-plots",
      "urls": {
        "en": "/en/tools/speculative-identity-rule-audit/",
        "ja": "/ja/tools/speculative-identity-rule-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "speculative novel and comic creators",
      "scenario": "Test contradictory outcomes across name driven plot events",
      "task": "Test contradictory outcomes across name driven plot events",
      "searchIntent": {
        "primary": "Complete the task: Test contradictory outcomes across name driven plot events",
        "queryHypothesis": "speculative identity rule audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test contradictory outcomes across name driven plot events?",
        "When should speculative identity rule audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional name power contract: define consequences",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "identity and observer state: resolve targets",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: test loopholes",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims"
      ],
      "requiredData": [
        {
          "description": "original magic rule table",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "plot event fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity and knowledge ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test contradictory outcomes across name driven plot events",
        "effects follow the disclosed fictional rule rather than author convenience",
        "separate magical fiction from real world claims",
        "Proposed category workflow: fictional contract → event tests → loophole review → scene proof",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "rule bound identity effects",
        "contradictions and loopholes",
        "counterfactual scene consequences"
      ],
      "capabilities": [
        "replay one event under alternate name choices",
        "test limits and exceptions against all declared plot events"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test contradictory outcomes across name driven plot events. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-rule-migration",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Test contradictory outcomes across name driven plot events versus Compare outcomes before adopting a new shared naming grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-consistency-audit",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Test contradictory outcomes across name driven plot events versus Find mismatched author forms across a supplied publication list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-maximum-expansion",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Test contradictory outcomes across name driven plot events versus Test worst case localized names across declared UI components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test contradictory outcomes across name driven plot events",
        "outline": [
          "Explain the specific decision: Test contradictory outcomes across name driven plot events",
          "Define the applicable contract and limits for Speculative identity rule audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test contradictory outcomes across name driven plot events; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test contradictory outcomes across name driven plot events",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:724",
      "profileSource": "data/profiles.json#speculative-plots"
    },
    {
      "id": "nw-coming-of-age-chosen-name",
      "slug": "coming-of-age-chosen-name",
      "name": "Coming of age chosen name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/coming-of-age-chosen-name/",
        "ja": "/ja/tools/coming-of-age-chosen-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Connect a name decision to a specific act of agency",
      "task": "Connect a name decision to a specific act of agency",
      "searchIntent": {
        "primary": "Complete the task: Connect a name decision to a specific act of agency",
        "queryHypothesis": "coming of age chosen name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect a name decision to a specific act of agency?",
        "When should coming of age chosen name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect a name decision to a specific act of agency",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect a name decision to a specific act of agency. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Connect a name decision to a specific act of agency versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-names-a-child",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Connect a name decision to a specific act of agency versus Connect the decision to earlier experiences without assuming resolution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-age-cohort-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Connect a name decision to a specific act of agency versus Match fictional birth timing to sourced cohort data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect a name decision to a specific act of agency",
        "outline": [
          "Explain the specific decision: Connect a name decision to a specific act of agency",
          "Define the applicable contract and limits for Coming of age chosen name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect a name decision to a specific act of agency; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect a name decision to a specific act of agency",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:727",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-rejects-family-name",
      "slug": "character-rejects-family-name",
      "name": "Character rejects family name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-rejects-family-name/",
        "ja": "/ja/tools/character-rejects-family-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Track practical and relational consequences in authored scenes",
      "task": "Track practical and relational consequences in authored scenes",
      "searchIntent": {
        "primary": "Complete the task: Track practical and relational consequences in authored scenes",
        "queryHypothesis": "character rejects family name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track practical and relational consequences in authored scenes?",
        "When should character rejects family name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track practical and relational consequences in authored scenes",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track practical and relational consequences in authored scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-generational-confusion-audit",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Track practical and relational consequences in authored scenes versus Detect repeated name references in dated scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Track practical and relational consequences in authored scenes versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-memorial-naming",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track practical and relational consequences in authored scenes versus Track whom a child is named for and who knows the connection; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track practical and relational consequences in authored scenes",
        "outline": [
          "Explain the specific decision: Track practical and relational consequences in authored scenes",
          "Define the applicable contract and limits for Character rejects family name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track practical and relational consequences in authored scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track practical and relational consequences in authored scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:728",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-returns-to-family-name",
      "slug": "character-returns-to-family-name",
      "name": "Character returns to family name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-returns-to-family-name/",
        "ja": "/ja/tools/character-returns-to-family-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Distinguish reconciliation from pressure to conform",
      "task": "Distinguish reconciliation from pressure to conform",
      "searchIntent": {
        "primary": "Complete the task: Distinguish reconciliation from pressure to conform",
        "queryHypothesis": "character returns to family name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish reconciliation from pressure to conform?",
        "When should character returns to family name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish reconciliation from pressure to conform",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish reconciliation from pressure to conform. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-after-survival",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Distinguish reconciliation from pressure to conform versus Distinguish continuity, reinvention and survivor pressure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-family-name",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Distinguish reconciliation from pressure to conform versus Track practical and relational consequences in authored scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-memorial-naming",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Distinguish reconciliation from pressure to conform versus Track whom a child is named for and who knows the connection; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish reconciliation from pressure to conform",
        "outline": [
          "Explain the specific decision: Distinguish reconciliation from pressure to conform",
          "Define the applicable contract and limits for Character returns to family name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish reconciliation from pressure to conform; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish reconciliation from pressure to conform",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:729",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-embraces-ordinary-name",
      "slug": "character-embraces-ordinary-name",
      "name": "Character embraces ordinary name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-embraces-ordinary-name/",
        "ja": "/ja/tools/character-embraces-ordinary-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Build an arc without equating unusual names with depth",
      "task": "Build an arc without equating unusual names with depth",
      "searchIntent": {
        "primary": "Complete the task: Build an arc without equating unusual names with depth",
        "queryHypothesis": "character embraces ordinary name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build an arc without equating unusual names with depth?",
        "When should character embraces ordinary name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build an arc without equating unusual names with depth",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build an arc without equating unusual names with depth. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-commoner-register",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Build an arc without equating unusual names with depth versus Define structural differences without equating status and virtue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-unnamed-character-viewpoint-exercise",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Build an arc without equating unusual names with depth versus Compare intimacy and distance without adding a name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-only-identity-introduction",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Build an arc without equating unusual names with depth versus Introduce characters without relying on visual name cards; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build an arc without equating unusual names with depth",
        "outline": [
          "Explain the specific decision: Build an arc without equating unusual names with depth",
          "Define the applicable contract and limits for Character embraces ordinary name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build an arc without equating unusual names with depth; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build an arc without equating unusual names with depth",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:730",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-abandons-heroic-title",
      "slug": "character-abandons-heroic-title",
      "name": "Character abandons heroic title",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-abandons-heroic-title/",
        "ja": "/ja/tools/character-abandons-heroic-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Show identity beyond an earned public role",
      "task": "Show identity beyond an earned public role",
      "searchIntent": {
        "primary": "Complete the task: Show identity beyond an earned public role",
        "queryHypothesis": "character abandons heroic title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show identity beyond an earned public role?",
        "When should character abandons heroic title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show identity beyond an earned public role",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show identity beyond an earned public role. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Show identity beyond an earned public role versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-occupation-name-separation",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Show identity beyond an earned public role versus Keep role titles from replacing individual identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Show identity beyond an earned public role versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show identity beyond an earned public role",
        "outline": [
          "Explain the specific decision: Show identity beyond an earned public role",
          "Define the applicable contract and limits for Character abandons heroic title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show identity beyond an earned public role; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show identity beyond an earned public role",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:731",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-accepts-unwanted-nickname",
      "slug": "character-accepts-unwanted-nickname",
      "name": "Character accepts unwanted nickname",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-accepts-unwanted-nickname/",
        "ja": "/ja/tools/character-accepts-unwanted-nickname/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Trace changed meaning and remaining boundaries",
      "task": "Trace changed meaning and remaining boundaries",
      "searchIntent": {
        "primary": "Complete the task: Trace changed meaning and remaining boundaries",
        "queryHypothesis": "character accepts unwanted nickname",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace changed meaning and remaining boundaries?",
        "When should character accepts unwanted nickname be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace changed meaning and remaining boundaries",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace changed meaning and remaining boundaries. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-restoration-ending",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Trace changed meaning and remaining boundaries versus Trace what restoring a name repairs and what remains changed; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-nickname-notification",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Trace changed meaning and remaining boundaries versus Announce a changed name in a way players can understand; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Trace changed meaning and remaining boundaries versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace changed meaning and remaining boundaries",
        "outline": [
          "Explain the specific decision: Trace changed meaning and remaining boundaries",
          "Define the applicable contract and limits for Character accepts unwanted nickname",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace changed meaning and remaining boundaries; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace changed meaning and remaining boundaries",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:732",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-reclaims-intimate-name",
      "slug": "character-reclaims-intimate-name",
      "name": "Character reclaims intimate name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-reclaims-intimate-name/",
        "ja": "/ja/tools/character-reclaims-intimate-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Identify whose use becomes welcome and why",
      "task": "Identify whose use becomes welcome and why",
      "searchIntent": {
        "primary": "Complete the task: Identify whose use becomes welcome and why",
        "queryHypothesis": "character reclaims intimate name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify whose use becomes welcome and why?",
        "When should character reclaims intimate name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify whose use becomes welcome and why",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify whose use becomes welcome and why. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-namesake-ambiguity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Identify whose use becomes welcome and why versus Identify repeated names whose referents require context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-setting-name-rule-exception-map",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Identify whose use becomes welcome and why versus Identify which characters violate local rules and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-intimate-nickname-boundaries",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Identify whose use becomes welcome and why versus Restrict private names to authorized speakers and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify whose use becomes welcome and why",
        "outline": [
          "Explain the specific decision: Identify whose use becomes welcome and why",
          "Define the applicable contract and limits for Character reclaims intimate name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify whose use becomes welcome and why; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify whose use becomes welcome and why",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:733",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-changes-surname-after-exile",
      "slug": "character-changes-surname-after-exile",
      "name": "Character changes surname after exile",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-changes-surname-after-exile/",
        "ja": "/ja/tools/character-changes-surname-after-exile/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Preserve continuity across home and adopted communities",
      "task": "Preserve continuity across home and adopted communities",
      "searchIntent": {
        "primary": "Complete the task: Preserve continuity across home and adopted communities",
        "queryHypothesis": "character changes surname after exile",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve continuity across home and adopted communities?",
        "When should character changes surname after exile be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve continuity across home and adopted communities",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve continuity across home and adopted communities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-immortal-reputation-names",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Preserve continuity across home and adopted communities versus Track names across communities and centuries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-returning-emigrant-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Preserve continuity across home and adopted communities versus Reconcile home references with an adopted public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-survival",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Preserve continuity across home and adopted communities versus Distinguish continuity, reinvention and survivor pressure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve continuity across home and adopted communities",
        "outline": [
          "Explain the specific decision: Preserve continuity across home and adopted communities",
          "Define the applicable contract and limits for Character changes surname after exile",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve continuity across home and adopted communities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve continuity across home and adopted communities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:734",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-uses-childhood-name",
      "slug": "character-uses-childhood-name",
      "name": "Character uses childhood name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-uses-childhood-name/",
        "ja": "/ja/tools/character-uses-childhood-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Map vulnerability and selective trust in a return scene",
      "task": "Map vulnerability and selective trust in a return scene",
      "searchIntent": {
        "primary": "Complete the task: Map vulnerability and selective trust in a return scene",
        "queryHypothesis": "character uses childhood name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map vulnerability and selective trust in a return scene?",
        "When should character uses childhood name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map vulnerability and selective trust in a return scene",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map vulnerability and selective trust in a return scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Map vulnerability and selective trust in a return scene versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Map vulnerability and selective trust in a return scene versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reconciliation-name-return",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Map vulnerability and selective trust in a return scene versus Make the return of a form of address legible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map vulnerability and selective trust in a return scene",
        "outline": [
          "Explain the specific decision: Map vulnerability and selective trust in a return scene",
          "Define the applicable contract and limits for Character uses childhood name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map vulnerability and selective trust in a return scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map vulnerability and selective trust in a return scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:735",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-outgrows-stage-identity",
      "slug": "character-outgrows-stage-identity",
      "name": "Character outgrows stage identity",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-outgrows-stage-identity/",
        "ja": "/ja/tools/character-outgrows-stage-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Connect public persona change to career and self understanding",
      "task": "Connect public persona change to career and self understanding",
      "searchIntent": {
        "primary": "Complete the task: Connect public persona change to career and self understanding",
        "queryHypothesis": "character outgrows stage identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect public persona change to career and self understanding?",
        "When should character outgrows stage identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect public persona change to career and self understanding",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect public persona change to career and self understanding. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Connect public persona change to career and self understanding versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-arena-fighter-ring-name",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Connect public persona change to career and self understanding versus Connect public persona, announcer readability and private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Connect public persona change to career and self understanding versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect public persona change to career and self understanding",
        "outline": [
          "Explain the specific decision: Connect public persona change to career and self understanding",
          "Define the applicable contract and limits for Character outgrows stage identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect public persona change to career and self understanding; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect public persona change to career and self understanding",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:736",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-shares-secret-name",
      "slug": "character-shares-secret-name",
      "name": "Character shares secret name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-shares-secret-name/",
        "ja": "/ja/tools/character-shares-secret-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Make disclosure a meaningful relationship choice",
      "task": "Make disclosure a meaningful relationship choice",
      "searchIntent": {
        "primary": "Complete the task: Make disclosure a meaningful relationship choice",
        "queryHypothesis": "character shares secret name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make disclosure a meaningful relationship choice?",
        "When should character shares secret name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make disclosure a meaningful relationship choice",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make disclosure a meaningful relationship choice. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-gives-another-a-name",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Make disclosure a meaningful relationship choice versus Make consent, power and relationship explicit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-letter-salutation-clue",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Make disclosure a meaningful relationship choice versus Make an address form reveal a specific relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-sibling-alias-clues",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Make disclosure a meaningful relationship choice versus Limit overlaps that would expose a relationship prematurely; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make disclosure a meaningful relationship choice",
        "outline": [
          "Explain the specific decision: Make disclosure a meaningful relationship choice",
          "Define the applicable contract and limits for Character shares secret name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make disclosure a meaningful relationship choice; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make disclosure a meaningful relationship choice",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:737",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-refuses-name-disclosure",
      "slug": "character-refuses-name-disclosure",
      "name": "Character refuses name disclosure",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-refuses-name-disclosure/",
        "ja": "/ja/tools/character-refuses-name-disclosure/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Preserve agency while maintaining reader orientation",
      "task": "Preserve agency while maintaining reader orientation",
      "searchIntent": {
        "primary": "Complete the task: Preserve agency while maintaining reader orientation",
        "queryHypothesis": "character refuses name disclosure",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve agency while maintaining reader orientation?",
        "When should character refuses name disclosure be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve agency while maintaining reader orientation",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve agency while maintaining reader orientation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-forgotten-by-everyone",
          "score": 0.2785714285714286,
          "sharedProfile": false,
          "difference": "Preserve agency while maintaining reader orientation versus Preserve reader orientation while characters lose references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-doppelganger-cast-labeling",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Preserve agency while maintaining reader orientation versus Maintain intended likeness while preserving reader orientation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Preserve agency while maintaining reader orientation versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve agency while maintaining reader orientation",
        "outline": [
          "Explain the specific decision: Preserve agency while maintaining reader orientation",
          "Define the applicable contract and limits for Character refuses name disclosure",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve agency while maintaining reader orientation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve agency while maintaining reader orientation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:738",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-learns-ancestor-name",
      "slug": "character-learns-ancestor-name",
      "name": "Character learns ancestor name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-learns-ancestor-name/",
        "ja": "/ja/tools/character-learns-ancestor-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Separate discovery from uncritical acceptance of inheritance",
      "task": "Separate discovery from uncritical acceptance of inheritance",
      "searchIntent": {
        "primary": "Complete the task: Separate discovery from uncritical acceptance of inheritance",
        "queryHypothesis": "character learns ancestor name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate discovery from uncritical acceptance of inheritance?",
        "When should character learns ancestor name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate discovery from uncritical acceptance of inheritance",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate discovery from uncritical acceptance of inheritance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-namesake-ancestor-chain",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate discovery from uncritical acceptance of inheritance versus Show repeated names with unambiguous narrative references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-surname-construction",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate discovery from uncritical acceptance of inheritance versus Build a family identifier with explicit inheritance assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-codex-spoiler-names",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate discovery from uncritical acceptance of inheritance versus Gate names by discovery flags with explicit fallback labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate discovery from uncritical acceptance of inheritance",
        "outline": [
          "Explain the specific decision: Separate discovery from uncritical acceptance of inheritance",
          "Define the applicable contract and limits for Character learns ancestor name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate discovery from uncritical acceptance of inheritance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate discovery from uncritical acceptance of inheritance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:739",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-corrects-public-record",
      "slug": "character-corrects-public-record",
      "name": "Character corrects public record",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-corrects-public-record/",
        "ja": "/ja/tools/character-corrects-public-record/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Trace the cost and story consequences of correction",
      "task": "Trace the cost and story consequences of correction",
      "searchIntent": {
        "primary": "Complete the task: Trace the cost and story consequences of correction",
        "queryHypothesis": "character corrects public record",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace the cost and story consequences of correction?",
        "When should character corrects public record be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace the cost and story consequences of correction",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace the cost and story consequences of correction. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-fictional-penal-renaming",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Trace the cost and story consequences of correction versus Trace coercion, records and later reclamation in story context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-secret-public-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Trace the cost and story consequences of correction versus Define access to name layers within a fictional culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-investigator-public-reputation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Trace the cost and story consequences of correction versus Contrast newspaper label, professional title and self identification; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace the cost and story consequences of correction",
        "outline": [
          "Explain the specific decision: Trace the cost and story consequences of correction",
          "Define the applicable contract and limits for Character corrects public record",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace the cost and story consequences of correction; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace the cost and story consequences of correction",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:740",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-forgives-misnaming",
      "slug": "character-forgives-misnaming",
      "name": "Character forgives misnaming",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-forgives-misnaming/",
        "ja": "/ja/tools/character-forgives-misnaming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Show response and boundaries without treating forgiveness as required",
      "task": "Show response and boundaries without treating forgiveness as required",
      "searchIntent": {
        "primary": "Complete the task: Show response and boundaries without treating forgiveness as required",
        "queryHypothesis": "character forgives misnaming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show response and boundaries without treating forgiveness as required?",
        "When should character forgives misnaming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show response and boundaries without treating forgiveness as required",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show response and boundaries without treating forgiveness as required. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-deliberate-misnaming-scene",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Show response and boundaries without treating forgiveness as required versus Track intent, harm and response without normalizing the act; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-anonymous-service-arc",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Show response and boundaries without treating forgiveness as required versus Show the choice to act without seeking a named reputation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-stutter-name-policy",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Show response and boundaries without treating forgiveness as required versus Record deliberate performance choices without treating disability as a naming trope; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show response and boundaries without treating forgiveness as required",
        "outline": [
          "Explain the specific decision: Show response and boundaries without treating forgiveness as required",
          "Define the applicable contract and limits for Character forgives misnaming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show response and boundaries without treating forgiveness as required; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show response and boundaries without treating forgiveness as required",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:741",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-rejects-imposed-title",
      "slug": "character-rejects-imposed-title",
      "name": "Character rejects imposed title",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-rejects-imposed-title/",
        "ja": "/ja/tools/character-rejects-imposed-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Distinguish self naming from outsiders' reputation labels",
      "task": "Distinguish self naming from outsiders' reputation labels",
      "searchIntent": {
        "primary": "Complete the task: Distinguish self naming from outsiders' reputation labels",
        "queryHypothesis": "character rejects imposed title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish self naming from outsiders' reputation labels?",
        "When should character rejects imposed title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish self naming from outsiders' reputation labels",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish self naming from outsiders' reputation labels. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.24404761904761904,
          "sharedProfile": false,
          "difference": "Distinguish self naming from outsiders' reputation labels versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Distinguish self naming from outsiders' reputation labels versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish self naming from outsiders' reputation labels versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish self naming from outsiders' reputation labels",
        "outline": [
          "Explain the specific decision: Distinguish self naming from outsiders' reputation labels",
          "Define the applicable contract and limits for Character rejects imposed title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish self naming from outsiders' reputation labels; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish self naming from outsiders' reputation labels",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:742",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-loses-naming-authority",
      "slug": "character-loses-naming-authority",
      "name": "Character loses naming authority",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-loses-naming-authority/",
        "ja": "/ja/tools/character-loses-naming-authority/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Track who controls labels and how that power shifts",
      "task": "Track who controls labels and how that power shifts",
      "searchIntent": {
        "primary": "Complete the task: Track who controls labels and how that power shifts",
        "queryHypothesis": "character loses naming authority",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track who controls labels and how that power shifts?",
        "When should character loses naming authority be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track who controls labels and how that power shifts",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track who controls labels and how that power shifts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-god-loses-worship-name",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Track who controls labels and how that power shifts versus Track changes in reference, power and remembered identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shared-campaign-naming-authority",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Track who controls labels and how that power shifts versus Record who may introduce or revise each naming rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-gang-imposed-nicknames",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Track who controls labels and how that power shifts versus Show power and refusal rather than treating labels as neutral; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track who controls labels and how that power shifts",
        "outline": [
          "Explain the specific decision: Track who controls labels and how that power shifts",
          "Define the applicable contract and limits for Character loses naming authority",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track who controls labels and how that power shifts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track who controls labels and how that power shifts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:743",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-gives-another-a-name",
      "slug": "character-gives-another-a-name",
      "name": "Character gives another a name",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-gives-another-a-name/",
        "ja": "/ja/tools/character-gives-another-a-name/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Make consent, power and relationship explicit",
      "task": "Make consent, power and relationship explicit",
      "searchIntent": {
        "primary": "Complete the task: Make consent, power and relationship explicit",
        "queryHypothesis": "character gives another a name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make consent, power and relationship explicit?",
        "When should character gives another a name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make consent, power and relationship explicit",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make consent, power and relationship explicit. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-shares-secret-name",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Make consent, power and relationship explicit versus Make disclosure a meaningful relationship choice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-letter-salutation-clue",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Make consent, power and relationship explicit versus Make an address form reveal a specific relationship; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Make consent, power and relationship explicit versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make consent, power and relationship explicit",
        "outline": [
          "Explain the specific decision: Make consent, power and relationship explicit",
          "Define the applicable contract and limits for Character gives another a name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make consent, power and relationship explicit; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make consent, power and relationship explicit",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:744",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-apologizes-through-address",
      "slug": "character-apologizes-through-address",
      "name": "Character apologizes through address",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-apologizes-through-address/",
        "ja": "/ja/tools/character-apologizes-through-address/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Compare a changed vocative with an earned behavioral change",
      "task": "Compare a changed vocative with an earned behavioral change",
      "searchIntent": {
        "primary": "Complete the task: Compare a changed vocative with an earned behavioral change",
        "queryHypothesis": "character apologizes through address",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare a changed vocative with an earned behavioral change?",
        "When should character apologizes through address be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare a changed vocative with an earned behavioral change",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare a changed vocative with an earned behavioral change. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-arc-scene-checklist",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Compare a changed vocative with an earned behavioral change versus Link every address change to an earned story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare a changed vocative with an earned behavioral change versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-accepts-unwanted-nickname",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Compare a changed vocative with an earned behavioral change versus Trace changed meaning and remaining boundaries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare a changed vocative with an earned behavioral change",
        "outline": [
          "Explain the specific decision: Compare a changed vocative with an earned behavioral change",
          "Define the applicable contract and limits for Character apologizes through address",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare a changed vocative with an earned behavioral change; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare a changed vocative with an earned behavioral change",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:745",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-name-after-betrayal",
      "slug": "character-name-after-betrayal",
      "name": "Character name after betrayal",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-name-after-betrayal/",
        "ja": "/ja/tools/character-name-after-betrayal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Map who retains or rejects earlier intimate forms",
      "task": "Map who retains or rejects earlier intimate forms",
      "searchIntent": {
        "primary": "Complete the task: Map who retains or rejects earlier intimate forms",
        "queryHypothesis": "character name after betrayal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map who retains or rejects earlier intimate forms?",
        "When should character name after betrayal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map who retains or rejects earlier intimate forms",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map who retains or rejects earlier intimate forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-villain-public-moniker",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Map who retains or rejects earlier intimate forms versus Track who coined the name and who rejects it; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shapeshifter-form-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Map who retains or rejects earlier intimate forms versus Map physical forms to stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-border-town-name-register",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Map who retains or rejects earlier intimate forms versus Map local and official forms across a fictional frontier; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map who retains or rejects earlier intimate forms",
        "outline": [
          "Explain the specific decision: Map who retains or rejects earlier intimate forms",
          "Define the applicable contract and limits for Character name after betrayal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map who retains or rejects earlier intimate forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map who retains or rejects earlier intimate forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:746",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-name-after-rescue",
      "slug": "character-name-after-rescue",
      "name": "Character name after rescue",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-name-after-rescue/",
        "ja": "/ja/tools/character-name-after-rescue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Avoid reducing a rescued character to a rescuer assigned label",
      "task": "Avoid reducing a rescued character to a rescuer assigned label",
      "searchIntent": {
        "primary": "Complete the task: Avoid reducing a rescued character to a rescuer assigned label",
        "queryHypothesis": "character name after rescue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid reducing a rescued character to a rescuer assigned label?",
        "When should character name after rescue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid reducing a rescued character to a rescuer assigned label",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid reducing a rescued character to a rescuer assigned label. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-amnesiac-placeholder-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Avoid reducing a rescued character to a rescuer assigned label versus Transition from assigned label to recovered or chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-betrayal",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Avoid reducing a rescued character to a rescuer assigned label versus Map who retains or rejects earlier intimate forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-survival",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Avoid reducing a rescued character to a rescuer assigned label versus Distinguish continuity, reinvention and survivor pressure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid reducing a rescued character to a rescuer assigned label",
        "outline": [
          "Explain the specific decision: Avoid reducing a rescued character to a rescuer assigned label",
          "Define the applicable contract and limits for Character name after rescue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid reducing a rescued character to a rescuer assigned label; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid reducing a rescued character to a rescuer assigned label",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:747",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-mourning-name-ritual",
      "slug": "character-mourning-name-ritual",
      "name": "Character mourning name ritual",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-mourning-name-ritual/",
        "ja": "/ja/tools/character-mourning-name-ritual/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Tie memorial references to authored relationships and beliefs",
      "task": "Tie memorial references to authored relationships and beliefs",
      "searchIntent": {
        "primary": "Complete the task: Tie memorial references to authored relationships and beliefs",
        "queryHypothesis": "character mourning name ritual",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie memorial references to authored relationships and beliefs?",
        "When should character mourning name ritual be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie memorial references to authored relationships and beliefs",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie memorial references to authored relationships and beliefs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-posthumous-name-rules",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Tie memorial references to authored relationships and beliefs versus Keep living and memorial references consistent; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-ritual-viewpoint",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Tie memorial references to authored relationships and beliefs versus Show how participants interpret the same ceremony differently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-editor-name-correction-sheet",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Tie memorial references to authored relationships and beliefs versus Track corrections with page and panel references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie memorial references to authored relationships and beliefs",
        "outline": [
          "Explain the specific decision: Tie memorial references to authored relationships and beliefs",
          "Define the applicable contract and limits for Character mourning name ritual",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie memorial references to authored relationships and beliefs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie memorial references to authored relationships and beliefs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:748",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-name-after-survival",
      "slug": "character-name-after-survival",
      "name": "Character name after survival",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-name-after-survival/",
        "ja": "/ja/tools/character-name-after-survival/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Distinguish continuity, reinvention and survivor pressure",
      "task": "Distinguish continuity, reinvention and survivor pressure",
      "searchIntent": {
        "primary": "Complete the task: Distinguish continuity, reinvention and survivor pressure",
        "queryHypothesis": "character name after survival",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish continuity, reinvention and survivor pressure?",
        "When should character name after survival be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish continuity, reinvention and survivor pressure",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish continuity, reinvention and survivor pressure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Distinguish continuity, reinvention and survivor pressure versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-changes-surname-after-exile",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Distinguish continuity, reinvention and survivor pressure versus Preserve continuity across home and adopted communities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-after-betrayal",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Distinguish continuity, reinvention and survivor pressure versus Map who retains or rejects earlier intimate forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish continuity, reinvention and survivor pressure",
        "outline": [
          "Explain the specific decision: Distinguish continuity, reinvention and survivor pressure",
          "Define the applicable contract and limits for Character name after survival",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish continuity, reinvention and survivor pressure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish continuity, reinvention and survivor pressure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:749",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-identity-under-fame",
      "slug": "character-identity-under-fame",
      "name": "Character identity under fame",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-identity-under-fame/",
        "ja": "/ja/tools/character-identity-under-fame/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Separate public shorthand from private relationship forms",
      "task": "Separate public shorthand from private relationship forms",
      "searchIntent": {
        "primary": "Complete the task: Separate public shorthand from private relationship forms",
        "queryHypothesis": "character identity under fame",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate public shorthand from private relationship forms?",
        "When should character identity under fame be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate public shorthand from private relationship forms",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate public shorthand from private relationship forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-companion-nickname-unlock",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Separate public shorthand from private relationship forms versus Tie private address forms to explicit relationship flags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-heist-crew-identity-matrix",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Separate public shorthand from private relationship forms versus Align crew handles with public and private identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Separate public shorthand from private relationship forms versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate public shorthand from private relationship forms",
        "outline": [
          "Explain the specific decision: Separate public shorthand from private relationship forms",
          "Define the applicable contract and limits for Character identity under fame",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate public shorthand from private relationship forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate public shorthand from private relationship forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:750",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-anonymous-service-arc",
      "slug": "character-anonymous-service-arc",
      "name": "Character anonymous service arc",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-anonymous-service-arc/",
        "ja": "/ja/tools/character-anonymous-service-arc/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Show the choice to act without seeking a named reputation",
      "task": "Show the choice to act without seeking a named reputation",
      "searchIntent": {
        "primary": "Complete the task: Show the choice to act without seeking a named reputation",
        "queryHypothesis": "character anonymous service arc",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show the choice to act without seeking a named reputation?",
        "When should character anonymous service arc be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show the choice to act without seeking a named reputation",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show the choice to act without seeking a named reputation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-anonymous-publication-byline",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Show the choice to act without seeking a named reputation versus Compare anonymity language and reader expectations without privacy guarantees; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-deliberate-misnaming-scene",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Show the choice to act without seeking a named reputation versus Track intent, harm and response without normalizing the act; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-alternative-ending",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Show the choice to act without seeking a named reputation versus Compare how a final naming choice changes the story's implied resolution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show the choice to act without seeking a named reputation",
        "outline": [
          "Explain the specific decision: Show the choice to act without seeking a named reputation",
          "Define the applicable contract and limits for Character anonymous service arc",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show the choice to act without seeking a named reputation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show the choice to act without seeking a named reputation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:751",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-passes-on-title",
      "slug": "character-passes-on-title",
      "name": "Character passes on title",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-passes-on-title/",
        "ja": "/ja/tools/character-passes-on-title/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Preserve the outgoing and incoming holders' distinct identities",
      "task": "Preserve the outgoing and incoming holders' distinct identities",
      "searchIntent": {
        "primary": "Complete the task: Preserve the outgoing and incoming holders' distinct identities",
        "queryHypothesis": "character passes on title",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve the outgoing and incoming holders' distinct identities?",
        "When should character passes on title be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve the outgoing and incoming holders' distinct identities",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve the outgoing and incoming holders' distinct identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-cue-name-system",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Preserve the outgoing and incoming holders' distinct identities versus Keep production cues distinct from spoken identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-title-inheritance",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Preserve the outgoing and incoming holders' distinct identities versus Transfer a shared public identity without collapsing individual holders; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inherited-questgiver-title",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Preserve the outgoing and incoming holders' distinct identities versus Transfer office without merging save identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve the outgoing and incoming holders' distinct identities",
        "outline": [
          "Explain the specific decision: Preserve the outgoing and incoming holders' distinct identities",
          "Define the applicable contract and limits for Character passes on title",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve the outgoing and incoming holders' distinct identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve the outgoing and incoming holders' distinct identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:752",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-names-a-child",
      "slug": "character-names-a-child",
      "name": "Character names a child",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-names-a-child/",
        "ja": "/ja/tools/character-names-a-child/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Connect the decision to earlier experiences without assuming resolution",
      "task": "Connect the decision to earlier experiences without assuming resolution",
      "searchIntent": {
        "primary": "Complete the task: Connect the decision to earlier experiences without assuming resolution",
        "queryHypothesis": "character names a child",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect the decision to earlier experiences without assuming resolution?",
        "When should character names a child be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect the decision to earlier experiences without assuming resolution",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect the decision to earlier experiences without assuming resolution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-coming-of-age-chosen-name",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Connect the decision to earlier experiences without assuming resolution versus Connect a name decision to a specific act of agency; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-family-repeated-kanji",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Connect the decision to earlier experiences without assuming resolution versus Track shared characters without assuming universal family practice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Connect the decision to earlier experiences without assuming resolution versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect the decision to earlier experiences without assuming resolution",
        "outline": [
          "Explain the specific decision: Connect the decision to earlier experiences without assuming resolution",
          "Define the applicable contract and limits for Character names a child",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect the decision to earlier experiences without assuming resolution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect the decision to earlier experiences without assuming resolution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:753",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-breaks-namesake-cycle",
      "slug": "character-breaks-namesake-cycle",
      "name": "Character breaks namesake cycle",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-breaks-namesake-cycle/",
        "ja": "/ja/tools/character-breaks-namesake-cycle/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Show the deliberate rejection of a repeated family pattern",
      "task": "Show the deliberate rejection of a repeated family pattern",
      "searchIntent": {
        "primary": "Complete the task: Show the deliberate rejection of a repeated family pattern",
        "queryHypothesis": "character breaks namesake cycle",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show the deliberate rejection of a repeated family pattern?",
        "When should character breaks namesake cycle be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show the deliberate rejection of a repeated family pattern",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show the deliberate rejection of a repeated family pattern. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-namesake-ancestor-chain",
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Show the deliberate rejection of a repeated family pattern versus Show repeated names with unambiguous narrative references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-namesake-ambiguity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Show the deliberate rejection of a repeated family pattern versus Identify repeated names whose referents require context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Show the deliberate rejection of a repeated family pattern versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show the deliberate rejection of a repeated family pattern",
        "outline": [
          "Explain the specific decision: Show the deliberate rejection of a repeated family pattern",
          "Define the applicable contract and limits for Character breaks namesake cycle",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show the deliberate rejection of a repeated family pattern; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show the deliberate rejection of a repeated family pattern",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:754",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-reconciles-dual-identities",
      "slug": "character-reconciles-dual-identities",
      "name": "Character reconciles dual identities",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-reconciles-dual-identities/",
        "ja": "/ja/tools/character-reconciles-dual-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Define which differences remain after integration",
      "task": "Define which differences remain after integration",
      "searchIntent": {
        "primary": "Complete the task: Define which differences remain after integration",
        "queryHypothesis": "character reconciles dual identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define which differences remain after integration?",
        "When should character reconciles dual identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define which differences remain after integration",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define which differences remain after integration. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-player-renaming-story-integration",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define which differences remain after integration versus Define which dialogue and records update after renaming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-expelled-member-references",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Define which differences remain after integration versus Record which titles cease and which personal names remain; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sacred-name-avoidance",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define which differences remain after integration versus Define who may speak which name in which context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define which differences remain after integration",
        "outline": [
          "Explain the specific decision: Define which differences remain after integration",
          "Define the applicable contract and limits for Character reconciles dual identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define which differences remain after integration; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define which differences remain after integration",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:755",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-character-ending-signature",
      "slug": "character-ending-signature",
      "name": "Character ending signature",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/character-ending-signature/",
        "ja": "/ja/tools/character-ending-signature/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Compare the final signature with the opening identity state",
      "task": "Compare the final signature with the opening identity state",
      "searchIntent": {
        "primary": "Complete the task: Compare the final signature with the opening identity state",
        "queryHypothesis": "character ending signature",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare the final signature with the opening identity state?",
        "When should character ending signature be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare the final signature with the opening identity state",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare the final signature with the opening identity state. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-signature-ending-exercise",
          "score": 0.37777777777777777,
          "sharedProfile": false,
          "difference": "Compare the final signature with the opening identity state versus Revise a final signature to reflect an established character arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-signature-consistency",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Compare the final signature with the opening identity state versus Keep a drawn signature recognizable across localized editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-names-as-citizenship",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare the final signature with the opening identity state versus Separate state assigned recognition from self identity in a fictional regime; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare the final signature with the opening identity state",
        "outline": [
          "Explain the specific decision: Compare the final signature with the opening identity state",
          "Define the applicable contract and limits for Character ending signature",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare the final signature with the opening identity state; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare the final signature with the opening identity state",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:756",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-name-arc-scene-checklist",
      "slug": "name-arc-scene-checklist",
      "name": "Name arc scene checklist",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/name-arc-scene-checklist/",
        "ja": "/ja/tools/name-arc-scene-checklist/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Link every address change to an earned story event",
      "task": "Link every address change to an earned story event",
      "searchIntent": {
        "primary": "Complete the task: Link every address change to an earned story event",
        "queryHypothesis": "name arc scene checklist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link every address change to an earned story event?",
        "When should name arc scene checklist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link every address change to an earned story event",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link every address change to an earned story event. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-in-confession-scene",
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Link every address change to an earned story event versus Control who is identified by an emotionally loaded address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Link every address change to an earned story event versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-apologizes-through-address",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Link every address change to an earned story event versus Compare a changed vocative with an earned behavioral change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link every address change to an earned story event",
        "outline": [
          "Explain the specific decision: Link every address change to an earned story event",
          "Define the applicable contract and limits for Name arc scene checklist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link every address change to an earned story event; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link every address change to an earned story event",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:757",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-name-arc-emotional-continuity",
      "slug": "name-arc-emotional-continuity",
      "name": "Name arc emotional continuity",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/name-arc-emotional-continuity/",
        "ja": "/ja/tools/name-arc-emotional-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Test whether naming changes match the surrounding character behavior",
      "task": "Test whether naming changes match the surrounding character behavior",
      "searchIntent": {
        "primary": "Complete the task: Test whether naming changes match the surrounding character behavior",
        "queryHypothesis": "name arc emotional continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test whether naming changes match the surrounding character behavior?",
        "When should name arc emotional continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test whether naming changes match the surrounding character behavior",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test whether naming changes match the surrounding character behavior. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-ship-crew-watch-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Test whether naming changes match the surrounding character behavior versus Test names under watch rotations and role changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-subtitle-romanization-continuity",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Test whether naming changes match the surrounding character behavior versus Match visible Latin spellings to the pronunciation bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-name-badge-continuity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Test whether naming changes match the surrounding character behavior versus Match art badge text to timeline and identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test whether naming changes match the surrounding character behavior",
        "outline": [
          "Explain the specific decision: Test whether naming changes match the surrounding character behavior",
          "Define the applicable contract and limits for Name arc emotional continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test whether naming changes match the surrounding character behavior; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test whether naming changes match the surrounding character behavior",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:758",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-name-arc-reader-interpretation-test",
      "slug": "name-arc-reader-interpretation-test",
      "name": "Name arc reader interpretation test",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/name-arc-reader-interpretation-test/",
        "ja": "/ja/tools/name-arc-reader-interpretation-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Collect reader explanations without claiming universal symbolism",
      "task": "Collect reader explanations without claiming universal symbolism",
      "searchIntent": {
        "primary": "Complete the task: Collect reader explanations without claiming universal symbolism",
        "queryHypothesis": "name arc reader interpretation test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect reader explanations without claiming universal symbolism?",
        "When should name arc reader interpretation test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect reader explanations without claiming universal symbolism",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect reader explanations without claiming universal symbolism. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-role-association-test",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Collect reader explanations without claiming universal symbolism versus Compare reader associations with intended role without claiming objectivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-shortlist-blind-test",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Collect reader explanations without claiming universal symbolism versus Collect unaided impressions without showing author explanations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-surname-locality-check",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Collect reader explanations without claiming universal symbolism versus Record geographic evidence without claiming universal distribution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect reader explanations without claiming universal symbolism",
        "outline": [
          "Explain the specific decision: Collect reader explanations without claiming universal symbolism",
          "Define the applicable contract and limits for Name arc reader interpretation test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect reader explanations without claiming universal symbolism; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect reader explanations without claiming universal symbolism",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:759",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-name-arc-reverse-outline",
      "slug": "name-arc-reverse-outline",
      "name": "Name arc reverse outline",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/name-arc-reverse-outline/",
        "ja": "/ja/tools/name-arc-reverse-outline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Extract a timeline of identity references from authored scenes",
      "task": "Extract a timeline of identity references from authored scenes",
      "searchIntent": {
        "primary": "Complete the task: Extract a timeline of identity references from authored scenes",
        "queryHypothesis": "name arc reverse outline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to extract a timeline of identity references from authored scenes?",
        "When should name arc reverse outline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Extract a timeline of identity references from authored scenes",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Extract a timeline of identity references from authored scenes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-generational-confusion-audit",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Extract a timeline of identity references from authored scenes versus Detect repeated name references in dated scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-order-initiation-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Extract a timeline of identity references from authored scenes versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Extract a timeline of identity references from authored scenes versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Extract a timeline of identity references from authored scenes",
        "outline": [
          "Explain the specific decision: Extract a timeline of identity references from authored scenes",
          "Define the applicable contract and limits for Name arc reverse outline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Extract a timeline of identity references from authored scenes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Extract a timeline of identity references from authored scenes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:760",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-name-arc-alternative-ending",
      "slug": "name-arc-alternative-ending",
      "name": "Name arc alternative ending",
      "category": "narrative-arcs",
      "urls": {
        "en": "/en/tools/name-arc-alternative-ending/",
        "ja": "/ja/tools/name-arc-alternative-ending/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novelists and serial storytellers",
      "scenario": "Compare how a final naming choice changes the story's implied resolution",
      "task": "Compare how a final naming choice changes the story's implied resolution",
      "searchIntent": {
        "primary": "Complete the task: Compare how a final naming choice changes the story's implied resolution",
        "queryHypothesis": "name arc alternative ending",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare how a final naming choice changes the story's implied resolution?",
        "When should name arc alternative ending be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "opening and ending identity states: define change",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "relationship milestones: earn transitions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "character choices: connect naming to agency",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event"
      ],
      "requiredData": [
        {
          "description": "author scene timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "directed relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "identity decision ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare how a final naming choice changes the story's implied resolution",
        "a changed label is not itself proof of character growth",
        "tie each new address form to an authored event",
        "Proposed category workflow: arc brief → events → scene alternatives → emotional continuity review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name arc timeline",
        "unearned transition warnings",
        "counterfactual scene comparisons"
      ],
      "capabilities": [
        "compare opening and ending reference permissions",
        "trace a name choice to practical relationship consequences"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare how a final naming choice changes the story's implied resolution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-ending-signature",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Compare how a final naming choice changes the story's implied resolution versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-emotional-continuity",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Compare how a final naming choice changes the story's implied resolution versus Test whether naming changes match the surrounding character behavior; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-signature-ending-exercise",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Compare how a final naming choice changes the story's implied resolution versus Revise a final signature to reflect an established character arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare how a final naming choice changes the story's implied resolution",
        "outline": [
          "Explain the specific decision: Compare how a final naming choice changes the story's implied resolution",
          "Define the applicable contract and limits for Name arc alternative ending",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare how a final naming choice changes the story's implied resolution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare how a final naming choice changes the story's implied resolution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:761",
      "profileSource": "data/profiles.json#narrative-arcs"
    },
    {
      "id": "nw-village-surname-ecology",
      "slug": "village-surname-ecology",
      "name": "Village surname ecology",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/village-surname-ecology/",
        "ja": "/ja/tools/village-surname-ecology/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Design personal surnames from a bounded fictional local history",
      "task": "Design personal surnames from a bounded fictional local history",
      "searchIntent": {
        "primary": "Complete the task: Design personal surnames from a bounded fictional local history",
        "queryHypothesis": "village surname ecology",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design personal surnames from a bounded fictional local history?",
        "When should village surname ecology be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design personal surnames from a bounded fictional local history",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design personal surnames from a bounded fictional local history. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-village-ensemble-name-ecology",
          "score": 0.2472222222222222,
          "sharedProfile": false,
          "difference": "Design personal surnames from a bounded fictional local history versus Balance local patterns with individual distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-surname-construction",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Design personal surnames from a bounded fictional local history versus Build a family identifier with explicit inheritance assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-court-name-forms",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Design personal surnames from a bounded fictional local history versus Record local conventions with explicit evidence limitations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design personal surnames from a bounded fictional local history",
        "outline": [
          "Explain the specific decision: Design personal surnames from a bounded fictional local history",
          "Define the applicable contract and limits for Village surname ecology",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design personal surnames from a bounded fictional local history; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design personal surnames from a bounded fictional local history",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:764",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-port-city-migrant-identities",
      "slug": "port-city-migrant-identities",
      "name": "Port city migrant identities",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/port-city-migrant-identities/",
        "ja": "/ja/tools/port-city-migrant-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Track source names and contact forms without random cultural mixing",
      "task": "Track source names and contact forms without random cultural mixing",
      "searchIntent": {
        "primary": "Complete the task: Track source names and contact forms without random cultural mixing",
        "queryHypothesis": "port city migrant identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track source names and contact forms without random cultural mixing?",
        "When should port city migrant identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track source names and contact forms without random cultural mixing",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track source names and contact forms without random cultural mixing. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-identity-matching-test",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track source names and contact forms without random cultural mixing versus Ask readers to match source and localized character forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-taboo-system",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track source names and contact forms without random cultural mixing versus Exclude prohibited forms with an explicit cultural rule ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-trade-language-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track source names and contact forms without random cultural mixing versus Create contact forms distinct from native language names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track source names and contact forms without random cultural mixing",
        "outline": [
          "Explain the specific decision: Track source names and contact forms without random cultural mixing",
          "Define the applicable contract and limits for Port city migrant identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track source names and contact forms without random cultural mixing; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track source names and contact forms without random cultural mixing",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:765",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-border-town-name-register",
      "slug": "border-town-name-register",
      "name": "Border town name register",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/border-town-name-register/",
        "ja": "/ja/tools/border-town-name-register/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Map local and official forms across a fictional frontier",
      "task": "Map local and official forms across a fictional frontier",
      "searchIntent": {
        "primary": "Complete the task: Map local and official forms across a fictional frontier",
        "queryHypothesis": "border town name register",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to map local and official forms across a fictional frontier?",
        "When should border town name register be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Map local and official forms across a fictional frontier",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Map local and official forms across a fictional frontier. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-dialogue-address-permissions",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Map local and official forms across a fictional frontier versus Map permitted address forms across all speaker pairs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-in-records",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Map local and official forms across a fictional frontier versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Map local and official forms across a fictional frontier versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Map local and official forms across a fictional frontier",
        "outline": [
          "Explain the specific decision: Map local and official forms across a fictional frontier",
          "Define the applicable contract and limits for Border town name register",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Map local and official forms across a fictional frontier; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Map local and official forms across a fictional frontier",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:766",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-capital-court-name-hierarchy",
      "slug": "capital-court-name-hierarchy",
      "name": "Capital court name hierarchy",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/capital-court-name-hierarchy/",
        "ja": "/ja/tools/capital-court-name-hierarchy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Keep citizen identity, court titles and household membership distinct",
      "task": "Keep citizen identity, court titles and household membership distinct",
      "searchIntent": {
        "primary": "Complete the task: Keep citizen identity, court titles and household membership distinct",
        "queryHypothesis": "capital court name hierarchy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep citizen identity, court titles and household membership distinct?",
        "When should capital court name hierarchy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep citizen identity, court titles and household membership distinct",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep citizen identity, court titles and household membership distinct. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep citizen identity, court titles and household membership distinct versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-space-colony-name-registry",
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Keep citizen identity, court titles and household membership distinct versus Separate habitat citizenship from personal and household identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stepfamily-address-map",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Keep citizen identity, court titles and household membership distinct versus Distinguish household membership from inherited naming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep citizen identity, court titles and household membership distinct",
        "outline": [
          "Explain the specific decision: Keep citizen identity, court titles and household membership distinct",
          "Define the applicable contract and limits for Capital court name hierarchy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep citizen identity, court titles and household membership distinct; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep citizen identity, court titles and household membership distinct",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:767",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-frontier-settlement-naming",
      "slug": "frontier-settlement-naming",
      "name": "Frontier settlement naming",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/frontier-settlement-naming/",
        "ja": "/ja/tools/frontier-settlement-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Define how newcomers retain or adapt personal identities",
      "task": "Define how newcomers retain or adapt personal identities",
      "searchIntent": {
        "primary": "Complete the task: Define how newcomers retain or adapt personal identities",
        "queryHypothesis": "frontier settlement naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define how newcomers retain or adapt personal identities?",
        "When should frontier settlement naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define how newcomers retain or adapt personal identities",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define how newcomers retain or adapt personal identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-telepathic-identity-tokens",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Define how newcomers retain or adapt personal identities versus Define how shared mental identities appear in prose; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-erasure-story-continuity",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Define how newcomers retain or adapt personal identities versus Define how records and memories change after erasure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-settlement-pronunciation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Define how newcomers retain or adapt personal identities versus Keep place derived character references consistent at the table; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define how newcomers retain or adapt personal identities",
        "outline": [
          "Explain the specific decision: Define how newcomers retain or adapt personal identities",
          "Define the applicable contract and limits for Frontier settlement naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define how newcomers retain or adapt personal identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define how newcomers retain or adapt personal identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:768",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-refugee-character-naming",
      "slug": "refugee-character-naming",
      "name": "Refugee character naming",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/refugee-character-naming/",
        "ja": "/ja/tools/refugee-character-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Preserve chosen identity without assuming displacement erases culture",
      "task": "Preserve chosen identity without assuming displacement erases culture",
      "searchIntent": {
        "primary": "Complete the task: Preserve chosen identity without assuming displacement erases culture",
        "queryHypothesis": "refugee character naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve chosen identity without assuming displacement erases culture?",
        "When should refugee character naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve chosen identity without assuming displacement erases culture",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve chosen identity without assuming displacement erases culture. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-migration-name-records",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Preserve chosen identity without assuming displacement erases culture versus Trace documented variants without assuming identity from similarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-playable-character-preset-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Preserve chosen identity without assuming displacement erases culture versus Keep defaults distinct from player chosen identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Preserve chosen identity without assuming displacement erases culture versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve chosen identity without assuming displacement erases culture",
        "outline": [
          "Explain the specific decision: Preserve chosen identity without assuming displacement erases culture",
          "Define the applicable contract and limits for Refugee character naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve chosen identity without assuming displacement erases culture; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve chosen identity without assuming displacement erases culture",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:769",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-diaspora-family-continuity",
      "slug": "diaspora-family-continuity",
      "name": "Diaspora family continuity",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/diaspora-family-continuity/",
        "ja": "/ja/tools/diaspora-family-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Track names across generations with explicit family decisions",
      "task": "Track names across generations with explicit family decisions",
      "searchIntent": {
        "primary": "Complete the task: Track names across generations with explicit family decisions",
        "queryHypothesis": "diaspora family continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track names across generations with explicit family decisions?",
        "When should diaspora family continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track names across generations with explicit family decisions",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track names across generations with explicit family decisions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-hyphenated-family-name-limits",
          "score": 0.2557142857142857,
          "sharedProfile": false,
          "difference": "Track names across generations with explicit family decisions versus Resolve accumulated surnames across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-family-continuity",
          "score": 0.24,
          "sharedProfile": false,
          "difference": "Track names across generations with explicit family decisions versus Check new relatives against established family naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-secret-name",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track names across generations with explicit family decisions versus Track knowledge transfer and failures across generations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track names across generations with explicit family decisions",
        "outline": [
          "Explain the specific decision: Track names across generations with explicit family decisions",
          "Define the applicable contract and limits for Diaspora family continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track names across generations with explicit family decisions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track names across generations with explicit family decisions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:770",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-space-colony-name-registry",
      "slug": "space-colony-name-registry",
      "name": "Space colony name registry",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/space-colony-name-registry/",
        "ja": "/ja/tools/space-colony-name-registry/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Separate habitat citizenship from personal and household identity",
      "task": "Separate habitat citizenship from personal and household identity",
      "searchIntent": {
        "primary": "Complete the task: Separate habitat citizenship from personal and household identity",
        "queryHypothesis": "space colony name registry",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate habitat citizenship from personal and household identity?",
        "When should space colony name registry be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate habitat citizenship from personal and household identity",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate habitat citizenship from personal and household identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-legal-name-layers",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Separate habitat citizenship from personal and household identity versus Separate citizenship, household and personal chosen components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-clan-branch-registry",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Separate habitat citizenship from personal and household identity versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate habitat citizenship from personal and household identity versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate habitat citizenship from personal and household identity",
        "outline": [
          "Explain the specific decision: Separate habitat citizenship from personal and household identity",
          "Define the applicable contract and limits for Space colony name registry",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate habitat citizenship from personal and household identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate habitat citizenship from personal and household identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:771",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-generation-ship-family-names",
      "slug": "generation-ship-family-names",
      "name": "Generation ship family names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/generation-ship-family-names/",
        "ja": "/ja/tools/generation-ship-family-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Model repeated names across a closed fictional population",
      "task": "Model repeated names across a closed fictional population",
      "searchIntent": {
        "primary": "Complete the task: Model repeated names across a closed fictional population",
        "queryHypothesis": "generation ship family names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model repeated names across a closed fictional population?",
        "When should generation ship family names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model repeated names across a closed fictional population",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model repeated names across a closed fictional population. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-generation-marker",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Model repeated names across a closed fictional population versus Apply an author defined generation scheme to eligible relatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-family-generation",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Model repeated names across a closed fictional population versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-name-planner",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Model repeated names across a closed fictional population versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model repeated names across a closed fictional population",
        "outline": [
          "Explain the specific decision: Model repeated names across a closed fictional population",
          "Define the applicable contract and limits for Generation ship family names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model repeated names across a closed fictional population; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model repeated names across a closed fictional population",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:772",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-space-station-transient-names",
      "slug": "space-station-transient-names",
      "name": "Space station transient names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/space-station-transient-names/",
        "ja": "/ja/tools/space-station-transient-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Reconcile visitor logs with locally used identities",
      "task": "Reconcile visitor logs with locally used identities",
      "searchIntent": {
        "primary": "Complete the task: Reconcile visitor logs with locally used identities",
        "queryHypothesis": "space station transient names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile visitor logs with locally used identities?",
        "When should space station transient names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile visitor logs with locally used identities",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile visitor logs with locally used identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-acrostic-name-clue",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile visitor logs with locally used identities versus Reconcile translated names with an acrostic used in the plot; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-quest-witness-name-ledger",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Reconcile visitor logs with locally used identities versus Prevent logs from revealing identities the player has not learned; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-lost-sibling-reunion-names",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Reconcile visitor logs with locally used identities versus Reconcile names learned in separate households; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile visitor logs with locally used identities",
        "outline": [
          "Explain the specific decision: Reconcile visitor logs with locally used identities",
          "Define the applicable contract and limits for Space station transient names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile visitor logs with locally used identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile visitor logs with locally used identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:773",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-undersea-settlement-identity",
      "slug": "undersea-settlement-identity",
      "name": "Undersea settlement identity",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/undersea-settlement-identity/",
        "ja": "/ja/tools/undersea-settlement-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Connect communication constraints to personal naming rules",
      "task": "Connect communication constraints to personal naming rules",
      "searchIntent": {
        "primary": "Complete the task: Connect communication constraints to personal naming rules",
        "queryHypothesis": "undersea settlement identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect communication constraints to personal naming rules?",
        "When should undersea settlement identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect communication constraints to personal naming rules",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect communication constraints to personal naming rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-elemental-identity-convention",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Connect communication constraints to personal naming rules versus Build explicit fictional naming rules beyond a single elemental adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Connect communication constraints to personal naming rules versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-outgrows-stage-identity",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Connect communication constraints to personal naming rules versus Connect public persona change to career and self understanding; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect communication constraints to personal naming rules",
        "outline": [
          "Explain the specific decision: Connect communication constraints to personal naming rules",
          "Define the applicable contract and limits for Undersea settlement identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect communication constraints to personal naming rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect communication constraints to personal naming rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:774",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-underground-city-personal-names",
      "slug": "underground-city-personal-names",
      "name": "Underground city personal names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/underground-city-personal-names/",
        "ja": "/ja/tools/underground-city-personal-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Distinguish civic assignments from family chosen names",
      "task": "Distinguish civic assignments from family chosen names",
      "searchIntent": {
        "primary": "Complete the task: Distinguish civic assignments from family chosen names",
        "queryHypothesis": "underground city personal names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish civic assignments from family chosen names?",
        "When should underground city personal names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish civic assignments from family chosen names",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish civic assignments from family chosen names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish civic assignments from family chosen names versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.09285714285714286,
          "sharedProfile": true,
          "difference": "Distinguish civic assignments from family chosen names versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Distinguish civic assignments from family chosen names versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish civic assignments from family chosen names",
        "outline": [
          "Explain the specific decision: Distinguish civic assignments from family chosen names",
          "Define the applicable contract and limits for Underground city personal names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish civic assignments from family chosen names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish civic assignments from family chosen names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:775",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-nomadic-fictional-naming",
      "slug": "nomadic-fictional-naming",
      "name": "Nomadic fictional naming",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/nomadic-fictional-naming/",
        "ja": "/ja/tools/nomadic-fictional-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Model travel group membership without assuming one universal nomadic custom",
      "task": "Model travel group membership without assuming one universal nomadic custom",
      "searchIntent": {
        "primary": "Complete the task: Model travel group membership without assuming one universal nomadic custom",
        "queryHypothesis": "nomadic fictional naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model travel group membership without assuming one universal nomadic custom?",
        "When should nomadic fictional naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model travel group membership without assuming one universal nomadic custom",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model travel group membership without assuming one universal nomadic custom. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-family-repeated-kanji",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Model travel group membership without assuming one universal nomadic custom versus Track shared characters without assuming universal family practice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Model travel group membership without assuming one universal nomadic custom versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-source-contradiction",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Model travel group membership without assuming one universal nomadic custom versus Compare conflicting references without silently selecting one; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model travel group membership without assuming one universal nomadic custom",
        "outline": [
          "Explain the specific decision: Model travel group membership without assuming one universal nomadic custom",
          "Define the applicable contract and limits for Nomadic fictional naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model travel group membership without assuming one universal nomadic custom; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model travel group membership without assuming one universal nomadic custom",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:776",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-island-community-name-collisions",
      "slug": "island-community-name-collisions",
      "name": "Island community name collisions",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/island-community-name-collisions/",
        "ja": "/ja/tools/island-community-name-collisions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Resolve a small pool through authored relationship based references",
      "task": "Resolve a small pool through authored relationship based references",
      "searchIntent": {
        "primary": "Complete the task: Resolve a small pool through authored relationship based references",
        "queryHypothesis": "island community name collisions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve a small pool through authored relationship based references?",
        "When should island community name collisions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve a small pool through authored relationship based references",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve a small pool through authored relationship based references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-avoidance-subtext",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Resolve a small pool through authored relationship based references versus Show relationship tension through circumlocution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-misunderstanding-repair-scene",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Resolve a small pool through authored relationship based references versus Resolve a misunderstanding through established information; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Resolve a small pool through authored relationship based references versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve a small pool through authored relationship based references",
        "outline": [
          "Explain the specific decision: Resolve a small pool through authored relationship based references",
          "Define the applicable contract and limits for Island community name collisions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve a small pool through authored relationship based references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve a small pool through authored relationship based references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:777",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-trading-guild-diaspora-names",
      "slug": "trading-guild-diaspora-names",
      "name": "Trading guild diaspora names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/trading-guild-diaspora-names/",
        "ja": "/ja/tools/trading-guild-diaspora-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Track professional and home community forms separately",
      "task": "Track professional and home community forms separately",
      "searchIntent": {
        "primary": "Complete the task: Track professional and home community forms separately",
        "queryHypothesis": "trading guild diaspora names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track professional and home community forms separately?",
        "When should trading guild diaspora names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track professional and home community forms separately",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track professional and home community forms separately. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-guild-apprentice-names",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Track professional and home community forms separately versus Track entry, mastery and departure forms under authored guild rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-player-nickname-adoption",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track professional and home community forms separately versus Track table invented nicknames separately from in world forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-in-records",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Track professional and home community forms separately versus Keep official record forms separate from narrative display; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track professional and home community forms separately",
        "outline": [
          "Explain the specific decision: Track professional and home community forms separately",
          "Define the applicable contract and limits for Trading guild diaspora names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track professional and home community forms separately; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track professional and home community forms separately",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:778",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-academy-character-registers",
      "slug": "academy-character-registers",
      "name": "Academy character registers",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/academy-character-registers/",
        "ja": "/ja/tools/academy-character-registers/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Separate admission records, peers' names and ceremonial titles",
      "task": "Separate admission records, peers' names and ceremonial titles",
      "searchIntent": {
        "primary": "Complete the task: Separate admission records, peers' names and ceremonial titles",
        "queryHypothesis": "academy character registers",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate admission records, peers' names and ceremonial titles?",
        "When should academy character registers be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate admission records, peers' names and ceremonial titles",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate admission records, peers' names and ceremonial titles. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-academy-cohort-naming",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Separate admission records, peers' names and ceremonial titles versus Decide whether cohort labels belong in public personal references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Separate admission records, peers' names and ceremonial titles versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-obituary-clue",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Separate admission records, peers' names and ceremonial titles versus Reconcile dates, names and witnesses in fictional records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate admission records, peers' names and ceremonial titles",
        "outline": [
          "Explain the specific decision: Separate admission records, peers' names and ceremonial titles",
          "Define the applicable contract and limits for Academy character registers",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate admission records, peers' names and ceremonial titles; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate admission records, peers' names and ceremonial titles",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:779",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-monastery-identity-registers",
      "slug": "monastery-identity-registers",
      "name": "Monastery identity registers",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/monastery-identity-registers/",
        "ja": "/ja/tools/monastery-identity-registers/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Model invented initiation rules and outside references",
      "task": "Model invented initiation rules and outside references",
      "searchIntent": {
        "primary": "Complete the task: Model invented initiation rules and outside references",
        "queryHypothesis": "monastery identity registers",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model invented initiation rules and outside references?",
        "When should monastery identity registers be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model invented initiation rules and outside references",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model invented initiation rules and outside references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Model invented initiation rules and outside references versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wizard-order-name",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Model invented initiation rules and outside references versus Apply fictional rank and initiation rules to a personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Model invented initiation rules and outside references versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model invented initiation rules and outside references",
        "outline": [
          "Explain the specific decision: Model invented initiation rules and outside references",
          "Define the applicable contract and limits for Monastery identity registers",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model invented initiation rules and outside references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model invented initiation rules and outside references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:780",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-military-settlement-household-names",
      "slug": "military-settlement-household-names",
      "name": "Military settlement household names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/military-settlement-household-names/",
        "ja": "/ja/tools/military-settlement-household-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Keep family identity distinct from rank and posting",
      "task": "Keep family identity distinct from rank and posting",
      "searchIntent": {
        "primary": "Complete the task: Keep family identity distinct from rank and posting",
        "queryHypothesis": "military settlement household names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep family identity distinct from rank and posting?",
        "When should military settlement household names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep family identity distinct from rank and posting",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep family identity distinct from rank and posting. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-secret-society-member-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep family identity distinct from rank and posting versus Separate rank, ceremonial name and outside identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-foster-household-naming",
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Keep family identity distinct from rank and posting versus Preserve separate legal and informal family relationships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-confession-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Keep family identity distinct from rank and posting versus Keep the confessed name distinct from verified identity evidence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep family identity distinct from rank and posting",
        "outline": [
          "Explain the specific decision: Keep family identity distinct from rank and posting",
          "Define the applicable contract and limits for Military settlement household names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep family identity distinct from rank and posting; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep family identity distinct from rank and posting",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:781",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-prison-colony-imposed-labels",
      "slug": "prison-colony-imposed-labels",
      "name": "Prison colony imposed labels",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/prison-colony-imposed-labels/",
        "ja": "/ja/tools/prison-colony-imposed-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Track institutional naming and resistance without endorsing dehumanization",
      "task": "Track institutional naming and resistance without endorsing dehumanization",
      "searchIntent": {
        "primary": "Complete the task: Track institutional naming and resistance without endorsing dehumanization",
        "queryHypothesis": "prison colony imposed labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track institutional naming and resistance without endorsing dehumanization?",
        "When should prison colony imposed labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track institutional naming and resistance without endorsing dehumanization",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track institutional naming and resistance without endorsing dehumanization. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-prison-ensemble-naming",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Track institutional naming and resistance without endorsing dehumanization versus Separate institutional labels from self and peer chosen names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-illegitimacy-label-critique",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Track institutional naming and resistance without endorsing dehumanization versus Audit narrator and character labels without endorsing discriminatory categories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-identical-character-labels",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Track institutional naming and resistance without endorsing dehumanization versus Distinguish lookalikes in scripts without leaking to readers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track institutional naming and resistance without endorsing dehumanization",
        "outline": [
          "Explain the specific decision: Track institutional naming and resistance without endorsing dehumanization",
          "Define the applicable contract and limits for Prison colony imposed labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track institutional naming and resistance without endorsing dehumanization; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track institutional naming and resistance without endorsing dehumanization",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:782",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-post-collapse-record-loss",
      "slug": "post-collapse-record-loss",
      "name": "Post collapse record loss",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/post-collapse-record-loss/",
        "ja": "/ja/tools/post-collapse-record-loss/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Design personal continuity when documents become unreliable",
      "task": "Design personal continuity when documents become unreliable",
      "searchIntent": {
        "primary": "Complete the task: Design personal continuity when documents become unreliable",
        "queryHypothesis": "post collapse record loss",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design personal continuity when documents become unreliable?",
        "When should post collapse record loss be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design personal continuity when documents become unreliable",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design personal continuity when documents become unreliable. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-witness-protection-fiction-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Design personal continuity when documents become unreliable versus Design fictional continuity without offering real evasion procedures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-changes-surname-after-exile",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Design personal continuity when documents become unreliable versus Preserve continuity across home and adopted communities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-dossier-name-system",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Design personal continuity when documents become unreliable versus Reconcile names across documents, dialogue and narration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design personal continuity when documents become unreliable",
        "outline": [
          "Explain the specific decision: Design personal continuity when documents become unreliable",
          "Define the applicable contract and limits for Post collapse record loss",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design personal continuity when documents become unreliable; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design personal continuity when documents become unreliable",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:783",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-utopian-naming-institutions",
      "slug": "utopian-naming-institutions",
      "name": "Utopian naming institutions",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/utopian-naming-institutions/",
        "ja": "/ja/tools/utopian-naming-institutions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Specify actual rules and exceptions rather than a positive style adjective",
      "task": "Specify actual rules and exceptions rather than a positive style adjective",
      "searchIntent": {
        "primary": "Complete the task: Specify actual rules and exceptions rather than a positive style adjective",
        "queryHypothesis": "utopian naming institutions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to specify actual rules and exceptions rather than a positive style adjective?",
        "When should utopian naming institutions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Specify actual rules and exceptions rather than a positive style adjective",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Specify actual rules and exceptions rather than a positive style adjective. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-nonhuman-culture-naming-contrast",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Specify actual rules and exceptions rather than a positive style adjective versus Distinguish cultures within a species rather than one species one style; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-noble-title-system",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Specify actual rules and exceptions rather than a positive style adjective versus Define ranked titles using authored rules rather than historical claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-elemental-identity-convention",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Specify actual rules and exceptions rather than a positive style adjective versus Build explicit fictional naming rules beyond a single elemental adjective; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Specify actual rules and exceptions rather than a positive style adjective",
        "outline": [
          "Explain the specific decision: Specify actual rules and exceptions rather than a positive style adjective",
          "Define the applicable contract and limits for Utopian naming institutions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Specify actual rules and exceptions rather than a positive style adjective; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Specify actual rules and exceptions rather than a positive style adjective",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:784",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-dystopian-identity-allocation",
      "slug": "dystopian-identity-allocation",
      "name": "Dystopian identity allocation",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/dystopian-identity-allocation/",
        "ja": "/ja/tools/dystopian-identity-allocation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Model assigned identities and character agency within an invented system",
      "task": "Model assigned identities and character agency within an invented system",
      "searchIntent": {
        "primary": "Complete the task: Model assigned identities and character agency within an invented system",
        "queryHypothesis": "dystopian identity allocation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model assigned identities and character agency within an invented system?",
        "When should dystopian identity allocation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model assigned identities and character agency within an invented system",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model assigned identities and character agency within an invented system. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Model assigned identities and character agency within an invented system versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-curse-transfer",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Model assigned identities and character agency within an invented system versus Model conditions for transferring a curse through an invented name system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pilgrimage-chosen-names",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Model assigned identities and character agency within an invented system versus Model temporary and lasting identities in an invented journey ritual; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model assigned identities and character agency within an invented system",
        "outline": [
          "Explain the specific decision: Model assigned identities and character agency within an invented system",
          "Define the applicable contract and limits for Dystopian identity allocation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model assigned identities and character agency within an invented system; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model assigned identities and character agency within an invented system",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:785",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-city-district-surname-distribution",
      "slug": "city-district-surname-distribution",
      "name": "City district surname distribution",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/city-district-surname-distribution/",
        "ja": "/ja/tools/city-district-surname-distribution/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Avoid equating every district with a single ethnicity or class",
      "task": "Avoid equating every district with a single ethnicity or class",
      "searchIntent": {
        "primary": "Complete the task: Avoid equating every district with a single ethnicity or class",
        "queryHypothesis": "city district surname distribution",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid equating every district with a single ethnicity or class?",
        "When should city district surname distribution be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid equating every district with a single ethnicity or class",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid equating every district with a single ethnicity or class. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-mystery-naming-sensitivity-review",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid equating every district with a single ethnicity or class versus Avoid treating ethnicity inferred from a name as evidence of guilt; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-shared-champion-title",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Avoid equating every district with a single ethnicity or class versus Avoid assuming a title identifies a single person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-surname-construction",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Avoid equating every district with a single ethnicity or class versus Build a family identifier with explicit inheritance assumptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid equating every district with a single ethnicity or class",
        "outline": [
          "Explain the specific decision: Avoid equating every district with a single ethnicity or class",
          "Define the applicable contract and limits for City district surname distribution",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid equating every district with a single ethnicity or class; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid equating every district with a single ethnicity or class",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:786",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-rural-urban-name-adaptation",
      "slug": "rural-urban-name-adaptation",
      "name": "Rural urban name adaptation",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/rural-urban-name-adaptation/",
        "ja": "/ja/tools/rural-urban-name-adaptation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Trace specific character choices across a move",
      "task": "Trace specific character choices across a move",
      "searchIntent": {
        "primary": "Complete the task: Trace specific character choices across a move",
        "queryHypothesis": "rural urban name adaptation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace specific character choices across a move?",
        "When should rural urban name adaptation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace specific character choices across a move",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace specific character choices across a move. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Trace specific character choices across a move versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-diaspora-name-adaptation",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Trace specific character choices across a move versus Preserve identity across declared language contact rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-immortal-reputation-names",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Trace specific character choices across a move versus Track names across communities and centuries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace specific character choices across a move",
        "outline": [
          "Explain the specific decision: Trace specific character choices across a move",
          "Define the applicable contract and limits for Rural urban name adaptation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace specific character choices across a move; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace specific character choices across a move",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:787",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-fictional-religious-border-names",
      "slug": "fictional-religious-border-names",
      "name": "Fictional religious border names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/fictional-religious-border-names/",
        "ja": "/ja/tools/fictional-religious-border-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Track recognition of names by competing invented institutions",
      "task": "Track recognition of names by competing invented institutions",
      "searchIntent": {
        "primary": "Complete the task: Track recognition of names by competing invented institutions",
        "queryHypothesis": "fictional religious border names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track recognition of names by competing invented institutions?",
        "When should fictional religious border names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track recognition of names by competing invented institutions",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track recognition of names by competing invented institutions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track recognition of names by competing invented institutions versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track recognition of names by competing invented institutions versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.09285714285714286,
          "sharedProfile": true,
          "difference": "Track recognition of names by competing invented institutions versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track recognition of names by competing invented institutions",
        "outline": [
          "Explain the specific decision: Track recognition of names by competing invented institutions",
          "Define the applicable contract and limits for Fictional religious border names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track recognition of names by competing invented institutions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track recognition of names by competing invented institutions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:788",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-magic-school-house-identity",
      "slug": "magic-school-house-identity",
      "name": "Magic school house identity",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/magic-school-house-identity/",
        "ja": "/ja/tools/magic-school-house-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Separate group affiliation from personal and family names",
      "task": "Separate group affiliation from personal and family names",
      "searchIntent": {
        "primary": "Complete the task: Separate group affiliation from personal and family names",
        "queryHypothesis": "magic school house identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate group affiliation from personal and family names?",
        "When should magic school house identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate group affiliation from personal and family names",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate group affiliation from personal and family names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-court-retainer-identity",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Separate group affiliation from personal and family names versus Track service affiliation and inherited household names independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-house-identity-system",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Separate group affiliation from personal and family names versus Define house membership and inherited personal components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Separate group affiliation from personal and family names versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate group affiliation from personal and family names",
        "outline": [
          "Explain the specific decision: Separate group affiliation from personal and family names",
          "Define the applicable contract and limits for Magic school house identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate group affiliation from personal and family names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate group affiliation from personal and family names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:789",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-guild-town-occupational-surnames",
      "slug": "guild-town-occupational-surnames",
      "name": "Guild town occupational surnames",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/guild-town-occupational-surnames/",
        "ja": "/ja/tools/guild-town-occupational-surnames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Define when trade labels persist after occupation changes",
      "task": "Define when trade labels persist after occupation changes",
      "searchIntent": {
        "primary": "Complete the task: Define when trade labels persist after occupation changes",
        "queryHypothesis": "guild town occupational surnames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define when trade labels persist after occupation changes?",
        "When should guild town occupational surnames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define when trade labels persist after occupation changes",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define when trade labels persist after occupation changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-reconciles-dual-identities",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Define when trade labels persist after occupation changes versus Define which differences remain after integration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-occupation-surnames",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Define when trade labels persist after occupation changes versus Model when an occupational label becomes hereditary; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Define when trade labels persist after occupation changes versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define when trade labels persist after occupation changes",
        "outline": [
          "Explain the specific decision: Define when trade labels persist after occupation changes",
          "Define the applicable contract and limits for Guild town occupational surnames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define when trade labels persist after occupation changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define when trade labels persist after occupation changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:790",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-pilgrimage-chosen-names",
      "slug": "pilgrimage-chosen-names",
      "name": "Pilgrimage chosen names",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/pilgrimage-chosen-names/",
        "ja": "/ja/tools/pilgrimage-chosen-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Model temporary and lasting identities in an invented journey ritual",
      "task": "Model temporary and lasting identities in an invented journey ritual",
      "searchIntent": {
        "primary": "Complete the task: Model temporary and lasting identities in an invented journey ritual",
        "queryHypothesis": "pilgrimage chosen names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model temporary and lasting identities in an invented journey ritual?",
        "When should pilgrimage chosen names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model temporary and lasting identities in an invented journey ritual",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model temporary and lasting identities in an invented journey ritual. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dystopian-identity-allocation",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Model temporary and lasting identities in an invented journey ritual versus Model assigned identities and character agency within an invented system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-monastery-identity-registers",
          "score": 0.1181818181818182,
          "sharedProfile": true,
          "difference": "Model temporary and lasting identities in an invented journey ritual versus Model invented initiation rules and outside references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-names-as-currency",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model temporary and lasting identities in an invented journey ritual versus Model ownership, exchange and personal consequences in an invented economy; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model temporary and lasting identities in an invented journey ritual",
        "outline": [
          "Explain the specific decision: Model temporary and lasting identities in an invented journey ritual",
          "Define the applicable contract and limits for Pilgrimage chosen names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model temporary and lasting identities in an invented journey ritual; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model temporary and lasting identities in an invented journey ritual",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:791",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-fictional-penal-renaming",
      "slug": "fictional-penal-renaming",
      "name": "Fictional penal renaming",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/fictional-penal-renaming/",
        "ja": "/ja/tools/fictional-penal-renaming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Trace coercion, records and later reclamation in story context",
      "task": "Trace coercion, records and later reclamation in story context",
      "searchIntent": {
        "primary": "Complete the task: Trace coercion, records and later reclamation in story context",
        "queryHypothesis": "fictional penal renaming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace coercion, records and later reclamation in story context?",
        "When should fictional penal renaming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace coercion, records and later reclamation in story context",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace coercion, records and later reclamation in story context. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-corrects-public-record",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Trace coercion, records and later reclamation in story context versus Trace the cost and story consequences of correction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-session-npc-improvisation-log",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Trace coercion, records and later reclamation in story context versus Save improvised names with context for later continuity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-colonial-registry-renaming-fiction",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Trace coercion, records and later reclamation in story context versus Distinguish coercive records from self identified names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace coercion, records and later reclamation in story context",
        "outline": [
          "Explain the specific decision: Trace coercion, records and later reclamation in story context",
          "Define the applicable contract and limits for Fictional penal renaming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace coercion, records and later reclamation in story context; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace coercion, records and later reclamation in story context",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:792",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-settler-descendant-naming-conflict",
      "slug": "settler-descendant-naming-conflict",
      "name": "Settler descendant naming conflict",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/settler-descendant-naming-conflict/",
        "ja": "/ja/tools/settler-descendant-naming-conflict/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Compare competing claims while flagging real cultural research needs",
      "task": "Compare competing claims while flagging real cultural research needs",
      "searchIntent": {
        "primary": "Complete the task: Compare competing claims while flagging real cultural research needs",
        "queryHypothesis": "settler descendant naming conflict",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare competing claims while flagging real cultural research needs?",
        "When should settler descendant naming conflict be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare competing claims while flagging real cultural research needs",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare competing claims while flagging real cultural research needs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Compare competing claims while flagging real cultural research needs versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-renaming-transforms-reality",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Compare competing claims while flagging real cultural research needs versus Test scope, exceptions and competing claims of a name change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-naming-sensitivity-review",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Compare competing claims while flagging real cultural research needs versus Require context and native language review for cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare competing claims while flagging real cultural research needs",
        "outline": [
          "Explain the specific decision: Compare competing claims while flagging real cultural research needs",
          "Define the applicable contract and limits for Settler descendant naming conflict",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare competing claims while flagging real cultural research needs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare competing claims while flagging real cultural research needs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:793",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-returning-emigrant-identity",
      "slug": "returning-emigrant-identity",
      "name": "Returning emigrant identity",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/returning-emigrant-identity/",
        "ja": "/ja/tools/returning-emigrant-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Reconcile home references with an adopted public name",
      "task": "Reconcile home references with an adopted public name",
      "searchIntent": {
        "primary": "Complete the task: Reconcile home references with an adopted public name",
        "queryHypothesis": "returning emigrant identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile home references with an adopted public name?",
        "When should returning emigrant identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile home references with an adopted public name",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile home references with an adopted public name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-changes-surname-after-exile",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile home references with an adopted public name versus Preserve continuity across home and adopted communities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-theater-troupe-stage-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile home references with an adopted public name versus Coordinate public credits and backstage references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-publisher-handoff",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile home references with an adopted public name versus Reconcile bylines, cast pages and public facing names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile home references with an adopted public name",
        "outline": [
          "Explain the specific decision: Reconcile home references with an adopted public name",
          "Define the applicable contract and limits for Returning emigrant identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile home references with an adopted public name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile home references with an adopted public name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:794",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-stateless-fictional-character-records",
      "slug": "stateless-fictional-character-records",
      "name": "Stateless fictional character records",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/stateless-fictional-character-records/",
        "ja": "/ja/tools/stateless-fictional-character-records/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Distinguish institutional recognition from personal identity",
      "task": "Distinguish institutional recognition from personal identity",
      "searchIntent": {
        "primary": "Complete the task: Distinguish institutional recognition from personal identity",
        "queryHypothesis": "stateless fictional character records",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish institutional recognition from personal identity?",
        "When should stateless fictional character records be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish institutional recognition from personal identity",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish institutional recognition from personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-clan-branch-registry",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish institutional recognition from personal identity versus Distinguish branch identity from individual personal names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-same-reading-different-writing",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish institutional recognition from personal identity versus Distinguish character identity from graphic alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-research-collective-credit-names",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish institutional recognition from personal identity versus Distinguish institutional authorship from fictional individuals; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish institutional recognition from personal identity",
        "outline": [
          "Explain the specific decision: Distinguish institutional recognition from personal identity",
          "Define the applicable contract and limits for Stateless fictional character records",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish institutional recognition from personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish institutional recognition from personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:795",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-multi-calendar-name-timeline",
      "slug": "multi-calendar-name-timeline",
      "name": "Multi calendar name timeline",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/multi-calendar-name-timeline/",
        "ja": "/ja/tools/multi-calendar-name-timeline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Speculative-fiction, comic and game creators maintaining documents in more than one invented date system.",
      "scenario": "A person adopts a new name on a harbor-calendar date, while a ridge-calendar letter appears to use the old form afterward. An unanchored third calendar must remain unresolved.",
      "task": "Align explicit naming events across author-defined periodic calendars and audit exact name use against ordered adoptions.",
      "searchIntent": {
        "primary": "Align naming events across fictional calendars and audit ordered name use",
        "queryHypothesis": "multi calendar name timeline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "When do two fictional calendar dates mean the same day?",
        "Can an unknown calendar epoch justify calling an old name an error?"
      ],
      "inputs": [
        {
          "key": "calendars",
          "use": "1–8 calendars with null/known shared epoch, 1–12 periodic cycle years and explicit month lengths."
        },
        {
          "key": "people",
          "use": "Stable IDs, working labels and exact baseline form or null before all entered events."
        },
        {
          "key": "events",
          "use": "1–80 explicit adopt/use records with calendar date, same-day order, exact form and optional asserted shared day."
        },
        {
          "key": "synchronisms",
          "use": "Up to 30 author-declared same-day date pairs; audit known anchors and show unapplied epoch candidates for an unanchored calendar."
        },
        {
          "key": "targetCalendar",
          "use": "Convert each anchored event to a selected existing calendar; retain unanchored/outside-coverage states."
        }
      ],
      "rules": [
        "Each calendar year cycle begins with year 1; no year zero, negative years, era resets, time zones or inferred historical calendars. All dates share one declared day boundary.",
        "Use exact month IDs and day bounds for the selected cycle year; an intercalary month absent from that year is invalid.",
        "Unknown epoch is null, never zero. Preserve relative local day and withhold shared order and target conversion.",
        "Order anchored events by shared day and explicit same-day order. Reject duplicate positions for the same person; incidental array order has no authority.",
        "Adoption starts a new exact active form at its ordered event. Compare use with the latest prior anchored adoption or supplied baseline; do not infer aliases or motives.",
        "Any unanchored adoption for a person makes use checks conservatively unverifiable, even when the use has a known date.",
        "A one-known/one-unknown synchronism suggests an epoch; retain inconsistent candidates and do not apply a proposal or propagate through unanchored pairs."
      ],
      "requiredData": [
        {
          "description": "Original periodic harbor/ridge/old-log calendars and naming fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Creator-supplied date and identity records; no factual historical calendar dataset",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Each calendar year cycle begins with year 1; no year zero, negative years, era resets, time zones or inferred historical calendars. All dates share one declared day boundary.",
        "Use exact month IDs and day bounds for the selected cycle year; an intercalary month absent from that year is invalid.",
        "Unknown epoch is null, never zero. Preserve relative local day and withhold shared order and target conversion.",
        "Order anchored events by shared day and explicit same-day order. Reject duplicate positions for the same person; incidental array order has no authority.",
        "Adoption starts a new exact active form at its ordered event. Compare use with the latest prior anchored adoption or supplied baseline; do not infer aliases or motives.",
        "Any unanchored adoption for a person makes use checks conservatively unverifiable, even when the use has a known date.",
        "A one-known/one-unknown synchronism suggests an epoch; retain inconsistent candidates and do not apply a proposal or propagate through unanchored pairs."
      ],
      "outputs": [
        "Per-event local day, known/unknown shared day and selected-calendar date",
        "Exact active-form and asserted-day checks with unresolved states",
        "Same-day discrepancies, unapplied epoch candidates and private calendar/name ledger"
      ],
      "capabilities": [
        "Convert a date through multi-year cycles with intercalary months and prove round-trip correspondence.",
        "Separate an incorrect name use from an uncertain calendar anchor; expose conflicting synchronisms without selecting a convenient epoch."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The main decision is whether naming records refer to the same shared day, and whether an entered usage falls before or after an explicit adoption. It requires calendar cycles, epochs and same-day anchors; name generation and reign-number counting do not convert dates.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "regnal-numbering-consistency",
          "difference": "Reign numbering consumes already ordered integer times and counts a series. This tool constructs shared-day positions from explicit periodic month/year rules, validates dates, checks synchronisms and projects naming events into a selected calendar. It neither numbers rulers nor resolves legitimacy."
        }
      },
      "nearestTools": [
        {
          "id": "nw-multi-timeline-cast-names",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Align explicit naming events across author-defined periodic calendars and audit exact name use against ordered adoptions. versus Distinguish contemporaries, ancestors and repeated identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-author-rebrand-timeline",
          "score": 0.1061111111111111,
          "sharedProfile": false,
          "difference": "Align explicit naming events across author-defined periodic calendars and audit exact name use against ordered adoptions. versus Schedule name changes across a backlist and active series; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-multi-genre-author-identities",
          "score": 0.0925438596491228,
          "sharedProfile": false,
          "difference": "Align explicit naming events across author-defined periodic calendars and audit exact name use against ordered adoptions. versus Separate author brands while preserving optional reader connections; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A date disagreement can be an anchoring problem before it is a name-continuity mistake.",
        "outline": [
          "A corrected address on a ridge-calendar letter",
          "Define periodic years and one shared day boundary",
          "Convert the day before deciding which name applies",
          "Unanchored records remain useful without becoming dated facts",
          "Test an intercalary month and a same-day adoption"
        ],
        "story": "Lio adopts Kest at a harbor public event. A letter dated in the ridge calendar still uses Lio one shared day later. An old station log offers a possible anchor but is not silently used to certify chronology.",
        "storyAnalysis": "Replacing every old form would conceal whether a letter was late, deliberately resistant, or dated under an unproven calendar. Explicit arithmetic identifies the actual decision without inferring a character motive.",
        "evidence": "Original invented calendars, boundary/round-trip fixtures and scoped name-transition checks; no historical claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/calendars.md",
        "localizedBodies": {
          "en": "content/en/calendars.md",
          "ja": "content/ja/calendars.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Changing a cycle month length changes later shared days and target conversions.",
        "An adoption at order 0 affects a same-day use at order 1; reversing those orders changes the name check.",
        "Unknown epochs retain null shared days and prevent false chronological conclusions.",
        "A consistent anchor proposal remains unapplied until an explicit input edit; contradictory candidates stay visible.",
        "Permuting event rows preserves ordered outcomes.",
        "Missing dates, invalid leap months, duplicate positions and unknown IDs produce conflicts."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:796",
      "profileSource": "data/profiles.json#setting-linked",
      "specBatch": "batch-05",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Exact bounded date arithmetic, unknown anchors, chronology and bilingual original editorial explanation."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "calendars",
        "engineFiles": [
          "web/fictional-calendars.mjs",
          "web/calendar-view.mjs",
          "web/calendar-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/calendar.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "calendars",
          "label": [
            "Periodic calendars · JSON",
            "周期の暦・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"harbor\",\n    \"label\": \"Harbor calendar\",\n    \"epochDay\": 0,\n    \"cycle\": [\n      {\n        \"months\": [\n          {\n            \"id\": \"flood\",\n            \"label\": \"Flood\",\n            \"days\": 20\n          },\n          {\n            \"id\": \"dry\",\n            \"label\": \"Dry\",\n            \"days\": 20\n          }\n        ]\n      },\n      {\n        \"months\": [\n          {\n            \"id\": \"flood\",\n            \"label\": \"Flood\",\n            \"days\": 20\n          },\n          {\n            \"id\": \"dry\",\n            \"label\": \"Dry\",\n            \"days\": 20\n          },\n          {\n            \"id\": \"turn\",\n            \"label\": \"Turn\",\n            \"days\": 5\n          }\n        ]\n      }\n    ]\n  },\n  {\n    \"id\": \"ridge\",\n    \"label\": \"Ridge calendar\",\n    \"epochDay\": 30,\n    \"cycle\": [\n      {\n        \"months\": [\n          {\n            \"id\": \"watch\",\n            \"label\": \"Watch\",\n            \"days\": 30\n          },\n          {\n            \"id\": \"rest\",\n            \"label\": \"Rest\",\n            \"days\": 30\n          }\n        ]\n      }\n    ]\n  },\n  {\n    \"id\": \"old\",\n    \"label\": \"Old station log\",\n    \"epochDay\": null,\n    \"cycle\": [\n      {\n        \"months\": [\n          {\n            \"id\": \"watch\",\n            \"label\": \"Watch\",\n            \"days\": 30\n          },\n          {\n            \"id\": \"rest\",\n            \"label\": \"Rest\",\n            \"days\": 30\n          }\n        ]\n      }\n    ]\n  }\n]",
          "help": [
            "epochDay is the shared day of year 1/month 1/day 1, or null. cycle repeats 1–12 years; months have exact IDs, labels and 1–500 days. All calendars share one day boundary.",
            "epochDayは1年の最初の月の1日に対応する共通日かnull。cycleは1〜12年で繰り返し、月には正確なID、label、1〜500の日数。全暦は同じ日境界を使います。"
          ],
          "maxLength": 150000
        },
        {
          "key": "people",
          "label": [
            "People & initial forms · JSON",
            "人物と開始前の表記・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"lio\",\n    \"name\": \"Lio / Kest\",\n    \"initialForm\": \"Lio\"\n  }\n]",
          "help": [
            "The baseline form precedes all entered events; null means unknown. Exact forms are not automatic aliases.",
            "initialFormは入力した全項目より前の表記です。nullは不明。異なる表記を自動で別名とみなしません。"
          ],
          "maxLength": 150000
        },
        {
          "key": "events",
          "label": [
            "Dated adoptions & uses · JSON",
            "日付付きの改名と使用・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"adoption\",\n    \"person\": \"lio\",\n    \"kind\": \"adopt\",\n    \"form\": \"Kest\",\n    \"date\": {\n      \"calendar\": \"harbor\",\n      \"year\": 2,\n      \"month\": \"dry\",\n      \"day\": 5\n    },\n    \"order\": 0,\n    \"claimDay\": null\n  },\n  {\n    \"id\": \"old-address\",\n    \"person\": \"lio\",\n    \"kind\": \"use\",\n    \"form\": \"Lio\",\n    \"date\": {\n      \"calendar\": \"harbor\",\n      \"year\": 2,\n      \"month\": \"dry\",\n      \"day\": 5\n    },\n    \"order\": 1,\n    \"claimDay\": null\n  },\n  {\n    \"id\": \"ridge-letter\",\n    \"person\": \"lio\",\n    \"kind\": \"use\",\n    \"form\": \"Kest\",\n    \"date\": {\n      \"calendar\": \"ridge\",\n      \"year\": 1,\n      \"month\": \"rest\",\n      \"day\": 6\n    },\n    \"order\": 0,\n    \"claimDay\": 64\n  },\n  {\n    \"id\": \"old-log\",\n    \"person\": \"lio\",\n    \"kind\": \"use\",\n    \"form\": \"Kest\",\n    \"date\": {\n      \"calendar\": \"old\",\n      \"year\": 1,\n      \"month\": \"watch\",\n      \"day\": 6\n    },\n    \"order\": 1,\n    \"claimDay\": null\n  },\n  {\n    \"id\": \"cycle-return\",\n    \"person\": \"lio\",\n    \"kind\": \"use\",\n    \"form\": \"Kest\",\n    \"date\": {\n      \"calendar\": \"harbor\",\n      \"year\": 3,\n      \"month\": \"flood\",\n      \"day\": 1\n    },\n    \"order\": 0,\n    \"claimDay\": null\n  }\n]",
          "help": [
            "Stable id/person, adopt/use, exact form, date {calendar,year,month,day}, order and integer/null claimDay. Year 1–10000; no year zero. Order separates one person’s same-day events.",
            "id/person、adopt/use、正確なform、date {calendar,year,month,day}、order、整数かnullのclaimDay。年は1〜10000、0年はなし。同じ人物の同日はorderで順を分けます。"
          ],
          "maxLength": 150000
        },
        {
          "key": "synchronisms",
          "label": [
            "Declared same-day pairs · JSON",
            "同日として扱う対応・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"public-day\",\n    \"left\": {\n      \"calendar\": \"harbor\",\n      \"year\": 2,\n      \"month\": \"dry\",\n      \"day\": 5\n    },\n    \"right\": {\n      \"calendar\": \"ridge\",\n      \"year\": 1,\n      \"month\": \"rest\",\n      \"day\": 5\n    }\n  },\n  {\n    \"id\": \"old-bridge\",\n    \"left\": {\n      \"calendar\": \"harbor\",\n      \"year\": 2,\n      \"month\": \"dry\",\n      \"day\": 5\n    },\n    \"right\": {\n      \"calendar\": \"old\",\n      \"year\": 1,\n      \"month\": \"watch\",\n      \"day\": 5\n    }\n  }\n]",
          "help": [
            "id/left/right dates. A suggestion never edits the epoch. Review inconsistent candidates and explicitly edit calendars to adopt an anchor.",
            "id/left/rightの日付。提案は起点を編集しません。矛盾した候補を確認し、採用するならcalendarsを明示的に編集します。"
          ],
          "maxLength": 150000
        },
        {
          "key": "targetCalendar",
          "label": [
            "Target calendar ID",
            "変換先の暦ID"
          ],
          "type": "text",
          "default": "ridge",
          "help": null
        }
      ]
    },
    {
      "id": "nw-setting-naming-bible",
      "slug": "setting-naming-bible",
      "name": "Setting naming bible",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/setting-naming-bible/",
        "ja": "/ja/tools/setting-naming-bible/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Link places, institutions and people without merging their naming grammars",
      "task": "Link places, institutions and people without merging their naming grammars",
      "searchIntent": {
        "primary": "Complete the task: Link places, institutions and people without merging their naming grammars",
        "queryHypothesis": "setting naming bible",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link places, institutions and people without merging their naming grammars?",
        "When should setting naming bible be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link places, institutions and people without merging their naming grammars",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link places, institutions and people without merging their naming grammars. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-bible",
          "score": 0.16309523809523807,
          "sharedProfile": false,
          "difference": "Link places, institutions and people without merging their naming grammars versus Export people, naming rules and exception decisions as one reference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-records-mismatch",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Link places, institutions and people without merging their naming grammars versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-inherited-questgiver-title",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Link places, institutions and people without merging their naming grammars versus Transfer office without merging save identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link places, institutions and people without merging their naming grammars",
        "outline": [
          "Explain the specific decision: Link places, institutions and people without merging their naming grammars",
          "Define the applicable contract and limits for Setting naming bible",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link places, institutions and people without merging their naming grammars; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link places, institutions and people without merging their naming grammars",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:797",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-setting-name-rule-exception-map",
      "slug": "setting-name-rule-exception-map",
      "name": "Setting name rule exception map",
      "category": "setting-linked",
      "urls": {
        "en": "/en/tools/setting-name-rule-exception-map/",
        "ja": "/ja/tools/setting-name-rule-exception-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and setting focused writers",
      "scenario": "Identify which characters violate local rules and why",
      "task": "Identify which characters violate local rules and why",
      "searchIntent": {
        "primary": "Complete the task: Identify which characters violate local rules and why",
        "queryHypothesis": "setting name rule exception map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify which characters violate local rules and why?",
        "When should setting name rule exception map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional settlement rules: constrain local conventions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "character mobility: track adaptation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "institution and family choices: avoid geographic determinism",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence"
      ],
      "requiredData": [
        {
          "description": "authored settlement histories",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "household and migration graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "fictional rule exceptions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify which characters violate local rules and why",
        "location does not automatically determine personal identity",
        "separate fictional setting rules from real cultural evidence",
        "Proposed category workflow: setting history → local rules → individual decisions → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "local and external name forms",
        "adaptation decisions",
        "setting consistency warnings"
      ],
      "capabilities": [
        "simulate a move without erasing prior identity",
        "compare local rules with individual exceptions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify which characters violate local rules and why. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-reclaims-intimate-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Identify which characters violate local rules and why versus Identify whose use becomes welcome and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-generation-audit-trail",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Identify which characters violate local rules and why versus Export which entries and rules produced a candidate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-naming-uncertainty-map",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Identify which characters violate local rules and why versus Identify missing research before committing a culturally situated name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify which characters violate local rules and why",
        "outline": [
          "Explain the specific decision: Identify which characters violate local rules and why",
          "Define the applicable contract and limits for Setting name rule exception map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify which characters violate local rules and why; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify which characters violate local rules and why",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:798",
      "profileSource": "data/profiles.json#setting-linked"
    },
    {
      "id": "nw-fictional-house-identity-system",
      "slug": "fictional-house-identity-system",
      "name": "Fictional house identity system",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/fictional-house-identity-system/",
        "ja": "/ja/tools/fictional-house-identity-system/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Define house membership and inherited personal components",
      "task": "Define house membership and inherited personal components",
      "searchIntent": {
        "primary": "Complete the task: Define house membership and inherited personal components",
        "queryHypothesis": "fictional house identity system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define house membership and inherited personal components?",
        "When should fictional house identity system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define house membership and inherited personal components",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define house membership and inherited personal components. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-stepfamily-address-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Define house membership and inherited personal components versus Distinguish household membership from inherited naming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-religious-personal-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Define house membership and inherited personal components versus Define devotional components within a fictional belief system; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-court-retainer-identity",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Define house membership and inherited personal components versus Track service affiliation and inherited household names independently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define house membership and inherited personal components",
        "outline": [
          "Explain the specific decision: Define house membership and inherited personal components",
          "Define the applicable contract and limits for Fictional house identity system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define house membership and inherited personal components; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define house membership and inherited personal components",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:801",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-clan-branch-registry",
      "slug": "clan-branch-registry",
      "name": "Clan branch registry",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/clan-branch-registry/",
        "ja": "/ja/tools/clan-branch-registry/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Distinguish branch identity from individual personal names",
      "task": "Distinguish branch identity from individual personal names",
      "searchIntent": {
        "primary": "Complete the task: Distinguish branch identity from individual personal names",
        "queryHypothesis": "clan branch registry",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish branch identity from individual personal names?",
        "When should clan branch registry be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish branch identity from individual personal names",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish branch identity from individual personal names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-same-reading-different-writing",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish branch identity from individual personal names versus Distinguish character identity from graphic alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish branch identity from individual personal names versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hive-member-identity",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish branch identity from individual personal names versus Distinguish collective reference from individual agents; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish branch identity from individual personal names",
        "outline": [
          "Explain the specific decision: Distinguish branch identity from individual personal names",
          "Define the applicable contract and limits for Clan branch registry",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish branch identity from individual personal names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish branch identity from individual personal names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:802",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-guild-apprentice-names",
      "slug": "guild-apprentice-names",
      "name": "Guild apprentice names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/guild-apprentice-names/",
        "ja": "/ja/tools/guild-apprentice-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Track entry, mastery and departure forms under authored guild rules",
      "task": "Track entry, mastery and departure forms under authored guild rules",
      "searchIntent": {
        "primary": "Complete the task: Track entry, mastery and departure forms under authored guild rules",
        "queryHypothesis": "guild apprentice names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track entry, mastery and departure forms under authored guild rules?",
        "When should guild apprentice names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track entry, mastery and departure forms under authored guild rules",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track entry, mastery and departure forms under authored guild rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-trading-guild-diaspora-names",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Track entry, mastery and departure forms under authored guild rules versus Track professional and home community forms separately; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-guild-mastery-title",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Track entry, mastery and departure forms under authored guild rules versus Resolve titles by certification events in an invented guild; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-bound-oath-breach",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Track entry, mastery and departure forms under authored guild rules versus Define breach detection and consequences under authored rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track entry, mastery and departure forms under authored guild rules",
        "outline": [
          "Explain the specific decision: Track entry, mastery and departure forms under authored guild rules",
          "Define the applicable contract and limits for Guild apprentice names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track entry, mastery and departure forms under authored guild rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track entry, mastery and departure forms under authored guild rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:803",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-order-initiation-names",
      "slug": "order-initiation-names",
      "name": "Order initiation names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/order-initiation-names/",
        "ja": "/ja/tools/order-initiation-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Apply fictional ceremonial name rules with an identity timeline",
      "task": "Apply fictional ceremonial name rules with an identity timeline",
      "searchIntent": {
        "primary": "Complete the task: Apply fictional ceremonial name rules with an identity timeline",
        "queryHypothesis": "order initiation names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply fictional ceremonial name rules with an identity timeline?",
        "When should order initiation names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply fictional ceremonial name rules with an identity timeline",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply fictional ceremonial name rules with an identity timeline. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-wizard-order-name",
          "score": 0.3952380952380952,
          "sharedProfile": false,
          "difference": "Apply fictional ceremonial name rules with an identity timeline versus Apply fictional rank and initiation rules to a personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-adoption-event-names",
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Apply fictional ceremonial name rules with an identity timeline versus Apply household rules with author approved identity retention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-society-member-names",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Apply fictional ceremonial name rules with an identity timeline versus Separate rank, ceremonial name and outside identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply fictional ceremonial name rules with an identity timeline",
        "outline": [
          "Explain the specific decision: Apply fictional ceremonial name rules with an identity timeline",
          "Define the applicable contract and limits for Order initiation names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply fictional ceremonial name rules with an identity timeline; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply fictional ceremonial name rules with an identity timeline",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:804",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-academy-cohort-naming",
      "slug": "academy-cohort-naming",
      "name": "Academy cohort naming",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/academy-cohort-naming/",
        "ja": "/ja/tools/academy-cohort-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Decide whether cohort labels belong in public personal references",
      "task": "Decide whether cohort labels belong in public personal references",
      "searchIntent": {
        "primary": "Complete the task: Decide whether cohort labels belong in public personal references",
        "queryHypothesis": "academy cohort naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to decide whether cohort labels belong in public personal references?",
        "When should academy cohort naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Decide whether cohort labels belong in public personal references",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Decide whether cohort labels belong in public personal references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-age-cohort-naming",
          "score": 0.17083333333333334,
          "sharedProfile": false,
          "difference": "Decide whether cohort labels belong in public personal references versus Match fictional birth timing to sourced cohort data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Decide whether cohort labels belong in public personal references versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-returning-emigrant-identity",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Decide whether cohort labels belong in public personal references versus Reconcile home references with an adopted public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Decide whether cohort labels belong in public personal references",
        "outline": [
          "Explain the specific decision: Decide whether cohort labels belong in public personal references",
          "Define the applicable contract and limits for Academy cohort naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Decide whether cohort labels belong in public personal references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Decide whether cohort labels belong in public personal references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:805",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-military-unit-callsign-roster",
      "slug": "military-unit-callsign-roster",
      "name": "Military unit callsign roster",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/military-unit-callsign-roster/",
        "ja": "/ja/tools/military-unit-callsign-roster/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Keep unit identifiers distinct from individual callsigns",
      "task": "Keep unit identifiers distinct from individual callsigns",
      "searchIntent": {
        "primary": "Complete the task: Keep unit identifiers distinct from individual callsigns",
        "queryHypothesis": "military unit callsign roster",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep unit identifiers distinct from individual callsigns?",
        "When should military unit callsign roster be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep unit identifiers distinct from individual callsigns",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep unit identifiers distinct from individual callsigns. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-military-callsign-design",
          "score": 0.3025,
          "sharedProfile": false,
          "difference": "Keep unit identifiers distinct from individual callsigns versus Derive fictional callsigns from unit practice and character history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-point-of-view-roster",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Keep unit identifiers distinct from individual callsigns versus Keep viewpoint names distinct in chapter transitions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Keep unit identifiers distinct from individual callsigns versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep unit identifiers distinct from individual callsigns",
        "outline": [
          "Explain the specific decision: Keep unit identifiers distinct from individual callsigns",
          "Define the applicable contract and limits for Military unit callsign roster",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep unit identifiers distinct from individual callsigns; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep unit identifiers distinct from individual callsigns",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:806",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-rebel-cell-codenames",
      "slug": "rebel-cell-codenames",
      "name": "Rebel cell codenames",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/rebel-cell-codenames/",
        "ja": "/ja/tools/rebel-cell-codenames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Design a fiction specific namespace and permitted knowledge graph",
      "task": "Design a fiction specific namespace and permitted knowledge graph",
      "searchIntent": {
        "primary": "Complete the task: Design a fiction specific namespace and permitted knowledge graph",
        "queryHypothesis": "rebel cell codenames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a fiction specific namespace and permitted knowledge graph?",
        "When should rebel cell codenames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a fiction specific namespace and permitted knowledge graph",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a fiction specific namespace and permitted knowledge graph. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rebel-cell-identity-separation",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Design a fiction specific namespace and permitted knowledge graph versus Avoid accidental leakage between cells in story dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-secret-address-slip",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Design a fiction specific namespace and permitted knowledge graph versus Design a revealing form of address with a scene knowledge ledger; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-coming-of-age-chosen-name",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Design a fiction specific namespace and permitted knowledge graph versus Connect a name decision to a specific act of agency; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a fiction specific namespace and permitted knowledge graph",
        "outline": [
          "Explain the specific decision: Design a fiction specific namespace and permitted knowledge graph",
          "Define the applicable contract and limits for Rebel cell codenames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a fiction specific namespace and permitted knowledge graph; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a fiction specific namespace and permitted knowledge graph",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:807",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-secret-society-member-names",
      "slug": "secret-society-member-names",
      "name": "Secret society member names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/secret-society-member-names/",
        "ja": "/ja/tools/secret-society-member-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Separate rank, ceremonial name and outside identity",
      "task": "Separate rank, ceremonial name and outside identity",
      "searchIntent": {
        "primary": "Complete the task: Separate rank, ceremonial name and outside identity",
        "queryHypothesis": "secret society member names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate rank, ceremonial name and outside identity?",
        "When should secret society member names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate rank, ceremonial name and outside identity",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate rank, ceremonial name and outside identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-military-settlement-household-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate rank, ceremonial name and outside identity versus Keep family identity distinct from rank and posting; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-order-initiation-names",
          "score": 0.18571428571428572,
          "sharedProfile": true,
          "difference": "Separate rank, ceremonial name and outside identity versus Apply fictional ceremonial name rules with an identity timeline; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-religious-office-name",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate rank, ceremonial name and outside identity versus Separate chosen religious identity from institutional rank; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate rank, ceremonial name and outside identity",
        "outline": [
          "Explain the specific decision: Separate rank, ceremonial name and outside identity",
          "Define the applicable contract and limits for Secret society member names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate rank, ceremonial name and outside identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate rank, ceremonial name and outside identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:808",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-theater-troupe-stage-names",
      "slug": "theater-troupe-stage-names",
      "name": "Theater troupe stage names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/theater-troupe-stage-names/",
        "ja": "/ja/tools/theater-troupe-stage-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Coordinate public credits and backstage references",
      "task": "Coordinate public credits and backstage references",
      "searchIntent": {
        "primary": "Complete the task: Coordinate public credits and backstage references",
        "queryHypothesis": "theater troupe stage names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to coordinate public credits and backstage references?",
        "When should theater troupe stage names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Coordinate public credits and backstage references",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Coordinate public credits and backstage references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-returning-emigrant-identity",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Coordinate public credits and backstage references versus Reconcile home references with an adopted public name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rewrites-own-myth",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Coordinate public credits and backstage references versus Coordinate chosen name, public story and skeptical observers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-academy-cohort-naming",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Coordinate public credits and backstage references versus Decide whether cohort labels belong in public personal references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Coordinate public credits and backstage references",
        "outline": [
          "Explain the specific decision: Coordinate public credits and backstage references",
          "Define the applicable contract and limits for Theater troupe stage names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Coordinate public credits and backstage references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Coordinate public credits and backstage references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:809",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-idol-group-fictional-identities",
      "slug": "idol-group-fictional-identities",
      "name": "Idol group fictional identities",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/idol-group-fictional-identities/",
        "ja": "/ja/tools/idol-group-fictional-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Keep stage persona and private identity relationships explicit",
      "task": "Keep stage persona and private identity relationships explicit",
      "searchIntent": {
        "primary": "Complete the task: Keep stage persona and private identity relationships explicit",
        "queryHypothesis": "idol group fictional identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep stage persona and private identity relationships explicit?",
        "When should idol group fictional identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep stage persona and private identity relationships explicit",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep stage persona and private identity relationships explicit. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-arena-fighter-ring-name",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Keep stage persona and private identity relationships explicit versus Connect public persona, announcer readability and private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-teacher-student-address-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Keep stage persona and private identity relationships explicit versus Differentiate institutional and private relationships; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-leaderboard-fiction-identities",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Keep stage persona and private identity relationships explicit versus Separate fictional in world rankings from player account identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep stage persona and private identity relationships explicit",
        "outline": [
          "Explain the specific decision: Keep stage persona and private identity relationships explicit",
          "Define the applicable contract and limits for Idol group fictional identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep stage persona and private identity relationships explicit; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep stage persona and private identity relationships explicit",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:810",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-circus-ensemble-billing-names",
      "slug": "circus-ensemble-billing-names",
      "name": "Circus ensemble billing names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/circus-ensemble-billing-names/",
        "ja": "/ja/tools/circus-ensemble-billing-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Compare announcement names and intimate troupe address",
      "task": "Compare announcement names and intimate troupe address",
      "searchIntent": {
        "primary": "Complete the task: Compare announcement names and intimate troupe address",
        "queryHypothesis": "circus ensemble billing names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare announcement names and intimate troupe address?",
        "When should circus ensemble billing names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare announcement names and intimate troupe address",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare announcement names and intimate troupe address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-team-callsign-dialogue",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Compare announcement names and intimate troupe address versus Keep operational and personal address contexts separate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-ensemble-name-separation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare announcement names and intimate troupe address versus Optimize a supplied cast for distinct written and spoken forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-ensemble-naming",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare announcement names and intimate troupe address versus Separate institutional labels from self and peer chosen names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare announcement names and intimate troupe address",
        "outline": [
          "Explain the specific decision: Compare announcement names and intimate troupe address",
          "Define the applicable contract and limits for Circus ensemble billing names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare announcement names and intimate troupe address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare announcement names and intimate troupe address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:811",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-sports-team-character-nicknames",
      "slug": "sports-team-character-nicknames",
      "name": "Sports team character nicknames",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/sports-team-character-nicknames/",
        "ja": "/ja/tools/sports-team-character-nicknames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Derive labels from authored team interactions rather than athlete stereotypes",
      "task": "Derive labels from authored team interactions rather than athlete stereotypes",
      "searchIntent": {
        "primary": "Complete the task: Derive labels from authored team interactions rather than athlete stereotypes",
        "queryHypothesis": "sports team character nicknames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive labels from authored team interactions rather than athlete stereotypes?",
        "When should sports team character nicknames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive labels from authored team interactions rather than athlete stereotypes",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive labels from authored team interactions rather than athlete stereotypes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-prison-gang-imposed-nicknames",
          "score": 0.20833333333333334,
          "sharedProfile": true,
          "difference": "Derive labels from authored team interactions rather than athlete stereotypes versus Show power and refusal rather than treating labels as neutral; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-team-naming-hierarchy",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Derive labels from authored team interactions rather than athlete stereotypes versus Separate individual names, role labels and collective references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Derive labels from authored team interactions rather than athlete stereotypes versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive labels from authored team interactions rather than athlete stereotypes",
        "outline": [
          "Explain the specific decision: Derive labels from authored team interactions rather than athlete stereotypes",
          "Define the applicable contract and limits for Sports team character nicknames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive labels from authored team interactions rather than athlete stereotypes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive labels from authored team interactions rather than athlete stereotypes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:812",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-research-collective-credit-names",
      "slug": "research-collective-credit-names",
      "name": "Research collective credit names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/research-collective-credit-names/",
        "ja": "/ja/tools/research-collective-credit-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Distinguish institutional authorship from fictional individuals",
      "task": "Distinguish institutional authorship from fictional individuals",
      "searchIntent": {
        "primary": "Complete the task: Distinguish institutional authorship from fictional individuals",
        "queryHypothesis": "research collective credit names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish institutional authorship from fictional individuals?",
        "When should research collective credit names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish institutional authorship from fictional individuals",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish institutional authorship from fictional individuals. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-stateless-fictional-character-records",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Distinguish institutional authorship from fictional individuals versus Distinguish institutional recognition from personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-author-credit-governance",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Distinguish institutional authorship from fictional individuals versus Resolve which authored byline and contributor snapshot belongs to each edition as collective membership and internal credit permissions change.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-script-artist-credit-pairing",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Distinguish institutional authorship from fictional individuals versus Distinguish writer and artist names in limited credit space; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish institutional authorship from fictional individuals",
        "outline": [
          "Explain the specific decision: Distinguish institutional authorship from fictional individuals",
          "Define the applicable contract and limits for Research collective credit names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish institutional authorship from fictional individuals; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish institutional authorship from fictional individuals",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:813",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-mage-council-title-assignment",
      "slug": "mage-council-title-assignment",
      "name": "Mage council title assignment",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/mage-council-title-assignment/",
        "ja": "/ja/tools/mage-council-title-assignment/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Model offices and personal names under a declared constitution",
      "task": "Model offices and personal names under a declared constitution",
      "searchIntent": {
        "primary": "Complete the task: Model offices and personal names under a declared constitution",
        "queryHypothesis": "mage council title assignment",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model offices and personal names under a declared constitution?",
        "When should mage council title assignment be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model offices and personal names under a declared constitution",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model offices and personal names under a declared constitution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-supporting-character-name-assignment",
          "score": 0.11642857142857142,
          "sharedProfile": false,
          "difference": "Model offices and personal names under a declared constitution versus Assign a supplied name pool jointly to an authored cast under eligibility, locks and scene-collision constraints.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-saint-like-fictional-title",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Model offices and personal names under a declared constitution versus Model veneration within invented religion without asserting real canonization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-court-ensemble-address-map",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Model offices and personal names under a declared constitution versus Disambiguate personal names, offices and ranked titles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model offices and personal names under a declared constitution",
        "outline": [
          "Explain the specific decision: Model offices and personal names under a declared constitution",
          "Define the applicable contract and limits for Mage council title assignment",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model offices and personal names under a declared constitution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model offices and personal names under a declared constitution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:814",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-priesthood-succession-names",
      "slug": "priesthood-succession-names",
      "name": "Priesthood succession names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/priesthood-succession-names/",
        "ja": "/ja/tools/priesthood-succession-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Track repeated religious names and distinguish holders",
      "task": "Track repeated religious names and distinguish holders",
      "searchIntent": {
        "primary": "Complete the task: Track repeated religious names and distinguish holders",
        "queryHypothesis": "priesthood succession names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track repeated religious names and distinguish holders?",
        "When should priesthood succession names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track repeated religious names and distinguish holders",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track repeated religious names and distinguish holders. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-multi-timeline-cast-names",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track repeated religious names and distinguish holders versus Distinguish contemporaries, ancestors and repeated identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-collective-name-succession",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Track repeated religious names and distinguish holders versus Transfer a communal identity without erasing individual histories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-returns-to-family-name",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Track repeated religious names and distinguish holders versus Distinguish reconciliation from pressure to conform; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track repeated religious names and distinguish holders",
        "outline": [
          "Explain the specific decision: Track repeated religious names and distinguish holders",
          "Define the applicable contract and limits for Priesthood succession names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track repeated religious names and distinguish holders; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track repeated religious names and distinguish holders",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:815",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-assassin-order-fictional-identities",
      "slug": "assassin-order-fictional-identities",
      "name": "Assassin order fictional identities",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/assassin-order-fictional-identities/",
        "ja": "/ja/tools/assassin-order-fictional-identities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Focus on narrative continuity and knowledge rather than real evasion",
      "task": "Focus on narrative continuity and knowledge rather than real evasion",
      "searchIntent": {
        "primary": "Complete the task: Focus on narrative continuity and knowledge rather than real evasion",
        "queryHypothesis": "assassin order fictional identities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to focus on narrative continuity and knowledge rather than real evasion?",
        "When should assassin order fictional identities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Focus on narrative continuity and knowledge rather than real evasion",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Focus on narrative continuity and knowledge rather than real evasion. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-witness-protection-fiction-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Focus on narrative continuity and knowledge rather than real evasion versus Design fictional continuity without offering real evasion procedures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-sibling-birth-order-address",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Focus on narrative continuity and knowledge rather than real evasion versus Use a supplied cultural policy rather than infer kin terms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-uploaded-person-identity",
          "score": 0.1392857142857143,
          "sharedProfile": false,
          "difference": "Focus on narrative continuity and knowledge rather than real evasion versus Model continuity claims as story positions rather than scientific fact; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Focus on narrative continuity and knowledge rather than real evasion",
        "outline": [
          "Explain the specific decision: Focus on narrative continuity and knowledge rather than real evasion",
          "Define the applicable contract and limits for Assassin order fictional identities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Focus on narrative continuity and knowledge rather than real evasion; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Focus on narrative continuity and knowledge rather than real evasion",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:816",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-merchant-family-trade-names",
      "slug": "merchant-family-trade-names",
      "name": "Merchant family trade names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/merchant-family-trade-names/",
        "ja": "/ja/tools/merchant-family-trade-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Separate a business label from each household member",
      "task": "Separate a business label from each household member",
      "searchIntent": {
        "primary": "Complete the task: Separate a business label from each household member",
        "queryHypothesis": "merchant family trade names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a business label from each household member?",
        "When should merchant family trade names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a business label from each household member",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a business label from each household member. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-story-annotation",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Separate a business label from each household member versus Label each naming choice and its observable consequence in a supplied passage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-family-generation",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Separate a business label from each household member versus Propagate household rules through a generated settlement graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nonhuman-family-transmission",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Separate a business label from each household member versus Model kinship rules without assuming human household structures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a business label from each household member",
        "outline": [
          "Explain the specific decision: Separate a business label from each household member",
          "Define the applicable contract and limits for Merchant family trade names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a business label from each household member; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a business label from each household member",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:817",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-traveling-caravan-member-references",
      "slug": "traveling-caravan-member-references",
      "name": "Traveling caravan member references",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/traveling-caravan-member-references/",
        "ja": "/ja/tools/traveling-caravan-member-references/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Resolve personal names, duties and group roles in dialogue",
      "task": "Resolve personal names, duties and group roles in dialogue",
      "searchIntent": {
        "primary": "Complete the task: Resolve personal names, duties and group roles in dialogue",
        "queryHypothesis": "traveling caravan member references",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve personal names, duties and group roles in dialogue?",
        "When should traveling caravan member references be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve personal names, duties and group roles in dialogue",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve personal names, duties and group roles in dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-institution-member-name-collision",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Resolve personal names, duties and group roles in dialogue versus Resolve duplicate public names with declared internal conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-expelled-member-references",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Resolve personal names, duties and group roles in dialogue versus Record which titles cease and which personal names remain; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-hospital-drama-staff-references",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Resolve personal names, duties and group roles in dialogue versus Distinguish staff roles, surnames and patient address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve personal names, duties and group roles in dialogue",
        "outline": [
          "Explain the specific decision: Resolve personal names, duties and group roles in dialogue",
          "Define the applicable contract and limits for Traveling caravan member references",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve personal names, duties and group roles in dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve personal names, duties and group roles in dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:818",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-prison-gang-imposed-nicknames",
      "slug": "prison-gang-imposed-nicknames",
      "name": "Prison gang imposed nicknames",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/prison-gang-imposed-nicknames/",
        "ja": "/ja/tools/prison-gang-imposed-nicknames/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Show power and refusal rather than treating labels as neutral",
      "task": "Show power and refusal rather than treating labels as neutral",
      "searchIntent": {
        "primary": "Complete the task: Show power and refusal rather than treating labels as neutral",
        "queryHypothesis": "prison gang imposed nicknames",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show power and refusal rather than treating labels as neutral?",
        "When should prison gang imposed nicknames be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show power and refusal rather than treating labels as neutral",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show power and refusal rather than treating labels as neutral. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-sports-team-character-nicknames",
          "score": 0.20833333333333334,
          "sharedProfile": true,
          "difference": "Show power and refusal rather than treating labels as neutral versus Derive labels from authored team interactions rather than athlete stereotypes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-ensemble-naming",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Show power and refusal rather than treating labels as neutral versus Separate institutional labels from self and peer chosen names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-prison-colony-imposed-labels",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Show power and refusal rather than treating labels as neutral versus Track institutional naming and resistance without endorsing dehumanization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show power and refusal rather than treating labels as neutral",
        "outline": [
          "Explain the specific decision: Show power and refusal rather than treating labels as neutral",
          "Define the applicable contract and limits for Prison gang imposed nicknames",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show power and refusal rather than treating labels as neutral; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show power and refusal rather than treating labels as neutral",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:819",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-school-club-cast-names",
      "slug": "school-club-cast-names",
      "name": "School club cast names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/school-club-cast-names/",
        "ja": "/ja/tools/school-club-cast-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Separate playful member roles from narrator identity",
      "task": "Separate playful member roles from narrator identity",
      "searchIntent": {
        "primary": "Complete the task: Separate playful member roles from narrator identity",
        "queryHypothesis": "school club cast names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate playful member roles from narrator identity?",
        "When should school club cast names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate playful member roles from narrator identity",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate playful member roles from narrator identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-unreliable-name-attribution",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Separate playful member roles from narrator identity versus Separate a narrator's claim from corroborated identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-name-budget",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Separate playful member roles from narrator identity versus Allocate memorable naming signals to narratively important roles; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Separate playful member roles from narrator identity versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate playful member roles from narrator identity",
        "outline": [
          "Explain the specific decision: Separate playful member roles from narrator identity",
          "Define the applicable contract and limits for School club cast names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate playful member roles from narrator identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate playful member roles from narrator identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:820",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-student-council-office-names",
      "slug": "student-council-office-names",
      "name": "Student council office names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/student-council-office-names/",
        "ja": "/ja/tools/student-council-office-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Update office references after elections without replacing character IDs",
      "task": "Update office references after elections without replacing character IDs",
      "searchIntent": {
        "primary": "Complete the task: Update office references after elections without replacing character IDs",
        "queryHypothesis": "student council office names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to update office references after elections without replacing character IDs?",
        "When should student council office names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Update office references after elections without replacing character IDs",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Update office references after elections without replacing character IDs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-rpg-journal-name-refresh",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Update office references after elections without replacing character IDs versus Update references after an identity reveal without rewriting historical facts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-colorist-character-keys",
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Update office references after elections without replacing character IDs versus Map stable IDs to visual references without relying on names alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-title-drift",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Update office references after elections without replacing character IDs versus Compare office references against character promotions and succession; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Update office references after elections without replacing character IDs",
        "outline": [
          "Explain the specific decision: Update office references after elections without replacing character IDs",
          "Define the applicable contract and limits for Student council office names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Update office references after elections without replacing character IDs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Update office references after elections without replacing character IDs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:821",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-court-retainer-identity",
      "slug": "court-retainer-identity",
      "name": "Court retainer identity",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/court-retainer-identity/",
        "ja": "/ja/tools/court-retainer-identity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Track service affiliation and inherited household names independently",
      "task": "Track service affiliation and inherited household names independently",
      "searchIntent": {
        "primary": "Complete the task: Track service affiliation and inherited household names independently",
        "queryHypothesis": "court retainer identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track service affiliation and inherited household names independently?",
        "When should court retainer identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track service affiliation and inherited household names independently",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track service affiliation and inherited household names independently. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-stepfamily-address-map",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Track service affiliation and inherited household names independently versus Distinguish household membership from inherited naming; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Track service affiliation and inherited household names independently versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-house-identity-system",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Track service affiliation and inherited household names independently versus Define house membership and inherited personal components; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track service affiliation and inherited household names independently",
        "outline": [
          "Explain the specific decision: Track service affiliation and inherited household names independently",
          "Define the applicable contract and limits for Court retainer identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track service affiliation and inherited household names independently; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track service affiliation and inherited household names independently",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:822",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-royal-guard-honor-names",
      "slug": "royal-guard-honor-names",
      "name": "Royal guard honor names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/royal-guard-honor-names/",
        "ja": "/ja/tools/royal-guard-honor-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Tie earned names to authored service events and explicit eligibility",
      "task": "Tie earned names to authored service events and explicit eligibility",
      "searchIntent": {
        "primary": "Complete the task: Tie earned names to authored service events and explicit eligibility",
        "queryHypothesis": "royal guard honor names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie earned names to authored service events and explicit eligibility?",
        "When should royal guard honor names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie earned names to authored service events and explicit eligibility",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie earned names to authored service events and explicit eligibility. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-honor-name-pronunciation",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Tie earned names to authored service events and explicit eligibility versus Provide approved spoken forms for formal announcements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-apologizes-through-address",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Tie earned names to authored service events and explicit eligibility versus Compare a changed vocative with an earned behavioral change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-mourning-name-ritual",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Tie earned names to authored service events and explicit eligibility versus Tie memorial references to authored relationships and beliefs; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie earned names to authored service events and explicit eligibility",
        "outline": [
          "Explain the specific decision: Tie earned names to authored service events and explicit eligibility",
          "Define the applicable contract and limits for Royal guard honor names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie earned names to authored service events and explicit eligibility; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie earned names to authored service events and explicit eligibility",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:823",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-fictional-citizenship-name-reform",
      "slug": "fictional-citizenship-name-reform",
      "name": "Fictional citizenship name reform",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/fictional-citizenship-name-reform/",
        "ja": "/ja/tools/fictional-citizenship-name-reform/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Model policy change and individual exceptions over time",
      "task": "Model policy change and individual exceptions over time",
      "searchIntent": {
        "primary": "Complete the task: Model policy change and individual exceptions over time",
        "queryHypothesis": "fictional citizenship name reform",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to model policy change and individual exceptions over time?",
        "When should fictional citizenship name reform be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Model policy change and individual exceptions over time",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Model policy change and individual exceptions over time. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-secular-name-reform",
          "score": 0.26477272727272727,
          "sharedProfile": false,
          "difference": "Model policy change and individual exceptions over time versus Model a culture changing its naming institutions over time; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-names-as-citizenship",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Model policy change and individual exceptions over time versus Separate state assigned recognition from self identity in a fictional regime; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-renaming-transforms-reality",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Model policy change and individual exceptions over time versus Test scope, exceptions and competing claims of a name change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Model policy change and individual exceptions over time",
        "outline": [
          "Explain the specific decision: Model policy change and individual exceptions over time",
          "Define the applicable contract and limits for Fictional citizenship name reform",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Model policy change and individual exceptions over time; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Model policy change and individual exceptions over time",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:824",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-colonial-registry-renaming-fiction",
      "slug": "colonial-registry-renaming-fiction",
      "name": "Colonial registry renaming fiction",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/colonial-registry-renaming-fiction/",
        "ja": "/ja/tools/colonial-registry-renaming-fiction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Distinguish coercive records from self identified names",
      "task": "Distinguish coercive records from self identified names",
      "searchIntent": {
        "primary": "Complete the task: Distinguish coercive records from self identified names",
        "queryHypothesis": "colonial registry renaming fiction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish coercive records from self identified names?",
        "When should colonial registry renaming fiction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish coercive records from self identified names",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish coercive records from self identified names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-intelligence-instance-names",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish coercive records from self identified names versus Distinguish model, instance and self chosen name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-rejects-imposed-title",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Distinguish coercive records from self identified names versus Distinguish self naming from outsiders' reputation labels; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-colonization-name-policy",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Distinguish coercive records from self identified names versus Distinguish imposed labels from self identification in the story; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish coercive records from self identified names",
        "outline": [
          "Explain the specific decision: Distinguish coercive records from self identified names",
          "Define the applicable contract and limits for Colonial registry renaming fiction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish coercive records from self identified names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish coercive records from self identified names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:825",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-resistance-archive-restoration",
      "slug": "resistance-archive-restoration",
      "name": "Resistance archive restoration",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/resistance-archive-restoration/",
        "ja": "/ja/tools/resistance-archive-restoration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Reconcile imposed and restored names with evidence states",
      "task": "Reconcile imposed and restored names with evidence states",
      "searchIntent": {
        "primary": "Complete the task: Reconcile imposed and restored names with evidence states",
        "queryHypothesis": "resistance archive restoration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile imposed and restored names with evidence states?",
        "When should resistance archive restoration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile imposed and restored names with evidence states",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile imposed and restored names with evidence states. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-lost-sibling-reunion-names",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Reconcile imposed and restored names with evidence states versus Reconcile names learned in separate households; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-resistance-names",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Reconcile imposed and restored names with evidence states versus Link chosen forms to authored political acts without real group claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-erased-archive",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Reconcile imposed and restored names with evidence states versus Determine which records survive a fictional erasure event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile imposed and restored names with evidence states",
        "outline": [
          "Explain the specific decision: Reconcile imposed and restored names with evidence states",
          "Define the applicable contract and limits for Resistance archive restoration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile imposed and restored names with evidence states; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile imposed and restored names with evidence states",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:826",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-magical-contract-signatory-names",
      "slug": "magical-contract-signatory-names",
      "name": "Magical contract signatory names",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/magical-contract-signatory-names/",
        "ja": "/ja/tools/magical-contract-signatory-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Define which identity form a fictional contract recognizes",
      "task": "Define which identity form a fictional contract recognizes",
      "searchIntent": {
        "primary": "Complete the task: Define which identity form a fictional contract recognizes",
        "queryHypothesis": "magical contract signatory names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to define which identity form a fictional contract recognizes?",
        "When should magical contract signatory names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Define which identity form a fictional contract recognizes",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Define which identity form a fictional contract recognizes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-true-name-spell-contract",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Define which identity form a fictional contract recognizes versus Define exactly which name form grants which fictional capability; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dream-name-memory-anchor",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Define which identity form a fictional contract recognizes versus Define which form persists between dream and waking scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-reconciles-dual-identities",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Define which identity form a fictional contract recognizes versus Define which differences remain after integration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Define which identity form a fictional contract recognizes",
        "outline": [
          "Explain the specific decision: Define which identity form a fictional contract recognizes",
          "Define the applicable contract and limits for Magical contract signatory names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Define which identity form a fictional contract recognizes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Define which identity form a fictional contract recognizes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:827",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-clone-cohort-member-labels",
      "slug": "clone-cohort-member-labels",
      "name": "Clone cohort member labels",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/clone-cohort-member-labels/",
        "ja": "/ja/tools/clone-cohort-member-labels/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Preserve individuality while recording a shared biological origin",
      "task": "Preserve individuality while recording a shared biological origin",
      "searchIntent": {
        "primary": "Complete the task: Preserve individuality while recording a shared biological origin",
        "queryHypothesis": "clone cohort member labels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve individuality while recording a shared biological origin?",
        "When should clone cohort member labels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve individuality while recording a shared biological origin",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve individuality while recording a shared biological origin. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-invented-language-names",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve individuality while recording a shared biological origin versus Preserve fictional grammar while adapting script; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-pronunciation-notes",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Preserve individuality while recording a shared biological origin versus Provide recording references approved by the creator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-academy-cohort-naming",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Preserve individuality while recording a shared biological origin versus Decide whether cohort labels belong in public personal references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve individuality while recording a shared biological origin",
        "outline": [
          "Explain the specific decision: Preserve individuality while recording a shared biological origin",
          "Define the applicable contract and limits for Clone cohort member labels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve individuality while recording a shared biological origin; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve individuality while recording a shared biological origin",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:829",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-immortal-order-alias-archive",
      "slug": "immortal-order-alias-archive",
      "name": "Immortal order alias archive",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/immortal-order-alias-archive/",
        "ja": "/ja/tools/immortal-order-alias-archive/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Track dated public names without flattening a long identity history",
      "task": "Track dated public names without flattening a long identity history",
      "searchIntent": {
        "primary": "Complete the task: Track dated public names without flattening a long identity history",
        "queryHypothesis": "immortal order alias archive",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track dated public names without flattening a long identity history?",
        "When should immortal order alias archive be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track dated public names without flattening a long identity history",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track dated public names without flattening a long identity history. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-immortal-historical-aliases",
          "score": 0.22083333333333333,
          "sharedProfile": false,
          "difference": "Track dated public names without flattening a long identity history versus Maintain a dated identity chain without fabricated historical records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reincarnation-cast-mapping",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Track dated public names without flattening a long identity history versus Track identity continuity without revealing it in public references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-continuity-contradiction-scan",
          "score": 0.16818181818181818,
          "sharedProfile": false,
          "difference": "Track dated public names without flattening a long identity history versus Find incompatible forms in dated identity appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track dated public names without flattening a long identity history",
        "outline": [
          "Explain the specific decision: Track dated public names without flattening a long identity history",
          "Define the applicable contract and limits for Immortal order alias archive",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track dated public names without flattening a long identity history; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track dated public names without flattening a long identity history",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:830",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-institution-expelled-member-references",
      "slug": "institution-expelled-member-references",
      "name": "Institution expelled member references",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/institution-expelled-member-references/",
        "ja": "/ja/tools/institution-expelled-member-references/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Record which titles cease and which personal names remain",
      "task": "Record which titles cease and which personal names remain",
      "searchIntent": {
        "primary": "Complete the task: Record which titles cease and which personal names remain",
        "queryHypothesis": "institution expelled member references",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record which titles cease and which personal names remain?",
        "When should institution expelled member references be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record which titles cease and which personal names remain",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record which titles cease and which personal names remain. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-reconciles-dual-identities",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Record which titles cease and which personal names remain versus Define which differences remain after integration; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-map-npc-label-priority",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Record which titles cease and which personal names remain versus Decide which names remain visible when labels overlap; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-member-name-collision",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Record which titles cease and which personal names remain versus Resolve duplicate public names with declared internal conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record which titles cease and which personal names remain",
        "outline": [
          "Explain the specific decision: Record which titles cease and which personal names remain",
          "Define the applicable contract and limits for Institution expelled member references",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record which titles cease and which personal names remain; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record which titles cease and which personal names remain",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:831",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-institution-merged-identity-systems",
      "slug": "institution-merged-identity-systems",
      "name": "Institution merged identity systems",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/institution-merged-identity-systems/",
        "ja": "/ja/tools/institution-merged-identity-systems/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Reconcile naming rules after two fictional organizations combine",
      "task": "Reconcile naming rules after two fictional organizations combine",
      "searchIntent": {
        "primary": "Complete the task: Reconcile naming rules after two fictional organizations combine",
        "queryHypothesis": "institution merged identity systems",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile naming rules after two fictional organizations combine?",
        "When should institution merged identity systems be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile naming rules after two fictional organizations combine",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile naming rules after two fictional organizations combine. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-campaign-lore-naming-conflict",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Reconcile naming rules after two fictional organizations combine versus Reconcile two contributor supplied naming conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-intermarried-fictional-houses",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Reconcile naming rules after two fictional organizations combine versus Reconcile two invented inheritance policies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-undersea-settlement-identity",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Reconcile naming rules after two fictional organizations combine versus Connect communication constraints to personal naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile naming rules after two fictional organizations combine",
        "outline": [
          "Explain the specific decision: Reconcile naming rules after two fictional organizations combine",
          "Define the applicable contract and limits for Institution merged identity systems",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile naming rules after two fictional organizations combine; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile naming rules after two fictional organizations combine",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:832",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-institution-member-name-collision",
      "slug": "institution-member-name-collision",
      "name": "Institution member name collision",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/institution-member-name-collision/",
        "ja": "/ja/tools/institution-member-name-collision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Resolve duplicate public names with declared internal conventions",
      "task": "Resolve duplicate public names with declared internal conventions",
      "searchIntent": {
        "primary": "Complete the task: Resolve duplicate public names with declared internal conventions",
        "queryHypothesis": "institution member name collision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve duplicate public names with declared internal conventions?",
        "When should institution member name collision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve duplicate public names with declared internal conventions",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve duplicate public names with declared internal conventions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-institution-expelled-member-references",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Resolve duplicate public names with declared internal conventions versus Record which titles cease and which personal names remain; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-traveling-caravan-member-references",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Resolve duplicate public names with declared internal conventions versus Resolve personal names, duties and group roles in dialogue; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-fictional-name-charter",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Resolve duplicate public names with declared internal conventions versus Export membership, naming authority and exceptions as a usable guide; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve duplicate public names with declared internal conventions",
        "outline": [
          "Explain the specific decision: Resolve duplicate public names with declared internal conventions",
          "Define the applicable contract and limits for Institution member name collision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve duplicate public names with declared internal conventions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve duplicate public names with declared internal conventions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:833",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-institution-fictional-name-charter",
      "slug": "institution-fictional-name-charter",
      "name": "Institution fictional name charter",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/institution-fictional-name-charter/",
        "ja": "/ja/tools/institution-fictional-name-charter/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Export membership, naming authority and exceptions as a usable guide",
      "task": "Export membership, naming authority and exceptions as a usable guide",
      "searchIntent": {
        "primary": "Complete the task: Export membership, naming authority and exceptions as a usable guide",
        "queryHypothesis": "institution fictional name charter",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export membership, naming authority and exceptions as a usable guide?",
        "When should institution fictional name charter be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export membership, naming authority and exceptions as a usable guide",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export membership, naming authority and exceptions as a usable guide. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-institution-member-name-collision",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Export membership, naming authority and exceptions as a usable guide versus Resolve duplicate public names with declared internal conventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-institution-naming-power-audit",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Export membership, naming authority and exceptions as a usable guide versus Identify who can assign, refuse or change a personal label; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Export membership, naming authority and exceptions as a usable guide versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export membership, naming authority and exceptions as a usable guide",
        "outline": [
          "Explain the specific decision: Export membership, naming authority and exceptions as a usable guide",
          "Define the applicable contract and limits for Institution fictional name charter",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export membership, naming authority and exceptions as a usable guide; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export membership, naming authority and exceptions as a usable guide",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:834",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-institution-naming-power-audit",
      "slug": "institution-naming-power-audit",
      "name": "Institution naming power audit",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/institution-naming-power-audit/",
        "ja": "/ja/tools/institution-naming-power-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Identify who can assign, refuse or change a personal label",
      "task": "Identify who can assign, refuse or change a personal label",
      "searchIntent": {
        "primary": "Complete the task: Identify who can assign, refuse or change a personal label",
        "queryHypothesis": "institution naming power audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify who can assign, refuse or change a personal label?",
        "When should institution naming power audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify who can assign, refuse or change a personal label",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify who can assign, refuse or change a personal label. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-scene-cooccurrence-name-audit",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Identify who can assign, refuse or change a personal label versus Prioritize collisions between characters who share scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-time-loop-alias-experiment",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Identify who can assign, refuse or change a personal label versus Record changing aliases and who can detect the pattern; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-reclaimed-insult-name",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Identify who can assign, refuse or change a personal label versus Trace who may use a reclaimed label and when; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify who can assign, refuse or change a personal label",
        "outline": [
          "Explain the specific decision: Identify who can assign, refuse or change a personal label",
          "Define the applicable contract and limits for Institution naming power audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify who can assign, refuse or change a personal label; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify who can assign, refuse or change a personal label",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:835",
      "profileSource": "data/profiles.json#institutions"
    },
    {
      "id": "nw-historical-character-name-research",
      "slug": "historical-character-name-research",
      "name": "Historical character name research",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-character-name-research/",
        "ja": "/ja/tools/historical-character-name-research/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Specify period, place, language and evidence before generating candidates",
      "task": "Specify period, place, language and evidence before generating candidates",
      "searchIntent": {
        "primary": "Complete the task: Specify period, place, language and evidence before generating candidates",
        "queryHypothesis": "historical character name research",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to specify period, place, language and evidence before generating candidates?",
        "When should historical character name research be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Specify period, place, language and evidence before generating candidates",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Specify period, place, language and evidence before generating candidates. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-historical-name-research-brief",
          "score": 0.3375,
          "sharedProfile": false,
          "difference": "Specify period, place, language and evidence before generating candidates versus Specify period, locality and sources before candidate generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.2833333333333333,
          "sharedProfile": true,
          "difference": "Specify period, place, language and evidence before generating candidates versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-marriage-name-research",
          "score": 0.2333333333333333,
          "sharedProfile": true,
          "difference": "Specify period, place, language and evidence before generating candidates versus Avoid projecting current naming conventions onto past settings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Specify period, place, language and evidence before generating candidates",
        "outline": [
          "Explain the specific decision: Specify period, place, language and evidence before generating candidates",
          "Define the applicable contract and limits for Historical character name research",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Specify period, place, language and evidence before generating candidates; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Specify period, place, language and evidence before generating candidates",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:838",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-surname-locality-check",
      "slug": "historical-surname-locality-check",
      "name": "Historical surname locality check",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-surname-locality-check/",
        "ja": "/ja/tools/historical-surname-locality-check/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Record geographic evidence without claiming universal distribution",
      "task": "Record geographic evidence without claiming universal distribution",
      "searchIntent": {
        "primary": "Complete the task: Record geographic evidence without claiming universal distribution",
        "queryHypothesis": "historical surname locality check",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record geographic evidence without claiming universal distribution?",
        "When should historical surname locality check be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record geographic evidence without claiming universal distribution",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record geographic evidence without claiming universal distribution. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Record geographic evidence without claiming universal distribution versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-katakana-identity-choice",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Record geographic evidence without claiming universal distribution versus Explain author selected script effects without claiming universal meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-court-name-forms",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Record geographic evidence without claiming universal distribution versus Record local conventions with explicit evidence limitations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record geographic evidence without claiming universal distribution",
        "outline": [
          "Explain the specific decision: Record geographic evidence without claiming universal distribution",
          "Define the applicable contract and limits for Historical surname locality check",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record geographic evidence without claiming universal distribution; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record geographic evidence without claiming universal distribution",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:840",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-spelling-ledger",
      "slug": "historical-name-spelling-ledger",
      "name": "Historical name spelling ledger",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-spelling-ledger/",
        "ja": "/ja/tools/historical-name-spelling-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Preserve source spelling, normalized form and editorial decision",
      "task": "Preserve source spelling, normalized form and editorial decision",
      "searchIntent": {
        "primary": "Complete the task: Preserve source spelling, normalized form and editorial decision",
        "queryHypothesis": "historical name spelling ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve source spelling, normalized form and editorial decision?",
        "When should historical name spelling ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve source spelling, normalized form and editorial decision",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve source spelling, normalized form and editorial decision. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-parish-record-naming",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Preserve source spelling, normalized form and editorial decision versus Distinguish transcription uncertainty from source attestation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-bibliography-export",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve source spelling, normalized form and editorial decision versus Produce source linked references for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-story-naming-exception",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve source spelling, normalized form and editorial decision versus Explain an intentional departure in an editorial note; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve source spelling, normalized form and editorial decision",
        "outline": [
          "Explain the specific decision: Preserve source spelling, normalized form and editorial decision",
          "Define the applicable contract and limits for Historical name spelling ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve source spelling, normalized form and editorial decision; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve source spelling, normalized form and editorial decision",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:841",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-title-evidence-file",
      "slug": "historical-title-evidence-file",
      "name": "Historical title evidence file",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-title-evidence-file/",
        "ja": "/ja/tools/historical-title-evidence-file/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Separate attested office forms from fictional inventions",
      "task": "Separate attested office forms from fictional inventions",
      "searchIntent": {
        "primary": "Complete the task: Separate attested office forms from fictional inventions",
        "queryHypothesis": "historical title evidence file",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate attested office forms from fictional inventions?",
        "When should historical title evidence file be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate attested office forms from fictional inventions",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate attested office forms from fictional inventions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-royal-title-address-matrix",
          "score": 0.2125,
          "sharedProfile": false,
          "difference": "Separate attested office forms from fictional inventions versus Resolve forms by office, speaker and political recognition; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pseudonym-evidence",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Separate attested office forms from fictional inventions versus Distinguish documented pseudonyms from author invented analogues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Separate attested office forms from fictional inventions versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate attested office forms from fictional inventions",
        "outline": [
          "Explain the specific decision: Separate attested office forms from fictional inventions",
          "Define the applicable contract and limits for Historical title evidence file",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate attested office forms from fictional inventions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate attested office forms from fictional inventions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:842",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-address-scene-audit",
      "slug": "historical-address-scene-audit",
      "name": "Historical address scene audit",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-address-scene-audit/",
        "ja": "/ja/tools/historical-address-scene-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Check speaker relationship and source limits for one scene",
      "task": "Check speaker relationship and source limits for one scene",
      "searchIntent": {
        "primary": "Complete the task: Check speaker relationship and source limits for one scene",
        "queryHypothesis": "historical address scene audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check speaker relationship and source limits for one scene?",
        "When should historical address scene audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check speaker relationship and source limits for one scene",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check speaker relationship and source limits for one scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.19444444444444442,
          "sharedProfile": false,
          "difference": "Check speaker relationship and source limits for one scene versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-continuity-audit",
          "score": 0.19,
          "sharedProfile": false,
          "difference": "Check speaker relationship and source limits for one scene versus Find speaker pairs using unearned levels of familiarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Check speaker relationship and source limits for one scene versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check speaker relationship and source limits for one scene",
        "outline": [
          "Explain the specific decision: Check speaker relationship and source limits for one scene",
          "Define the applicable contract and limits for Historical address scene audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check speaker relationship and source limits for one scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check speaker relationship and source limits for one scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:843",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-naming-anachronism-review",
      "slug": "historical-naming-anachronism-review",
      "name": "Historical naming anachronism review",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-naming-anachronism-review/",
        "ja": "/ja/tools/historical-naming-anachronism-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Flag unsupported forms rather than manufacture certainty",
      "task": "Flag unsupported forms rather than manufacture certainty",
      "searchIntent": {
        "primary": "Complete the task: Flag unsupported forms rather than manufacture certainty",
        "queryHypothesis": "historical naming anachronism review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag unsupported forms rather than manufacture certainty?",
        "When should historical naming anachronism review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag unsupported forms rather than manufacture certainty",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag unsupported forms rather than manufacture certainty. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alternate-history-name-divergence",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Flag unsupported forms rather than manufacture certainty versus Trace the authored divergence rather than invent historical certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-era-mismatch-review",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Flag unsupported forms rather than manufacture certainty versus Flag unsupported period claims for a specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-nickname-attestation",
          "score": 0.16999999999999998,
          "sharedProfile": true,
          "difference": "Flag unsupported forms rather than manufacture certainty versus Require usage evidence rather than modern connotation alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag unsupported forms rather than manufacture certainty",
        "outline": [
          "Explain the specific decision: Flag unsupported forms rather than manufacture certainty",
          "Define the applicable contract and limits for Historical naming anachronism review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag unsupported forms rather than manufacture certainty; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag unsupported forms rather than manufacture certainty",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:844",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-adoption-name-research",
      "slug": "historical-adoption-name-research",
      "name": "Historical adoption name research",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-adoption-name-research/",
        "ja": "/ja/tools/historical-adoption-name-research/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Identify jurisdiction and period questions for specialist review",
      "task": "Identify jurisdiction and period questions for specialist review",
      "searchIntent": {
        "primary": "Complete the task: Identify jurisdiction and period questions for specialist review",
        "queryHypothesis": "historical adoption name research",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify jurisdiction and period questions for specialist review?",
        "When should historical adoption name research be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify jurisdiction and period questions for specialist review",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify jurisdiction and period questions for specialist review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.2833333333333333,
          "sharedProfile": true,
          "difference": "Identify jurisdiction and period questions for specialist review versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-era-mismatch-review",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Identify jurisdiction and period questions for specialist review versus Flag unsupported period claims for a specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-cast-evidence-coverage",
          "score": 0.20277777777777775,
          "sharedProfile": true,
          "difference": "Identify jurisdiction and period questions for specialist review versus Identify characters with no period appropriate support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify jurisdiction and period questions for specialist review",
        "outline": [
          "Explain the specific decision: Identify jurisdiction and period questions for specialist review",
          "Define the applicable contract and limits for Historical adoption name research",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify jurisdiction and period questions for specialist review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify jurisdiction and period questions for specialist review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:845",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-marriage-name-research",
      "slug": "historical-marriage-name-research",
      "name": "Historical marriage name research",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-marriage-name-research/",
        "ja": "/ja/tools/historical-marriage-name-research/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Avoid projecting current naming conventions onto past settings",
      "task": "Avoid projecting current naming conventions onto past settings",
      "searchIntent": {
        "primary": "Complete the task: Avoid projecting current naming conventions onto past settings",
        "queryHypothesis": "historical marriage name research",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid projecting current naming conventions onto past settings?",
        "When should historical marriage name research be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid projecting current naming conventions onto past settings",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid projecting current naming conventions onto past settings. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.2333333333333333,
          "sharedProfile": true,
          "difference": "Avoid projecting current naming conventions onto past settings versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Avoid projecting current naming conventions onto past settings versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-historical-name-research-brief",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Avoid projecting current naming conventions onto past settings versus Specify period, locality and sources before candidate generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid projecting current naming conventions onto past settings",
        "outline": [
          "Explain the specific decision: Avoid projecting current naming conventions onto past settings",
          "Define the applicable contract and limits for Historical marriage name research",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid projecting current naming conventions onto past settings; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid projecting current naming conventions onto past settings",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:846",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-migration-name-records",
      "slug": "historical-migration-name-records",
      "name": "Historical migration name records",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-migration-name-records/",
        "ja": "/ja/tools/historical-migration-name-records/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Trace documented variants without assuming identity from similarity",
      "task": "Trace documented variants without assuming identity from similarity",
      "searchIntent": {
        "primary": "Complete the task: Trace documented variants without assuming identity from similarity",
        "queryHypothesis": "historical migration name records",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace documented variants without assuming identity from similarity?",
        "When should historical migration name records be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace documented variants without assuming identity from similarity",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace documented variants without assuming identity from similarity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-voicing-variation-ledger",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace documented variants without assuming identity from similarity versus Store documented variants without inventing alternation rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-refugee-character-naming",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Trace documented variants without assuming identity from similarity versus Preserve chosen identity without assuming displacement erases culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-immortal-historical-aliases",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Trace documented variants without assuming identity from similarity versus Maintain a dated identity chain without fabricated historical records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace documented variants without assuming identity from similarity",
        "outline": [
          "Explain the specific decision: Trace documented variants without assuming identity from similarity",
          "Define the applicable contract and limits for Historical migration name records",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace documented variants without assuming identity from similarity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace documented variants without assuming identity from similarity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:847",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-census-candidate-extraction",
      "slug": "historical-census-candidate-extraction",
      "name": "Historical census candidate extraction",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-census-candidate-extraction/",
        "ja": "/ja/tools/historical-census-candidate-extraction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Log provenance and license before importing name data",
      "task": "Log provenance and license before importing name data",
      "searchIntent": {
        "primary": "Complete the task: Log provenance and license before importing name data",
        "queryHypothesis": "historical census candidate extraction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to log provenance and license before importing name data?",
        "When should historical census candidate extraction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Log provenance and license before importing name data",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Log provenance and license before importing name data. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Log provenance and license before importing name data versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-frequency-caveat",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Log provenance and license before importing name data versus Explain archive bias and missing populations in supplied data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-personal-name-dataset-intake",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Log provenance and license before importing name data versus Validate provenance, permitted use and structural fields before import; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Log provenance and license before importing name data",
        "outline": [
          "Explain the specific decision: Log provenance and license before importing name data",
          "Define the applicable contract and limits for Historical census candidate extraction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Log provenance and license before importing name data; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Log provenance and license before importing name data",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:848",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-parish-record-naming",
      "slug": "historical-parish-record-naming",
      "name": "Historical parish record naming",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-parish-record-naming/",
        "ja": "/ja/tools/historical-parish-record-naming/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Distinguish transcription uncertainty from source attestation",
      "task": "Distinguish transcription uncertainty from source attestation",
      "searchIntent": {
        "primary": "Complete the task: Distinguish transcription uncertainty from source attestation",
        "queryHypothesis": "historical parish record naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish transcription uncertainty from source attestation?",
        "When should historical parish record naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish transcription uncertainty from source attestation",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish transcription uncertainty from source attestation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-bibliography-export",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Distinguish transcription uncertainty from source attestation versus Produce source linked references for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-archive-name-uncertainty",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Distinguish transcription uncertainty from source attestation versus Store competing readings and confidence with source images; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-fact-annotation",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Distinguish transcription uncertainty from source attestation versus Label attestation, inference and invention at claim level; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish transcription uncertainty from source attestation",
        "outline": [
          "Explain the specific decision: Distinguish transcription uncertainty from source attestation",
          "Define the applicable contract and limits for Historical parish record naming",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish transcription uncertainty from source attestation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish transcription uncertainty from source attestation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:849",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-archive-name-uncertainty",
      "slug": "historical-archive-name-uncertainty",
      "name": "Historical archive name uncertainty",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-archive-name-uncertainty/",
        "ja": "/ja/tools/historical-archive-name-uncertainty/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Store competing readings and confidence with source images",
      "task": "Store competing readings and confidence with source images",
      "searchIntent": {
        "primary": "Complete the task: Store competing readings and confidence with source images",
        "queryHypothesis": "historical archive name uncertainty",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to store competing readings and confidence with source images?",
        "When should historical archive name uncertainty be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Store competing readings and confidence with source images",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Store competing readings and confidence with source images. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-reading-uncertainty",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Store competing readings and confidence with source images versus Preserve multiple readings with source specific confidence notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pronunciation-uncertainty",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Store competing readings and confidence with source images versus Present known limits instead of confident reconstructed audio; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-parish-record-naming",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Store competing readings and confidence with source images versus Distinguish transcription uncertainty from source attestation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Store competing readings and confidence with source images",
        "outline": [
          "Explain the specific decision: Store competing readings and confidence with source images",
          "Define the applicable contract and limits for Historical archive name uncertainty",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Store competing readings and confidence with source images; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Store competing readings and confidence with source images",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:850",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-fiction-composite-names",
      "slug": "historical-fiction-composite-names",
      "name": "Historical fiction composite names",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-fiction-composite-names/",
        "ja": "/ja/tools/historical-fiction-composite-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Document invented combinations and avoid presenting them as attested",
      "task": "Document invented combinations and avoid presenting them as attested",
      "searchIntent": {
        "primary": "Complete the task: Document invented combinations and avoid presenting them as attested",
        "queryHypothesis": "historical fiction composite names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to document invented combinations and avoid presenting them as attested?",
        "When should historical fiction composite names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Document invented combinations and avoid presenting them as attested",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Document invented combinations and avoid presenting them as attested. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-pseudonym-evidence",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Document invented combinations and avoid presenting them as attested versus Distinguish documented pseudonyms from author invented analogues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-podcast-fiction-guest-names",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Document invented combinations and avoid presenting them as attested versus Avoid confusion between returning and one episode characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-title-evidence-file",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Document invented combinations and avoid presenting them as attested versus Separate attested office forms from fictional inventions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Document invented combinations and avoid presenting them as attested",
        "outline": [
          "Explain the specific decision: Document invented combinations and avoid presenting them as attested",
          "Define the applicable contract and limits for Historical fiction composite names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Document invented combinations and avoid presenting them as attested; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Document invented combinations and avoid presenting them as attested",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:851",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-real-person-name-boundary",
      "slug": "historical-real-person-name-boundary",
      "name": "Historical real person name boundary",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-real-person-name-boundary/",
        "ja": "/ja/tools/historical-real-person-name-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Separate a fictional character from a real person's biography",
      "task": "Separate a fictional character from a real person's biography",
      "searchIntent": {
        "primary": "Complete the task: Separate a fictional character from a real person's biography",
        "queryHypothesis": "historical real person name boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a fictional character from a real person's biography?",
        "When should historical real person name boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a fictional character from a real person's biography",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a fictional character from a real person's biography. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-digital-ghost-account-identity",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Separate a fictional character from a real person's biography versus Separate a deceased person's account from a simulated character; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-identity-boundary",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Separate a fictional character from a real person's biography versus Record what public biography may connect to a private identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-magic-privacy-boundary",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Separate a fictional character from a real person's biography versus Define information access without implying real magical practices; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a fictional character from a real person's biography",
        "outline": [
          "Explain the specific decision: Separate a fictional character from a real person's biography",
          "Define the applicable contract and limits for Historical real person name boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a fictional character from a real person's biography; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a fictional character from a real person's biography",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:852",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-religious-name-evidence",
      "slug": "historical-religious-name-evidence",
      "name": "Historical religious name evidence",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-religious-name-evidence/",
        "ja": "/ja/tools/historical-religious-name-evidence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Require community and period specific sources",
      "task": "Require community and period specific sources",
      "searchIntent": {
        "primary": "Complete the task: Require community and period specific sources",
        "queryHypothesis": "historical religious name evidence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require community and period specific sources?",
        "When should historical religious name evidence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require community and period specific sources",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require community and period specific sources. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.25625,
          "sharedProfile": false,
          "difference": "Require community and period specific sources versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-cast-evidence-coverage",
          "score": 0.2122222222222222,
          "sharedProfile": true,
          "difference": "Require community and period specific sources versus Identify characters with no period appropriate support; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-historical-name-research-brief",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Require community and period specific sources versus Specify period, locality and sources before candidate generation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require community and period specific sources",
        "outline": [
          "Explain the specific decision: Require community and period specific sources",
          "Define the applicable contract and limits for Historical religious name evidence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require community and period specific sources; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require community and period specific sources",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:853",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-military-title-reference",
      "slug": "historical-military-title-reference",
      "name": "Historical military title reference",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-military-title-reference/",
        "ja": "/ja/tools/historical-military-title-reference/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Tie titles to a defined institution and date range",
      "task": "Tie titles to a defined institution and date range",
      "searchIntent": {
        "primary": "Complete the task: Tie titles to a defined institution and date range",
        "queryHypothesis": "historical military title reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to tie titles to a defined institution and date range?",
        "When should historical military title reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Tie titles to a defined institution and date range",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Tie titles to a defined institution and date range. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-earned-title-progression",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Tie titles to a defined institution and date range versus Sequence titles across actual narrative achievements; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-title-identity-map",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Tie titles to a defined institution and date range versus Separate translated titles from stable personal identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-campaign-title-reward",
          "score": 0.11742424242424243,
          "sharedProfile": false,
          "difference": "Tie titles to a defined institution and date range versus Create earned titles tied to actual in game actions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Tie titles to a defined institution and date range",
        "outline": [
          "Explain the specific decision: Tie titles to a defined institution and date range",
          "Define the applicable contract and limits for Historical military title reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Tie titles to a defined institution and date range; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Tie titles to a defined institution and date range",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:854",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-court-name-forms",
      "slug": "historical-court-name-forms",
      "name": "Historical court name forms",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-court-name-forms/",
        "ja": "/ja/tools/historical-court-name-forms/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Record local conventions with explicit evidence limitations",
      "task": "Record local conventions with explicit evidence limitations",
      "searchIntent": {
        "primary": "Complete the task: Record local conventions with explicit evidence limitations",
        "queryHypothesis": "historical court name forms",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record local conventions with explicit evidence limitations?",
        "When should historical court name forms be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record local conventions with explicit evidence limitations",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record local conventions with explicit evidence limitations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-character-name-research",
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Record local conventions with explicit evidence limitations versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-specialist-handoff",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Record local conventions with explicit evidence limitations versus Package exact questions and candidate evidence for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-historical-name-note",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Record local conventions with explicit evidence limitations versus Attach evidence gaps to exact occurrences for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record local conventions with explicit evidence limitations",
        "outline": [
          "Explain the specific decision: Record local conventions with explicit evidence limitations",
          "Define the applicable contract and limits for Historical court name forms",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record local conventions with explicit evidence limitations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record local conventions with explicit evidence limitations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:855",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-pseudonym-evidence",
      "slug": "historical-pseudonym-evidence",
      "name": "Historical pseudonym evidence",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-pseudonym-evidence/",
        "ja": "/ja/tools/historical-pseudonym-evidence/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Distinguish documented pseudonyms from author invented analogues",
      "task": "Distinguish documented pseudonyms from author invented analogues",
      "searchIntent": {
        "primary": "Complete the task: Distinguish documented pseudonyms from author invented analogues",
        "queryHypothesis": "historical pseudonym evidence",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish documented pseudonyms from author invented analogues?",
        "When should historical pseudonym evidence be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish documented pseudonyms from author invented analogues",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish documented pseudonyms from author invented analogues. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Distinguish documented pseudonyms from author invented analogues versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Distinguish documented pseudonyms from author invented analogues versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Distinguish documented pseudonyms from author invented analogues versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish documented pseudonyms from author invented analogues",
        "outline": [
          "Explain the specific decision: Distinguish documented pseudonyms from author invented analogues",
          "Define the applicable contract and limits for Historical pseudonym evidence",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish documented pseudonyms from author invented analogues; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish documented pseudonyms from author invented analogues",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:856",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-nickname-attestation",
      "slug": "historical-nickname-attestation",
      "name": "Historical nickname attestation",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-nickname-attestation/",
        "ja": "/ja/tools/historical-nickname-attestation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Require usage evidence rather than modern connotation alone",
      "task": "Require usage evidence rather than modern connotation alone",
      "searchIntent": {
        "primary": "Complete the task: Require usage evidence rather than modern connotation alone",
        "queryHypothesis": "historical nickname attestation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require usage evidence rather than modern connotation alone?",
        "When should historical nickname attestation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require usage evidence rather than modern connotation alone",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require usage evidence rather than modern connotation alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-naming-anachronism-review",
          "score": 0.16999999999999998,
          "sharedProfile": true,
          "difference": "Require usage evidence rather than modern connotation alone versus Flag unsupported forms rather than manufacture certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stolen-family-name-motive",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Require usage evidence rather than modern connotation alone versus Connect naming conflict to character stakes rather than a puzzle alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-character-name-research",
          "score": 0.13083333333333333,
          "sharedProfile": true,
          "difference": "Require usage evidence rather than modern connotation alone versus Specify period, place, language and evidence before generating candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require usage evidence rather than modern connotation alone",
        "outline": [
          "Explain the specific decision: Require usage evidence rather than modern connotation alone",
          "Define the applicable contract and limits for Historical nickname attestation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require usage evidence rather than modern connotation alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require usage evidence rather than modern connotation alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:857",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-frequency-caveat",
      "slug": "historical-name-frequency-caveat",
      "name": "Historical name frequency caveat",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-frequency-caveat/",
        "ja": "/ja/tools/historical-name-frequency-caveat/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Explain archive bias and missing populations in supplied data",
      "task": "Explain archive bias and missing populations in supplied data",
      "searchIntent": {
        "primary": "Complete the task: Explain archive bias and missing populations in supplied data",
        "queryHypothesis": "historical name frequency caveat",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain archive bias and missing populations in supplied data?",
        "When should historical name frequency caveat be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain archive bias and missing populations in supplied data",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain archive bias and missing populations in supplied data. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-story-naming-exception",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Explain archive bias and missing populations in supplied data versus Explain an intentional departure in an editorial note; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Explain archive bias and missing populations in supplied data versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-census-candidate-extraction",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Explain archive bias and missing populations in supplied data versus Log provenance and license before importing name data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain archive bias and missing populations in supplied data",
        "outline": [
          "Explain the specific decision: Explain archive bias and missing populations in supplied data",
          "Define the applicable contract and limits for Historical name frequency caveat",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain archive bias and missing populations in supplied data; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain archive bias and missing populations in supplied data",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:858",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-transliteration-policy",
      "slug": "historical-transliteration-policy",
      "name": "Historical transliteration policy",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-transliteration-policy/",
        "ja": "/ja/tools/historical-transliteration-policy/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Record original script, source romanization and house style",
      "task": "Record original script, source romanization and house style",
      "searchIntent": {
        "primary": "Complete the task: Record original script, source romanization and house style",
        "queryHypothesis": "historical transliteration policy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record original script, source romanization and house style?",
        "When should historical transliteration policy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record original script, source romanization and house style",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record original script, source romanization and house style. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-parish-record-naming",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Record original script, source romanization and house style versus Distinguish transcription uncertainty from source attestation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-bibliography-export",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Record original script, source romanization and house style versus Produce source linked references for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-obsolete-glyph-handling",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Record original script, source romanization and house style versus Preserve original and readable fallback separately; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record original script, source romanization and house style",
        "outline": [
          "Explain the specific decision: Record original script, source romanization and house style",
          "Define the applicable contract and limits for Historical transliteration policy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record original script, source romanization and house style; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record original script, source romanization and house style",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:859",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-obsolete-glyph-handling",
      "slug": "historical-obsolete-glyph-handling",
      "name": "Historical obsolete glyph handling",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-obsolete-glyph-handling/",
        "ja": "/ja/tools/historical-obsolete-glyph-handling/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Preserve original and readable fallback separately",
      "task": "Preserve original and readable fallback separately",
      "searchIntent": {
        "primary": "Complete the task: Preserve original and readable fallback separately",
        "queryHypothesis": "historical obsolete glyph handling",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve original and readable fallback separately?",
        "When should historical obsolete glyph handling be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve original and readable fallback separately",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve original and readable fallback separately. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Preserve original and readable fallback separately versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-glyph-fidelity",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Preserve original and readable fallback separately versus Preserve source glyphs separately from search normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-transliteration-policy",
          "score": 0.13055555555555554,
          "sharedProfile": true,
          "difference": "Preserve original and readable fallback separately versus Record original script, source romanization and house style; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve original and readable fallback separately",
        "outline": [
          "Explain the specific decision: Preserve original and readable fallback separately",
          "Define the applicable contract and limits for Historical obsolete glyph handling",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve original and readable fallback separately; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve original and readable fallback separately",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:860",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-pronunciation-uncertainty",
      "slug": "historical-pronunciation-uncertainty",
      "name": "Historical pronunciation uncertainty",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-pronunciation-uncertainty/",
        "ja": "/ja/tools/historical-pronunciation-uncertainty/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Present known limits instead of confident reconstructed audio",
      "task": "Present known limits instead of confident reconstructed audio",
      "searchIntent": {
        "primary": "Complete the task: Present known limits instead of confident reconstructed audio",
        "queryHypothesis": "historical pronunciation uncertainty",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to present known limits instead of confident reconstructed audio?",
        "When should historical pronunciation uncertainty be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Present known limits instead of confident reconstructed audio",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Present known limits instead of confident reconstructed audio. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-archive-name-uncertainty",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Present known limits instead of confident reconstructed audio versus Store competing readings and confidence with source images; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-pronunciation-revisions",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Present known limits instead of confident reconstructed audio versus Record changed readings and downstream audio assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-pronunciation-provenance",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Present known limits instead of confident reconstructed audio versus Attach approved audio or reading evidence to each entry; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Present known limits instead of confident reconstructed audio",
        "outline": [
          "Explain the specific decision: Present known limits instead of confident reconstructed audio",
          "Define the applicable contract and limits for Historical pronunciation uncertainty",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Present known limits instead of confident reconstructed audio; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Present known limits instead of confident reconstructed audio",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:861",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-source-contradiction",
      "slug": "historical-name-source-contradiction",
      "name": "Historical name source contradiction",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-source-contradiction/",
        "ja": "/ja/tools/historical-name-source-contradiction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Compare conflicting references without silently selecting one",
      "task": "Compare conflicting references without silently selecting one",
      "searchIntent": {
        "primary": "Complete the task: Compare conflicting references without silently selecting one",
        "queryHypothesis": "historical name source contradiction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare conflicting references without silently selecting one?",
        "When should historical name source contradiction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare conflicting references without silently selecting one",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare conflicting references without silently selecting one. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-bibliography-export",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare conflicting references without silently selecting one versus Produce source linked references for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-records-mismatch",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare conflicting references without silently selecting one versus Explain alternate spellings without silently merging characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-import-validation",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare conflicting references without silently selecting one versus Reject malformed datasets without silently dropping characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare conflicting references without silently selecting one",
        "outline": [
          "Explain the specific decision: Compare conflicting references without silently selecting one",
          "Define the applicable contract and limits for Historical name source contradiction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare conflicting references without silently selecting one; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare conflicting references without silently selecting one",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:862",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-specialist-handoff",
      "slug": "historical-name-specialist-handoff",
      "name": "Historical name specialist handoff",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-specialist-handoff/",
        "ja": "/ja/tools/historical-name-specialist-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Package exact questions and candidate evidence for review",
      "task": "Package exact questions and candidate evidence for review",
      "searchIntent": {
        "primary": "Complete the task: Package exact questions and candidate evidence for review",
        "queryHypothesis": "historical name specialist handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package exact questions and candidate evidence for review?",
        "When should historical name specialist handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package exact questions and candidate evidence for review",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package exact questions and candidate evidence for review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-historical-name-note",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Package exact questions and candidate evidence for review versus Attach evidence gaps to exact occurrences for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.2,
          "sharedProfile": true,
          "difference": "Package exact questions and candidate evidence for review versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-review-handoff",
          "score": 0.2,
          "sharedProfile": false,
          "difference": "Package exact questions and candidate evidence for review versus Package unresolved choices and evidence for a human translator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package exact questions and candidate evidence for review",
        "outline": [
          "Explain the specific decision: Package exact questions and candidate evidence for review",
          "Define the applicable contract and limits for Historical name specialist handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package exact questions and candidate evidence for review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package exact questions and candidate evidence for review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:863",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-fact-annotation",
      "slug": "historical-name-fact-annotation",
      "name": "Historical name fact annotation",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-fact-annotation/",
        "ja": "/ja/tools/historical-name-fact-annotation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Label attestation, inference and invention at claim level",
      "task": "Label attestation, inference and invention at claim level",
      "searchIntent": {
        "primary": "Complete the task: Label attestation, inference and invention at claim level",
        "queryHypothesis": "historical name fact annotation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to label attestation, inference and invention at claim level?",
        "When should historical name fact annotation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Label attestation, inference and invention at claim level",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Label attestation, inference and invention at claim level. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-parish-record-naming",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Label attestation, inference and invention at claim level versus Distinguish transcription uncertainty from source attestation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-story-annotation",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Label attestation, inference and invention at claim level versus Label each naming choice and its observable consequence in a supplied passage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-evidence-completeness",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Label attestation, inference and invention at claim level versus Report missing claim level evidence without inventing sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Label attestation, inference and invention at claim level",
        "outline": [
          "Explain the specific decision: Label attestation, inference and invention at claim level",
          "Define the applicable contract and limits for Historical name fact annotation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Label attestation, inference and invention at claim level; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Label attestation, inference and invention at claim level",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:864",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-cast-evidence-coverage",
      "slug": "historical-cast-evidence-coverage",
      "name": "Historical cast evidence coverage",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-cast-evidence-coverage/",
        "ja": "/ja/tools/historical-cast-evidence-coverage/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Identify characters with no period appropriate support",
      "task": "Identify characters with no period appropriate support",
      "searchIntent": {
        "primary": "Complete the task: Identify characters with no period appropriate support",
        "queryHypothesis": "historical cast evidence coverage",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify characters with no period appropriate support?",
        "When should historical cast evidence coverage be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify characters with no period appropriate support",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify characters with no period appropriate support. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.2122222222222222,
          "sharedProfile": true,
          "difference": "Identify characters with no period appropriate support versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-adoption-name-research",
          "score": 0.20277777777777775,
          "sharedProfile": true,
          "difference": "Identify characters with no period appropriate support versus Identify jurisdiction and period questions for specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-pseudonym-evidence",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Identify characters with no period appropriate support versus Distinguish documented pseudonyms from author invented analogues; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify characters with no period appropriate support",
        "outline": [
          "Explain the specific decision: Identify characters with no period appropriate support",
          "Define the applicable contract and limits for Historical cast evidence coverage",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify characters with no period appropriate support; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify characters with no period appropriate support",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:865",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-story-naming-exception",
      "slug": "historical-story-naming-exception",
      "name": "Historical story naming exception",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-story-naming-exception/",
        "ja": "/ja/tools/historical-story-naming-exception/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Explain an intentional departure in an editorial note",
      "task": "Explain an intentional departure in an editorial note",
      "searchIntent": {
        "primary": "Complete the task: Explain an intentional departure in an editorial note",
        "queryHypothesis": "historical story naming exception",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain an intentional departure in an editorial note?",
        "When should historical story naming exception be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain an intentional departure in an editorial note",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain an intentional departure in an editorial note. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-frequency-caveat",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Explain an intentional departure in an editorial note versus Explain archive bias and missing populations in supplied data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-spelling-ledger",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Explain an intentional departure in an editorial note versus Preserve source spelling, normalized form and editorial decision; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-duplicate-exception",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Explain an intentional departure in an editorial note versus Permit an intentional duplicate with a stated story reason; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain an intentional departure in an editorial note",
        "outline": [
          "Explain the specific decision: Explain an intentional departure in an editorial note",
          "Define the applicable contract and limits for Historical story naming exception",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain an intentional departure in an editorial note; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain an intentional departure in an editorial note",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:866",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-historical-name-bibliography-export",
      "slug": "historical-name-bibliography-export",
      "name": "Historical name bibliography export",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-name-bibliography-export/",
        "ja": "/ja/tools/historical-name-bibliography-export/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Produce source linked references for an editor",
      "task": "Produce source linked references for an editor",
      "searchIntent": {
        "primary": "Complete the task: Produce source linked references for an editor",
        "queryHypothesis": "historical name bibliography export",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce source linked references for an editor?",
        "When should historical name bibliography export be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce source linked references for an editor",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce source linked references for an editor. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-parish-record-naming",
          "score": 0.1597222222222222,
          "sharedProfile": true,
          "difference": "Produce source linked references for an editor versus Distinguish transcription uncertainty from source attestation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-tabletop-name-index-cards",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Produce source linked references for an editor versus Produce short physical references with role and pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-archive-name-uncertainty",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Produce source linked references for an editor versus Store competing readings and confidence with source images; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce source linked references for an editor",
        "outline": [
          "Explain the specific decision: Produce source linked references for an editor",
          "Define the applicable contract and limits for Historical name bibliography export",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce source linked references for an editor; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce source linked references for an editor",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:867",
      "profileSource": "data/profiles.json#historical-research"
    },
    {
      "id": "nw-manuscript-character-name-inventory",
      "slug": "manuscript-character-name-inventory",
      "name": "Manuscript character name inventory",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-character-name-inventory/",
        "ja": "/ja/tools/manuscript-character-name-inventory/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Extract author confirmed names without assuming every capitalized word is a person",
      "task": "Extract author confirmed names without assuming every capitalized word is a person",
      "searchIntent": {
        "primary": "Complete the task: Extract author confirmed names without assuming every capitalized word is a person",
        "queryHypothesis": "manuscript character name inventory",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to extract author confirmed names without assuming every capitalized word is a person?",
        "When should manuscript character name inventory be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Extract author confirmed names without assuming every capitalized word is a person",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Extract author confirmed names without assuming every capitalized word is a person. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.13392857142857142,
          "sharedProfile": false,
          "difference": "Extract author confirmed names without assuming every capitalized word is a person versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-pronoun-confusion",
          "score": 0.128125,
          "sharedProfile": true,
          "difference": "Extract author confirmed names without assuming every capitalized word is a person versus Surface passages for review without claiming automated interpretation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Extract author confirmed names without assuming every capitalized word is a person versus Supply author approved pronunciations without invented etymology; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Extract author confirmed names without assuming every capitalized word is a person",
        "outline": [
          "Explain the specific decision: Extract author confirmed names without assuming every capitalized word is a person",
          "Define the applicable contract and limits for Manuscript character name inventory",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Extract author confirmed names without assuming every capitalized word is a person; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Extract author confirmed names without assuming every capitalized word is a person",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:870",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-name-variant-audit",
      "slug": "manuscript-name-variant-audit",
      "name": "Manuscript name variant audit",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-variant-audit/",
        "ja": "/ja/tools/manuscript-name-variant-audit/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Find spelling variants for human identity confirmation",
      "task": "Find spelling variants for human identity confirmation",
      "searchIntent": {
        "primary": "Complete the task: Find spelling variants for human identity confirmation",
        "queryHypothesis": "manuscript name variant audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find spelling variants for human identity confirmation?",
        "When should manuscript name variant audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find spelling variants for human identity confirmation",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find spelling variants for human identity confirmation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Find spelling variants for human identity confirmation versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-continuity-contradiction-scan",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Find spelling variants for human identity confirmation versus Find incompatible forms in dated identity appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-save-format",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Find spelling variants for human identity confirmation versus Serialize identity, display variants and generation provenance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find spelling variants for human identity confirmation",
        "outline": [
          "Explain the specific decision: Find spelling variants for human identity confirmation",
          "Define the applicable contract and limits for Manuscript name variant audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find spelling variants for human identity confirmation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find spelling variants for human identity confirmation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:871",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-rename-impact-map",
      "slug": "manuscript-rename-impact-map",
      "name": "Manuscript rename impact map",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-rename-impact-map/",
        "ja": "/ja/tools/manuscript-rename-impact-map/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "List scenes, props and clues dependent on a proposed rename",
      "task": "List scenes, props and clues dependent on a proposed rename",
      "searchIntent": {
        "primary": "Complete the task: List scenes, props and clues dependent on a proposed rename",
        "queryHypothesis": "manuscript rename impact map",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to list scenes, props and clues dependent on a proposed rename?",
        "When should manuscript rename impact map be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: List scenes, props and clues dependent on a proposed rename",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: List scenes, props and clues dependent on a proposed rename. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.25333333333333335,
          "sharedProfile": false,
          "difference": "List scenes, props and clues dependent on a proposed rename versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-revision-history",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "List scenes, props and clues dependent on a proposed rename versus Track why a name changed and dependent scenes to revisit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-dialogue-tag-rename",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "List scenes, props and clues dependent on a proposed rename versus Distinguish script labels from spoken name text; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "List scenes, props and clues dependent on a proposed rename",
        "outline": [
          "Explain the specific decision: List scenes, props and clues dependent on a proposed rename",
          "Define the applicable contract and limits for Manuscript rename impact map",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for List scenes, props and clues dependent on a proposed rename; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: List scenes, props and clues dependent on a proposed rename",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:872",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-alias-continuity",
      "slug": "manuscript-alias-continuity",
      "name": "Manuscript alias continuity",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-alias-continuity/",
        "ja": "/ja/tools/manuscript-alias-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Check a dated reference ledger against scene identity states",
      "task": "Check a dated reference ledger against scene identity states",
      "searchIntent": {
        "primary": "Complete the task: Check a dated reference ledger against scene identity states",
        "queryHypothesis": "manuscript alias continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check a dated reference ledger against scene identity states?",
        "When should manuscript alias continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check a dated reference ledger against scene identity states",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check a dated reference ledger against scene identity states. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-alias-continuity-contradiction-scan",
          "score": 0.24833333333333332,
          "sharedProfile": false,
          "difference": "Check a dated reference ledger against scene identity states versus Find incompatible forms in dated identity appearances; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-family-continuity",
          "score": 0.16999999999999998,
          "sharedProfile": true,
          "difference": "Check a dated reference ledger against scene identity states versus Check new relatives against established family naming rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-fictional-genealogy-clue",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Check a dated reference ledger against scene identity states versus Check name evidence against a relationship graph and dated records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check a dated reference ledger against scene identity states",
        "outline": [
          "Explain the specific decision: Check a dated reference ledger against scene identity states",
          "Define the applicable contract and limits for Manuscript alias continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check a dated reference ledger against scene identity states; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check a dated reference ledger against scene identity states",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:873",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-address-consistency",
      "slug": "manuscript-address-consistency",
      "name": "Manuscript address consistency",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-address-consistency/",
        "ja": "/ja/tools/manuscript-address-consistency/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare speaker listener usage with approved relationship rules",
      "task": "Compare speaker listener usage with approved relationship rules",
      "searchIntent": {
        "primary": "Complete the task: Compare speaker listener usage with approved relationship rules",
        "queryHypothesis": "manuscript address consistency",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare speaker listener usage with approved relationship rules?",
        "When should manuscript address consistency be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare speaker listener usage with approved relationship rules",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare speaker listener usage with approved relationship rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-surname-address-map",
          "score": 0.38333333333333336,
          "sharedProfile": false,
          "difference": "Compare speaker listener usage with approved relationship rules versus Track surname usage by relationship and speaker; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Compare speaker listener usage with approved relationship rules versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-relationship-graph",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Compare speaker listener usage with approved relationship rules versus Generate permitted address forms for each speaker listener pair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare speaker listener usage with approved relationship rules",
        "outline": [
          "Explain the specific decision: Compare speaker listener usage with approved relationship rules",
          "Define the applicable contract and limits for Manuscript address consistency",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare speaker listener usage with approved relationship rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare speaker listener usage with approved relationship rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:874",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-full-name-overuse",
      "slug": "manuscript-full-name-overuse",
      "name": "Manuscript full name overuse",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-full-name-overuse/",
        "ja": "/ja/tools/manuscript-full-name-overuse/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Flag repetitions using configurable editorial context",
      "task": "Flag repetitions using configurable editorial context",
      "searchIntent": {
        "primary": "Complete the task: Flag repetitions using configurable editorial context",
        "queryHypothesis": "manuscript full name overuse",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag repetitions using configurable editorial context?",
        "When should manuscript full name overuse be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag repetitions using configurable editorial context",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag repetitions using configurable editorial context. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-namesake-ambiguity",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Flag repetitions using configurable editorial context versus Identify repeated names whose referents require context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-draft-label-cleanup",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Flag repetitions using configurable editorial context versus Find temporary labels using a project supplied list; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-character-name-inventory",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Flag repetitions using configurable editorial context versus Extract author confirmed names without assuming every capitalized word is a person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag repetitions using configurable editorial context",
        "outline": [
          "Explain the specific decision: Flag repetitions using configurable editorial context",
          "Define the applicable contract and limits for Manuscript full name overuse",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag repetitions using configurable editorial context; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag repetitions using configurable editorial context",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:876",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-name-pronoun-confusion",
      "slug": "manuscript-name-pronoun-confusion",
      "name": "Manuscript name pronoun confusion",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-pronoun-confusion/",
        "ja": "/ja/tools/manuscript-name-pronoun-confusion/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Surface passages for review without claiming automated interpretation",
      "task": "Surface passages for review without claiming automated interpretation",
      "searchIntent": {
        "primary": "Complete the task: Surface passages for review without claiming automated interpretation",
        "queryHypothesis": "manuscript name pronoun confusion",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to surface passages for review without claiming automated interpretation?",
        "When should manuscript name pronoun confusion be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Surface passages for review without claiming automated interpretation",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Surface passages for review without claiming automated interpretation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-character-name-inventory",
          "score": 0.128125,
          "sharedProfile": true,
          "difference": "Surface passages for review without claiming automated interpretation versus Extract author confirmed names without assuming every capitalized word is a person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-historical-name-note",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Surface passages for review without claiming automated interpretation versus Attach evidence gaps to exact occurrences for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-edit-decision-log",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Surface passages for review without claiming automated interpretation versus Preserve reasons, reviewers and affected passages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Surface passages for review without claiming automated interpretation",
        "outline": [
          "Explain the specific decision: Surface passages for review without claiming automated interpretation",
          "Define the applicable contract and limits for Manuscript name pronoun confusion",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Surface passages for review without claiming automated interpretation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Surface passages for review without claiming automated interpretation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:878",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-namesake-ambiguity",
      "slug": "manuscript-namesake-ambiguity",
      "name": "Manuscript namesake ambiguity",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-namesake-ambiguity/",
        "ja": "/ja/tools/manuscript-namesake-ambiguity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Identify repeated names whose referents require context",
      "task": "Identify repeated names whose referents require context",
      "searchIntent": {
        "primary": "Complete the task: Identify repeated names whose referents require context",
        "queryHypothesis": "manuscript namesake ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to identify repeated names whose referents require context?",
        "When should manuscript namesake ambiguity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Identify repeated names whose referents require context",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Identify repeated names whose referents require context. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-namesake-ancestor-chain",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Identify repeated names whose referents require context versus Show repeated names with unambiguous narrative references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-reclaims-intimate-name",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Identify repeated names whose referents require context versus Identify whose use becomes welcome and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-breaks-namesake-cycle",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Identify repeated names whose referents require context versus Show the deliberate rejection of a repeated family pattern; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Identify repeated names whose referents require context",
        "outline": [
          "Explain the specific decision: Identify repeated names whose referents require context",
          "Define the applicable contract and limits for Manuscript namesake ambiguity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Identify repeated names whose referents require context; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Identify repeated names whose referents require context",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:879",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-title-drift",
      "slug": "manuscript-title-drift",
      "name": "Manuscript title drift",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-title-drift/",
        "ja": "/ja/tools/manuscript-title-drift/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare office references against character promotions and succession",
      "task": "Compare office references against character promotions and succession",
      "searchIntent": {
        "primary": "Complete the task: Compare office references against character promotions and succession",
        "queryHypothesis": "manuscript title drift",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare office references against character promotions and succession?",
        "When should manuscript title drift be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare office references against character promotions and succession",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare office references against character promotions and succession. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-title-versus-personal-name",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Compare office references against character promotions and succession versus Choose references when office and individual interests conflict; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Compare office references against character promotions and succession versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-heir-courtesy-title",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Compare office references against character promotions and succession versus Separate an heir's style from the ruler's actual office; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare office references against character promotions and succession",
        "outline": [
          "Explain the specific decision: Compare office references against character promotions and succession",
          "Define the applicable contract and limits for Manuscript title drift",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare office references against character promotions and succession; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare office references against character promotions and succession",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:880",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-historical-name-note",
      "slug": "manuscript-historical-name-note",
      "name": "Manuscript historical name note",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-historical-name-note/",
        "ja": "/ja/tools/manuscript-historical-name-note/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Attach evidence gaps to exact occurrences for review",
      "task": "Attach evidence gaps to exact occurrences for review",
      "searchIntent": {
        "primary": "Complete the task: Attach evidence gaps to exact occurrences for review",
        "queryHypothesis": "manuscript historical name note",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to attach evidence gaps to exact occurrences for review?",
        "When should manuscript historical name note be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Attach evidence gaps to exact occurrences for review",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Attach evidence gaps to exact occurrences for review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-specialist-handoff",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Attach evidence gaps to exact occurrences for review versus Package exact questions and candidate evidence for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Attach evidence gaps to exact occurrences for review versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-court-name-forms",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Attach evidence gaps to exact occurrences for review versus Record local conventions with explicit evidence limitations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Attach evidence gaps to exact occurrences for review",
        "outline": [
          "Explain the specific decision: Attach evidence gaps to exact occurrences for review",
          "Define the applicable contract and limits for Manuscript historical name note",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Attach evidence gaps to exact occurrences for review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Attach evidence gaps to exact occurrences for review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:881",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-character-registry",
      "slug": "series-character-registry",
      "name": "Series character registry",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-character-registry/",
        "ja": "/ja/tools/series-character-registry/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Preserve stable IDs across books and local display variants",
      "task": "Preserve stable IDs across books and local display variants",
      "searchIntent": {
        "primary": "Complete the task: Preserve stable IDs across books and local display variants",
        "queryHypothesis": "series character registry",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve stable IDs across books and local display variants?",
        "When should series character registry be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve stable IDs across books and local display variants",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve stable IDs across books and local display variants. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-npc-name-registry",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Preserve stable IDs across books and local display variants versus Assign stable identity keys and separate display names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-localization-name-map",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Preserve stable IDs across books and local display variants versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Preserve stable IDs across books and local display variants versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve stable IDs across books and local display variants",
        "outline": [
          "Explain the specific decision: Preserve stable IDs across books and local display variants",
          "Define the applicable contract and limits for Series character registry",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve stable IDs across books and local display variants; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve stable IDs across books and local display variants",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:882",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-retired-name-blacklist",
      "slug": "series-retired-name-blacklist",
      "name": "Series retired name blacklist",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-retired-name-blacklist/",
        "ja": "/ja/tools/series-retired-name-blacklist/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Prevent accidental reuse with a reason and permitted exceptions",
      "task": "Prevent accidental reuse with a reason and permitted exceptions",
      "searchIntent": {
        "primary": "Complete the task: Prevent accidental reuse with a reason and permitted exceptions",
        "queryHypothesis": "series retired name blacklist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent accidental reuse with a reason and permitted exceptions?",
        "When should series retired name blacklist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent accidental reuse with a reason and permitted exceptions",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent accidental reuse with a reason and permitted exceptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-series-guest-character-names",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Prevent accidental reuse with a reason and permitted exceptions versus Prevent conflict with archived recurring characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anthology-recurring-cast-names",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Prevent accidental reuse with a reason and permitted exceptions versus Detect accidental reuse across otherwise independent stories; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Prevent accidental reuse with a reason and permitted exceptions versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent accidental reuse with a reason and permitted exceptions",
        "outline": [
          "Explain the specific decision: Prevent accidental reuse with a reason and permitted exceptions",
          "Define the applicable contract and limits for Series retired name blacklist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent accidental reuse with a reason and permitted exceptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent accidental reuse with a reason and permitted exceptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:883",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-new-cast-collision",
      "slug": "series-new-cast-collision",
      "name": "Series new cast collision",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-new-cast-collision/",
        "ja": "/ja/tools/series-new-cast-collision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare a proposed cast against previous installments",
      "task": "Compare a proposed cast against previous installments",
      "searchIntent": {
        "primary": "Complete the task: Compare a proposed cast against previous installments",
        "queryHypothesis": "series new cast collision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare a proposed cast against previous installments?",
        "When should series new cast collision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare a proposed cast against previous installments",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare a proposed cast against previous installments. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.13125,
          "sharedProfile": false,
          "difference": "Compare a proposed cast against previous installments versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-list-spoiler-test",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare a proposed cast against previous installments versus Compare cast list entries against mystery disclosure timing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-expansion-pack-collisions",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare a proposed cast against previous installments versus Compare a new cast against base game identity records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare a proposed cast against previous installments",
        "outline": [
          "Explain the specific decision: Compare a proposed cast against previous installments",
          "Define the applicable contract and limits for Series new cast collision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare a proposed cast against previous installments; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare a proposed cast against previous installments",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:884",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-timeline-name-changes",
      "slug": "series-timeline-name-changes",
      "name": "Series timeline name changes",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-timeline-name-changes/",
        "ja": "/ja/tools/series-timeline-name-changes/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Resolve the correct reference at each book date",
      "task": "Resolve the correct reference at each book date",
      "searchIntent": {
        "primary": "Complete the task: Resolve the correct reference at each book date",
        "queryHypothesis": "series timeline name changes",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve the correct reference at each book date?",
        "When should series timeline name changes be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve the correct reference at each book date",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve the correct reference at each book date. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-aging-name-timeline",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Resolve the correct reference at each book date versus Transition child, adult and later references by world date; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-adopted-character-name-timeline",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Resolve the correct reference at each book date versus Track birth, placement and chosen names by story event; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Resolve the correct reference at each book date versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve the correct reference at each book date",
        "outline": [
          "Explain the specific decision: Resolve the correct reference at each book date",
          "Define the applicable contract and limits for Series timeline name changes",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve the correct reference at each book date; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve the correct reference at each book date",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:885",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-alias-spoiler-boundary",
      "slug": "series-alias-spoiler-boundary",
      "name": "Series alias spoiler boundary",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-alias-spoiler-boundary/",
        "ja": "/ja/tools/series-alias-spoiler-boundary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Export reader facing names by installment",
      "task": "Export reader facing names by installment",
      "searchIntent": {
        "primary": "Complete the task: Export reader facing names by installment",
        "queryHypothesis": "series alias spoiler boundary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export reader facing names by installment?",
        "When should series alias spoiler boundary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export reader facing names by installment",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export reader facing names by installment. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-localized-spoiler-safe-glossary",
          "score": 0.18,
          "sharedProfile": false,
          "difference": "Export reader facing names by installment versus Export entries only after the reader reaches the relevant reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Export reader facing names by installment versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.1222222222222222,
          "sharedProfile": false,
          "difference": "Export reader facing names by installment versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export reader facing names by installment",
        "outline": [
          "Explain the specific decision: Export reader facing names by installment",
          "Define the applicable contract and limits for Series alias spoiler boundary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export reader facing names by installment; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export reader facing names by installment",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:886",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-family-continuity",
      "slug": "series-family-continuity",
      "name": "Series family continuity",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-family-continuity/",
        "ja": "/ja/tools/series-family-continuity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Check new relatives against established family naming rules",
      "task": "Check new relatives against established family naming rules",
      "searchIntent": {
        "primary": "Complete the task: Check new relatives against established family naming rules",
        "queryHypothesis": "series family continuity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check new relatives against established family naming rules?",
        "When should series family continuity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check new relatives against established family naming rules",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check new relatives against established family naming rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-diaspora-family-continuity",
          "score": 0.24,
          "sharedProfile": false,
          "difference": "Check new relatives against established family naming rules versus Track names across generations with explicit family decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Check new relatives against established family naming rules versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-adoption-reveal-audit",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Check new relatives against established family naming rules versus Check earlier name references against the planned reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check new relatives against established family naming rules",
        "outline": [
          "Explain the specific decision: Check new relatives against established family naming rules",
          "Define the applicable contract and limits for Series family continuity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check new relatives against established family naming rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check new relatives against established family naming rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:887",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-pronunciation-revisions",
      "slug": "series-pronunciation-revisions",
      "name": "Series pronunciation revisions",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-pronunciation-revisions/",
        "ja": "/ja/tools/series-pronunciation-revisions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Record changed readings and downstream audio assets",
      "task": "Record changed readings and downstream audio assets",
      "searchIntent": {
        "primary": "Complete the task: Record changed readings and downstream audio assets",
        "queryHypothesis": "series pronunciation revisions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record changed readings and downstream audio assets?",
        "When should series pronunciation revisions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record changed readings and downstream audio assets",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record changed readings and downstream audio assets. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-npc-pronunciation-metadata",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Record changed readings and downstream audio assets versus Export approved pronunciations with dialogue assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-pronunciation-expectation-test",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Record changed readings and downstream audio assets versus Collect readings before exposing the approved pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-pronunciation-provenance",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Record changed readings and downstream audio assets versus Attach approved audio or reading evidence to each entry; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record changed readings and downstream audio assets",
        "outline": [
          "Explain the specific decision: Record changed readings and downstream audio assets",
          "Define the applicable contract and limits for Series pronunciation revisions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record changed readings and downstream audio assets; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record changed readings and downstream audio assets",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:888",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-localization-drift",
      "slug": "series-localization-drift",
      "name": "Series localization drift",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-localization-drift/",
        "ja": "/ja/tools/series-localization-drift/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare approved forms across translated volumes",
      "task": "Compare approved forms across translated volumes",
      "searchIntent": {
        "primary": "Complete the task: Compare approved forms across translated volumes",
        "queryHypothesis": "series localization drift",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare approved forms across translated volumes?",
        "When should series localization drift be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare approved forms across translated volumes",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare approved forms across translated volumes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-localization-name-map",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Compare approved forms across translated volumes versus Maintain stable character IDs across English and Japanese forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-terminology-drift-audit",
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Compare approved forms across translated volumes versus Detect one identity translated inconsistently across episodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-localization-name-bible",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Compare approved forms across translated volumes versus Maintain approved forms for editors and translators; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare approved forms across translated volumes",
        "outline": [
          "Explain the specific decision: Compare approved forms across translated volumes",
          "Define the applicable contract and limits for Series localization drift",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare approved forms across translated volumes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare approved forms across translated volumes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:889",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-serial-episode-name-recap",
      "slug": "serial-episode-name-recap",
      "name": "Serial episode name recap",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/serial-episode-name-recap/",
        "ja": "/ja/tools/serial-episode-name-recap/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Choose reminder forms from publication gap and reader knowledge",
      "task": "Choose reminder forms from publication gap and reader knowledge",
      "searchIntent": {
        "primary": "Complete the task: Choose reminder forms from publication gap and reader knowledge",
        "queryHypothesis": "serial episode name recap",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to choose reminder forms from publication gap and reader knowledge?",
        "When should serial episode name recap be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Choose reminder forms from publication gap and reader knowledge",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Choose reminder forms from publication gap and reader knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-recap-alias-continuity",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Choose reminder forms from publication gap and reader knowledge versus Keep recap wording within current reader knowledge; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Choose reminder forms from publication gap and reader knowledge versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-letter-signatures",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Choose reminder forms from publication gap and reader knowledge versus Map signature forms to sender knowledge and clue fairness; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Choose reminder forms from publication gap and reader knowledge",
        "outline": [
          "Explain the specific decision: Choose reminder forms from publication gap and reader knowledge",
          "Define the applicable contract and limits for Serial episode name recap",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Choose reminder forms from publication gap and reader knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Choose reminder forms from publication gap and reader knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:890",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-serial-reader-correction-log",
      "slug": "serial-reader-correction-log",
      "name": "Serial reader correction log",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/serial-reader-correction-log/",
        "ja": "/ja/tools/serial-reader-correction-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Track reports as claims pending author confirmation",
      "task": "Track reports as claims pending author confirmation",
      "searchIntent": {
        "primary": "Complete the task: Track reports as claims pending author confirmation",
        "queryHypothesis": "serial reader correction log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track reports as claims pending author confirmation?",
        "When should serial reader correction log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track reports as claims pending author confirmation",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track reports as claims pending author confirmation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Track reports as claims pending author confirmation versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-false-genealogy-naming",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Track reports as claims pending author confirmation versus Separate forged lineage claims from author known relations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.11499999999999999,
          "sharedProfile": false,
          "difference": "Track reports as claims pending author confirmation versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track reports as claims pending author confirmation",
        "outline": [
          "Explain the specific decision: Track reports as claims pending author confirmation",
          "Define the applicable contract and limits for Serial reader correction log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track reports as claims pending author confirmation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track reports as claims pending author confirmation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:891",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-global-replace-safety",
      "slug": "manuscript-global-replace-safety",
      "name": "Manuscript global replace safety",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-global-replace-safety/",
        "ja": "/ja/tools/manuscript-global-replace-safety/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Preview exact identity scoped edits before applying any replacement",
      "task": "Preview exact identity scoped edits before applying any replacement",
      "searchIntent": {
        "primary": "Complete the task: Preview exact identity scoped edits before applying any replacement",
        "queryHypothesis": "manuscript global replace safety",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preview exact identity scoped edits before applying any replacement?",
        "When should manuscript global replace safety be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preview exact identity scoped edits before applying any replacement",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preview exact identity scoped edits before applying any replacement. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Preview exact identity scoped edits before applying any replacement versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Preview exact identity scoped edits before applying any replacement versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-historical-name-note",
          "score": 0.10476190476190475,
          "sharedProfile": true,
          "difference": "Preview exact identity scoped edits before applying any replacement versus Attach evidence gaps to exact occurrences for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preview exact identity scoped edits before applying any replacement",
        "outline": [
          "Explain the specific decision: Preview exact identity scoped edits before applying any replacement",
          "Define the applicable contract and limits for Manuscript global replace safety",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preview exact identity scoped edits before applying any replacement; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preview exact identity scoped edits before applying any replacement",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:892",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-partial-name-replacement",
      "slug": "manuscript-partial-name-replacement",
      "name": "Manuscript partial name replacement",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-partial-name-replacement/",
        "ja": "/ja/tools/manuscript-partial-name-replacement/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Avoid changing unrelated words that contain a name",
      "task": "Avoid changing unrelated words that contain a name",
      "searchIntent": {
        "primary": "Complete the task: Avoid changing unrelated words that contain a name",
        "queryHypothesis": "manuscript partial name replacement",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid changing unrelated words that contain a name?",
        "When should manuscript partial name replacement be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid changing unrelated words that contain a name",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid changing unrelated words that contain a name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-replacement",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Avoid changing unrelated words that contain a name versus Replace one established name while preserving story dependencies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-initials-clue",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Avoid changing unrelated words that contain a name versus Repair initials dependent reveals without changing unrelated character facts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-character-name-inventory",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Avoid changing unrelated words that contain a name versus Extract author confirmed names without assuming every capitalized word is a person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid changing unrelated words that contain a name",
        "outline": [
          "Explain the specific decision: Avoid changing unrelated words that contain a name",
          "Define the applicable contract and limits for Manuscript partial name replacement",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid changing unrelated words that contain a name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid changing unrelated words that contain a name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:893",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-dialogue-tag-rename",
      "slug": "manuscript-dialogue-tag-rename",
      "name": "Manuscript dialogue tag rename",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-dialogue-tag-rename/",
        "ja": "/ja/tools/manuscript-dialogue-tag-rename/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Distinguish script labels from spoken name text",
      "task": "Distinguish script labels from spoken name text",
      "searchIntent": {
        "primary": "Complete the task: Distinguish script labels from spoken name text",
        "queryHypothesis": "manuscript dialogue tag rename",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish script labels from spoken name text?",
        "When should manuscript dialogue tag rename be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish script labels from spoken name text",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish script labels from spoken name text. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.24404761904761904,
          "sharedProfile": false,
          "difference": "Distinguish script labels from spoken name text versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-script-cast-synchronization",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish script labels from spoken name text versus Compare script labels with the approved cast bible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-title-versus-name-caption",
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Distinguish script labels from spoken name text versus Distinguish role labels from a character's actual name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish script labels from spoken name text",
        "outline": [
          "Explain the specific decision: Distinguish script labels from spoken name text",
          "Define the applicable contract and limits for Manuscript dialogue tag rename",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish script labels from spoken name text; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish script labels from spoken name text",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:894",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-glossary-synchronization",
      "slug": "manuscript-glossary-synchronization",
      "name": "Manuscript glossary synchronization",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-glossary-synchronization/",
        "ja": "/ja/tools/manuscript-glossary-synchronization/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare entries with the approved character ledger",
      "task": "Compare entries with the approved character ledger",
      "searchIntent": {
        "primary": "Complete the task: Compare entries with the approved character ledger",
        "queryHypothesis": "manuscript glossary synchronization",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare entries with the approved character ledger?",
        "When should manuscript glossary synchronization be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare entries with the approved character ledger",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare entries with the approved character ledger. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-glossary-spoiler-audit",
          "score": 0.15119047619047618,
          "sharedProfile": false,
          "difference": "Compare entries with the approved character ledger versus Compare reader knowledge by chapter against glossary entries; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Compare entries with the approved character ledger versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-spoiler-safe-glossary",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Compare entries with the approved character ledger versus Export entries only after the reader reaches the relevant reveal; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare entries with the approved character ledger",
        "outline": [
          "Explain the specific decision: Compare entries with the approved character ledger",
          "Define the applicable contract and limits for Manuscript glossary synchronization",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare entries with the approved character ledger; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare entries with the approved character ledger",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:895",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-name-style-sheet",
      "slug": "manuscript-name-style-sheet",
      "name": "Manuscript name style sheet",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-style-sheet/",
        "ja": "/ja/tools/manuscript-name-style-sheet/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Export preferred spellings, readings and relationship restrictions",
      "task": "Export preferred spellings, readings and relationship restrictions",
      "searchIntent": {
        "primary": "Complete the task: Export preferred spellings, readings and relationship restrictions",
        "queryHypothesis": "manuscript name style sheet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export preferred spellings, readings and relationship restrictions?",
        "When should manuscript name style sheet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export preferred spellings, readings and relationship restrictions",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export preferred spellings, readings and relationship restrictions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-letterer-handoff-names",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Export preferred spellings, readings and relationship restrictions versus Export approved spellings, pronunciations and forbidden variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-order-style-sheet",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Export preferred spellings, readings and relationship restrictions versus Record context dependent display order rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-address-consistency",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Export preferred spellings, readings and relationship restrictions versus Compare speaker listener usage with approved relationship rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export preferred spellings, readings and relationship restrictions",
        "outline": [
          "Explain the specific decision: Export preferred spellings, readings and relationship restrictions",
          "Define the applicable contract and limits for Manuscript name style sheet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export preferred spellings, readings and relationship restrictions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export preferred spellings, readings and relationship restrictions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:896",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-character-merge-review",
      "slug": "manuscript-character-merge-review",
      "name": "Manuscript character merge review",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-character-merge-review/",
        "ja": "/ja/tools/manuscript-character-merge-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Fiction writers, comic teams and game masters checking whether differently labelled source records refer to the same fictional person.",
      "scenario": "Gate tender Nemi Rook and the masked Reedkeeper are one person, while an arriving instrument repairer has the same full name. A crowd thanks the wrong Nemi, and naive record deduplication would erase the distinction.",
      "task": "Screen supplied naming records for possible identity duplicates, record reasoned same/different relationships, diagnose contradictory paths and choose representatives for a source-preserving mapping plan.",
      "searchIntent": {
        "primary": "Review possible duplicate character records while preserving deliberate same-name people.",
        "queryHypothesis": "duplicate character records name review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Does matching a full name prove two cast records are one person?",
        "How can same-person chains contradict a different-person note?",
        "Why does a source edit invalidate a representative decision?"
      ],
      "inputs": [
        {
          "key": "entries",
          "use": "1–24 records, exactly id/name/aliases/source/note. ID refers to a record, not a certified person. Up to four aliases; source is an authored location label, not a verified citation. Keep the original cast bible."
        },
        {
          "key": "policy",
          "use": "No pronunciation inference, transliteration or Unicode normalization. This changes suggestions, not the author’s confirmed identities."
        },
        {
          "key": "threshold",
          "use": "Multiset Dice overlap of adjacent code-point pairs; maximum over supplied name/alias combinations. Inclusive threshold uses the unrounded fraction. It is a review heuristic, not an identity probability."
        },
        {
          "key": "reviews",
          "use": "Use the pair controls and give a reason. same/different/defer are author declarations. Changed source records make an old review stale; deferred and orphan reviews remain visible."
        },
        {
          "key": "canonical",
          "use": "Choose a representative for every consistent multi-record group. The choice binds its members and confirmed same-person links. No record is deleted or rewritten."
        }
      ],
      "rules": [
        "Validate 1–24 explicit source records and keep IDs separate from fictional person identity; reject missing/extra fields and malformed Unicode.",
        "Screen every bounded pair using the maximum multiset Dice score over supplied names/aliases, with repeated adjacent code-point counts. Disclose fraction, threshold and exact/ASCII-only case policy.",
        "A similar string suggests review only. Same/different/defer require a nonblank authored reason and exact source expectations.",
        "Only current same-person reviews create graph paths. A different relationship inside a component produces a positive-path/negative-review contradiction; never discard an edge automatically.",
        "Different-person relationships are not transitive. Cross-group different coverage requires an explicit negative witness and positive paths on both sides.",
        "Changed source records stale old reviews; missing endpoints remain orphan obligations. Deferred or old reviews never silently clear the plan.",
        "Each consistent multi-record group needs an explicit representative bound to its member records and current positive links. Changed group contexts stale the choice; unmatched old choices remain visible.",
        "Export the complete mapping only after the screened scope and required choices resolve, retaining all source records and disclosed outside-screen limits. No manuscript/database merge or real-person identification occurs."
      ],
      "requiredData": [
        {
          "description": "Original fictional Nemi/tender/repairer records, supplied alias labels and authored scene references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-supplied naming records and relationship declarations, not verified identity documents or external evidence services",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate 1–24 explicit source records and keep IDs separate from fictional person identity; reject missing/extra fields and malformed Unicode.",
        "Screen every bounded pair using the maximum multiset Dice score over supplied names/aliases, with repeated adjacent code-point counts. Disclose fraction, threshold and exact/ASCII-only case policy.",
        "A similar string suggests review only. Same/different/defer require a nonblank authored reason and exact source expectations.",
        "Only current same-person reviews create graph paths. A different relationship inside a component produces a positive-path/negative-review contradiction; never discard an edge automatically.",
        "Different-person relationships are not transitive. Cross-group different coverage requires an explicit negative witness and positive paths on both sides.",
        "Changed source records stale old reviews; missing endpoints remain orphan obligations. Deferred or old reviews never silently clear the plan.",
        "Each consistent multi-record group needs an explicit representative bound to its member records and current positive links. Changed group contexts stale the choice; unmatched old choices remain visible.",
        "Export the complete mapping only after the screened scope and required choices resolve, retaining all source records and disclosed outside-screen limits. No manuscript/database merge or real-person identification occurs."
      ],
      "outputs": [
        "Pairwise lexical forms, exact score fractions and current relationship coverage",
        "Same-person components and inspected positive/negative witness paths",
        "Stale/orphan/deferred review obligations and representative-choice contexts",
        "Private complete audit and source-preserving representative mapping plan"
      ],
      "capabilities": [
        "Expose a contradictory different-person declaration through the exact accepted same-person path and review IDs, without treating different as transitive.",
        "Guard source-bound author reviews and representative choices, preserving homonyms and every original record before permitting a complete mapping handoff."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is to establish proposed correspondence between different source record IDs. Three-way cast reconciliation assumes person IDs already correspond and merges fields; an alias bridge assumes known identities and gates who may use a form. This task instead needs lexical suggestions, reasoned relationship reviews, positive components, negative contradiction witnesses, exact-context validity and representative choices before any mapping is exported.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "series-cast-change-diff",
          "difference": "Cast merge compares base/current/incoming values under an already declared person ID. This review starts with separate source IDs, supports homonyms and alias labels, screens adjacent-code-point overlap, validates same/different constraints and requires an explicit representative mapping without rewriting or consolidating source records."
        }
      },
      "nearestTools": [
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.09954545454545455,
          "sharedProfile": false,
          "difference": "Screen supplied naming records for possible identity duplicates, record reasoned same/different relationships, diagnose contradictory paths and choose representatives for a source-preserving mapping plan. versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-variant-audit",
          "score": 0.09826086956521739,
          "sharedProfile": true,
          "difference": "Screen supplied naming records for possible identity duplicates, record reasoned same/different relationships, diagnose contradictory paths and choose representatives for a source-preserving mapping plan. versus Find spelling variants for human identity confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.096,
          "sharedProfile": true,
          "difference": "Screen supplied naming records for possible identity duplicates, record reasoned same/different relationships, diagnose contradictory paths and choose representatives for a source-preserving mapping plan. versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A repeated label should open a source question, not erase a character; a proposed representative must preserve both identity evidence and every original record.",
        "outline": [
          "Separate repeated names from duplicate identities",
          "An original watergate chorus and two same-name arrivals",
          "Prepare explicit source scopes and aliases",
          "Inspect exact character overlap and cutoff limits",
          "Declare same/different relationships with reasons",
          "Follow contradiction witnesses and nontransitive differences",
          "Choose a representative without deleting records",
          "Invalidate old contexts and preserve source material in the handoff"
        ],
        "story": "During a watergate celebration, children thank arriving repairer Nemi Rook for the tender’s work. The tender is also called the Reedkeeper; a masked reveal connects those records, but the repairer remains a different same-name person. A specific title and action make the chorus address legible without forcing either person to rename.",
        "storyAnalysis": "Renaming the repairer Ilin Voss removes one exact name suggestion and changes the scene’s misunderstanding, but does not prove the masked identity. Combining a homonym with the title would conflate two biographies; choosing a representative is a private record decision, not a public naming rule.",
        "evidence": "Original complete EN/JA watergate chorus guides, explicit name counterfactual, LINK-01–23, LINK-HTML, 34 actual browser cases and four bilingual desktop/mobile keyboard submissions. No verified source truth, real identity or demand claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/identityReview.md",
        "localizedBodies": {
          "en": "content/en/identityReview.md",
          "ja": "content/ja/identityReview.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default example suggests two pairs without joining any records.",
        "Confirm gate/keeper same and gate/passenger different; require an explicit representative, then export the documented mapping with three original records intact.",
        "Adding keeper/passenger same exposes gate → keeper → passenger against the different witness and withholds export.",
        "Source edits stale reviews; positive-basis changes stale a representative; old controls cannot overwrite a changed context.",
        "Both heuristic parameters change actual suggestions; they do not silently rewrite confirmed identities. Full bounded screen computes all 276 pairs for 24 same-label records.",
        "Complete plan, private audit, source-preserving tabletop fixture, actual copy/favorites/compare/project restore and both localized mobile pages require recorded checks."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:897",
      "profileSource": "data/profiles.json#manuscript-audit",
      "specBatch": "batch-11",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Bounded all-pairs screening, count-preserving score traces, constrained relationship closure, contradictory path witnesses, guarded context decisions and original complete bilingual guidance; no fabricated effort estimate."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-campaign-archive-identity-merge",
          "input": "Distinct id/name/aliases/source/note records, screening policy and threshold, reasoned exact-context same/different/defer reviews and explicit representatives.",
          "rule": "No automatic identity merge from names or source labels. Only current author-declared same links form groups; contradictory different links and pending obligations withhold the plan.",
          "output": "Private representative mapping proposal retaining all source records and review context. No deletion, biography consolidation or applied database merge.",
          "acceptance": "Session 03 Archivist Elen and Session 07 Elen Rook remain separate before review. Explicit same review and representative s7 produce an actual downloaded s3→s7, s7→s7 mapping with both original notes preserved.",
          "evidence": [
            "LINK-22",
            "reports/identity-review-browser-qa.json campaign-records-remain-separate-before-review",
            "reports/identity-review-browser-qa.json campaign-record-review-complete-source-preserving-plan"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "identityReview",
        "engineFiles": [
          "web/identity-review.mjs",
          "web/identity-review-tool.mjs",
          "web/identity-review-view.mjs",
          "web/identity-review-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/identity-review.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "entries",
          "label": [
            "Distinct source records · JSON",
            "区別して持つ元の記録・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"gate\",\n    \"name\": \"Nemi Rook\",\n    \"aliases\": [\n      \"Nemi\"\n    ],\n    \"source\": \"Scene 02 · west floodgate\",\n    \"note\": \"The gate tender stays on the west bank.\"\n  },\n  {\n    \"id\": \"keeper\",\n    \"name\": \"The Reedkeeper\",\n    \"aliases\": [\n      \"Nemi\"\n    ],\n    \"source\": \"Scene 04 · market dialogue\",\n    \"note\": \"Authored reveal: the gate tender removes the keeper mask.\"\n  },\n  {\n    \"id\": \"passenger\",\n    \"name\": \"Nemi Rook\",\n    \"aliases\": [],\n    \"source\": \"Scene 05 · ferry arrival\",\n    \"note\": \"A different instrument repairer with the same name meets the gate tender at the dock.\"\n  }\n]",
          "help": [
            "1–24 records, exactly id/name/aliases/source/note. ID refers to a record, not a certified person. Up to four aliases; source is an authored location label, not a verified citation. Keep the original cast bible.",
            "1〜24件でid/name/aliases/source/noteだけを指定。IDは記録を指し、人物を認証しません。別名は4件まで。sourceは作者の参照ラベルで、出典の検証ではありません。元の設定表を残します。"
          ],
          "maxLength": 750000
        },
        {
          "key": "policy",
          "label": [
            "Character comparison policy",
            "文字の比較規則"
          ],
          "type": "select",
          "default": "exact",
          "help": [
            "No pronunciation inference, transliteration or Unicode normalization. This changes suggestions, not the author’s confirmed identities.",
            "発音推測、翻字、Unicode正規化はしません。変わるのは候補で、作者が確認した人物の指定ではありません。"
          ],
          "options": [
            [
              "exact",
              [
                "Exact code points, including spaces",
                "空白も含めコードポイントをそのまま比較"
              ]
            ],
            [
              "ascii-fold",
              [
                "ASCII A–Z → a–z only",
                "ASCIIのA〜Zだけa〜zへ"
              ]
            ]
          ]
        },
        {
          "key": "threshold",
          "label": [
            "Suggestion threshold · 0–100",
            "候補のしきい値・0〜100"
          ],
          "type": "number",
          "default": 80,
          "help": [
            "Multiset Dice overlap of adjacent code-point pairs; maximum over supplied name/alias combinations. Inclusive threshold uses the unrounded fraction. It is a review heuristic, not an identity probability.",
            "隣接する二コードポイントの重複数を使うDiceの目安です。名前と別名の組の最大値を使用。丸める前の分数がしきい値以上なら候補にします。同一人物の確率ではありません。"
          ]
        },
        {
          "key": "reviews",
          "label": [
            "Exact-context author reviews · JSON",
            "元記録の文脈に結び付く作者の判断・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Use the pair controls and give a reason. same/different/defer are author declarations. Changed source records make an old review stale; deferred and orphan reviews remain visible.",
            "組の操作欄で理由を添えて指定します。same／different／deferは作者の宣言。元記録を変えると古い判断は失効し、保留や適用先のない判断も表示します。"
          ],
          "maxLength": 750000
        },
        {
          "key": "canonical",
          "label": [
            "Representative choices · JSON",
            "代表記録の選択・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Choose a representative for every consistent multi-record group. The choice binds its members and confirmed same-person links. No record is deleted or rewritten.",
            "矛盾のない複数記録の組ごとに代表を選びます。判断は構成記録と同一人物の指定に結び付きます。記録を消したり書き換えたりしません。"
          ],
          "maxLength": 750000
        }
      ]
    },
    {
      "id": "nw-manuscript-character-split-revision",
      "slug": "manuscript-character-split-revision",
      "name": "Manuscript character split revision",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-character-split-revision/",
        "ja": "/ja/tools/manuscript-character-split-revision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Separate a combined draft role into distinct named characters",
      "task": "Separate a combined draft role into distinct named characters",
      "searchIntent": {
        "primary": "Complete the task: Separate a combined draft role into distinct named characters",
        "queryHypothesis": "manuscript character split revision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate a combined draft role into distinct named characters?",
        "When should manuscript character split revision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate a combined draft role into distinct named characters",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate a combined draft role into distinct named characters. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-name-editorial-signoff",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Separate a combined draft role into distinct named characters versus Require a named reviewer and unresolved issue disposition; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-naming-brief",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Separate a combined draft role into distinct named characters versus Convert a role, setting and narrative distance into a testable name brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-revision-history",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Separate a combined draft role into distinct named characters versus Track why a name changed and dependent scenes to revisit; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate a combined draft role into distinct named characters",
        "outline": [
          "Explain the specific decision: Separate a combined draft role into distinct named characters",
          "Define the applicable contract and limits for Manuscript character split revision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate a combined draft role into distinct named characters; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate a combined draft role into distinct named characters",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:898",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-sensitivity-query-list",
      "slug": "manuscript-sensitivity-query-list",
      "name": "Manuscript sensitivity query list",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-sensitivity-query-list/",
        "ja": "/ja/tools/manuscript-sensitivity-query-list/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Collect specific cultural uncertainties for a qualified reader",
      "task": "Collect specific cultural uncertainties for a qualified reader",
      "searchIntent": {
        "primary": "Complete the task: Collect specific cultural uncertainties for a qualified reader",
        "queryHypothesis": "manuscript sensitivity query list",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect specific cultural uncertainties for a qualified reader?",
        "When should manuscript sensitivity query list be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect specific cultural uncertainties for a qualified reader",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect specific cultural uncertainties for a qualified reader. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-test-cultural-review-questions",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Collect specific cultural uncertainties for a qualified reader versus Prepare context specific questions for a qualified reviewer; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Collect specific cultural uncertainties for a qualified reader versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Collect specific cultural uncertainties for a qualified reader versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect specific cultural uncertainties for a qualified reader",
        "outline": [
          "Explain the specific decision: Collect specific cultural uncertainties for a qualified reader",
          "Define the applicable contract and limits for Manuscript sensitivity query list",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect specific cultural uncertainties for a qualified reader; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect specific cultural uncertainties for a qualified reader",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:899",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-name-edit-decision-log",
      "slug": "manuscript-name-edit-decision-log",
      "name": "Manuscript name edit decision log",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-edit-decision-log/",
        "ja": "/ja/tools/manuscript-name-edit-decision-log/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Preserve reasons, reviewers and affected passages",
      "task": "Preserve reasons, reviewers and affected passages",
      "searchIntent": {
        "primary": "Complete the task: Preserve reasons, reviewers and affected passages",
        "queryHypothesis": "manuscript name edit decision log",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve reasons, reviewers and affected passages?",
        "When should manuscript name edit decision log be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve reasons, reviewers and affected passages",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve reasons, reviewers and affected passages. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-decision-record",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Preserve reasons, reviewers and affected passages versus Save chosen names with reasons and rejected alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-voice-cast-retake-name-log",
          "score": 0.14285714285714285,
          "sharedProfile": false,
          "difference": "Preserve reasons, reviewers and affected passages versus Track pronunciation corrections and affected timecodes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-transliteration-decision-log",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Preserve reasons, reviewers and affected passages versus Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve reasons, reviewers and affected passages",
        "outline": [
          "Explain the specific decision: Preserve reasons, reviewers and affected passages",
          "Define the applicable contract and limits for Manuscript name edit decision log",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve reasons, reviewers and affected passages; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve reasons, reviewers and affected passages",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:900",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-contributor-name-handoff",
      "slug": "series-contributor-name-handoff",
      "name": "Series contributor name handoff",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-contributor-name-handoff/",
        "ja": "/ja/tools/series-contributor-name-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Package approved forms and forbidden variants for guest writers",
      "task": "Package approved forms and forbidden variants for guest writers",
      "searchIntent": {
        "primary": "Complete the task: Package approved forms and forbidden variants for guest writers",
        "queryHypothesis": "series contributor name handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package approved forms and forbidden variants for guest writers?",
        "When should series contributor name handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package approved forms and forbidden variants for guest writers",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package approved forms and forbidden variants for guest writers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-comic-letterer-handoff-names",
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Package approved forms and forbidden variants for guest writers versus Export approved spellings, pronunciations and forbidden variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-localization-drift",
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Package approved forms and forbidden variants for guest writers versus Compare approved forms across translated volumes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-character-registry",
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Package approved forms and forbidden variants for guest writers versus Preserve stable IDs across books and local display variants; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package approved forms and forbidden variants for guest writers",
        "outline": [
          "Explain the specific decision: Package approved forms and forbidden variants for guest writers",
          "Define the applicable contract and limits for Series contributor name handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package approved forms and forbidden variants for guest writers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package approved forms and forbidden variants for guest writers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:901",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-world-rule-regression",
      "slug": "series-world-rule-regression",
      "name": "Series world rule regression",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-world-rule-regression/",
        "ja": "/ja/tools/series-world-rule-regression/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Compare newly added names against the current fictional grammar",
      "task": "Compare newly added names against the current fictional grammar",
      "searchIntent": {
        "primary": "Complete the task: Compare newly added names against the current fictional grammar",
        "queryHypothesis": "series world rule regression",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare newly added names against the current fictional grammar?",
        "When should series world rule regression be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare newly added names against the current fictional grammar",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare newly added names against the current fictional grammar. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare newly added names against the current fictional grammar versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-naming-system-reader-load",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare newly added names against the current fictional grammar versus Test grammar complexity against reader recall exercises; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-rule-migration",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Compare newly added names against the current fictional grammar versus Compare outcomes before adopting a new shared naming grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare newly added names against the current fictional grammar",
        "outline": [
          "Explain the specific decision: Compare newly added names against the current fictional grammar",
          "Define the applicable contract and limits for Series world rule regression",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare newly added names against the current fictional grammar; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare newly added names against the current fictional grammar",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:902",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-quoted-document-names",
      "slug": "manuscript-quoted-document-names",
      "name": "Manuscript quoted document names",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-quoted-document-names/",
        "ja": "/ja/tools/manuscript-quoted-document-names/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Authors tracking names visible in fictional letters, quoted documents, sealed enclosures and physical copies.",
      "scenario": "A sealed invitation has a public exterior form and private dedication. Copying one inner face sends its name elsewhere; closing the original cannot undo the exposure.",
      "task": "Replay physical custody, nested visibility and copy lineage, then audit first authored name exposure against reveal windows at a selected timeline cutoff.",
      "searchIntent": {
        "primary": "Audit a story’s name revelations through physical letters, enclosures and copies.",
        "queryHypothesis": "novel letter reveal continuity name hidden document",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Does receiving a sealed letter reveal its dedication?",
        "Can closing an envelope erase a prior exposure?",
        "Does a copied name expose its recipient before they read?"
      ],
      "inputs": [
        {
          "key": "actors",
          "type": "textarea",
          "purpose": "1–30 unique {id,label} objects. Actor IDs identify custodians and observers, not inferred identity owners."
        },
        {
          "key": "props",
          "type": "textarea",
          "purpose": "1–40 exact {id,label,kind,parent,form,identity,sealed,holder}. kind=container/text. Only roots have actor holders; children use null. Parent must be a container. Blank container form requires identity=null. Text needs a name and cannot be sealed. Every form→identity association is your fictional declaration."
        },
        {
          "key": "events",
          "type": "textarea",
          "purpose": "≤120 unique events; integer at 0–1,000,000, nondecreasing. Every event: id/at/actor/action/target. transfer/show add to; copy adds to/copyId; open/close/read add nothing. No extra fields. Equal times use supplied order. Failed actions do not mutate state."
        },
        {
          "key": "windows",
          "type": "textarea",
          "purpose": "≤60 unique {observer,identity,earliest,latest}. Existing actors and initial identity IDs; integer 0–1,000,000. First exposure to any declared form counts. Pending is distinct from a missed deadline."
        },
        {
          "key": "through",
          "type": "number",
          "purpose": "Select the finite replay cutoff without applying later events."
        },
        {
          "key": "context",
          "type": "textarea",
          "purpose": "≤1000 units, retained in private copies and audit. The model tracks authored exposure, not comprehension, memory or whether a clue is fair."
        }
      ],
      "rules": [
        "1–30 actors, 1–40 initial physical surfaces and ≤120 chronological actions. Exact schema, unique IDs, existing container parents, root-only actor custody and acyclic containment. Text surfaces are named/unsealed; containers can have blank exterior form with identity null.",
        "Access requires the actor to hold the containing root and all ancestors of the target to be open. A sealed target hides its descendants, not its own exterior form. No automatic reading on transfer or opening; closure never erases exposure.",
        "Read exposes actor; show exposes only the explicit recipient without transfer. Copy exposes the copying actor to one selected visible face and creates a new unsealed text root for recipient, preserving literal form, authored identity and copy lineage. Receiving a copy is not reading it.",
        "Transfer applies only to roots and carries descendants. Rejected actions have no effect; subsequent steps use retained state. Duplicate copy IDs cannot overwrite or leave a partial exposure. Equal times replay in input order.",
        "Replay cutoff queues later actions with no effect. Unique observer/identity windows compare first exposure to any authored form: early/within/late, pending before deadline, not-observed once due. This is exposure, not inferred comprehension, memory or identity recognition.",
        "All copy/favorite/compare/project/audit artifacts are private and preserve physical source paths, earlier exposure and story context. No reader-safe redaction or actual identity-evidence claim."
      ],
      "requiredData": [
        {
          "description": "Original fictional reading-room invitation, exterior Maren/inner Arel forms and dedication-copy fixtures.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-authored surfaces, identity associations, actors and chronological actions; no historical archival, etymological or legal source claims.",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "1–30 actors, 1–40 initial physical surfaces and ≤120 chronological actions. Exact schema, unique IDs, existing container parents, root-only actor custody and acyclic containment. Text surfaces are named/unsealed; containers can have blank exterior form with identity null.",
        "Access requires the actor to hold the containing root and all ancestors of the target to be open. A sealed target hides its descendants, not its own exterior form. No automatic reading on transfer or opening; closure never erases exposure.",
        "Read exposes actor; show exposes only the explicit recipient without transfer. Copy exposes the copying actor to one selected visible face and creates a new unsealed text root for recipient, preserving literal form, authored identity and copy lineage. Receiving a copy is not reading it.",
        "Transfer applies only to roots and carries descendants. Rejected actions have no effect; subsequent steps use retained state. Duplicate copy IDs cannot overwrite or leave a partial exposure. Equal times replay in input order.",
        "Replay cutoff queues later actions with no effect. Unique observer/identity windows compare first exposure to any authored form: early/within/late, pending before deadline, not-observed once due. This is exposure, not inferred comprehension, memory or identity recognition.",
        "All copy/favorite/compare/project/audit artifacts are private and preserve physical source paths, earlier exposure and story context. No reader-safe redaction or actual identity-evidence claim."
      ],
      "outputs": [
        "First-exposure window findings with event, time and literal form.",
        "Applied/rejected/queued action trace and blocking ancestor/custodian paths.",
        "All explicit exposures with original-to-copy lineage.",
        "Current physical surfaces, containment, seals and root custody at cutoff.",
        "Private source-bound audit and individual observation proofs."
      ],
      "capabilities": [
        "Nested-surface visibility and root custody replay with atomically rejected impossible actions.",
        "Copy creation and lineage independent of recipient reading, retaining earlier exposure after closure.",
        "Finite cutoff replay with early/late/missing/pending first-exposure windows, distinct from interpretation."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Alias knowledge tools record identity relationships and who is declared to know them. Manuscript rename tools patch references. This task instead determines whether explicitly authored physical actions can expose a face under custody and nested seals, creates physical copies and traces source paths without inferring recognition. Switching an alias permission cannot reproduce document state or copy lineage.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "alias-identity-reveal-planner",
          "difference": "Physical access and copying are state transitions over nested surfaces; the output proves an exposure event rather than asserting that an observer recognized an identity. Custody, seals, copy roots and failed-event atomicity are separate data and rules."
        }
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-title-drift",
          "score": 0.10095238095238095,
          "sharedProfile": true,
          "difference": "Replay physical custody, nested visibility and copy lineage, then audit first authored name exposure against reveal windows at a selected timeline cutoff. versus Compare office references against character promotions and succession; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.09708333333333333,
          "sharedProfile": true,
          "difference": "Replay physical custody, nested visibility and copy lineage, then audit first authored name exposure against reveal windows at a selected timeline cutoff. versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-character-name-inventory",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Replay physical custody, nested visibility and copy lineage, then audit first authored name exposure against reveal windows at a selected timeline cutoff. versus Extract author confirmed names without assuming every capitalized word is a person; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A document’s physical journey and a name’s observed journey differ; expose that distinction without equating a visible alias with recognized identity.",
        "outline": [
          "Possession is not reading",
          "Original dedication travels alone",
          "Surface and actor contract",
          "Exterior versus hidden contents",
          "Chronological actions",
          "Physical copies and lineage",
          "First exposure versus convenient reveal",
          "Rejected continuity steps",
          "Private emotional purpose"
        ],
        "story": "The guest copies only an intimate dedication for a keeper, while the original remains elsewhere. Moving the opening later fails to repair an earlier exterior reading, so the author separates physical exposure from later recognition.",
        "storyAnalysis": "If the exterior form were an event heading rather than a writer alias, changing its declared association would move first writer exposure to the later dedication. The scene must support that changed model; a status warning cannot be erased by relabelling for convenience.",
        "evidence": "Original complete EN/JA reading-room guides and executable physical-state fixtures; no actual identity comprehension or archival practice claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/propDisclosure.md",
        "localizedBodies": {
          "en": "content/en/propDisclosure.md",
          "ja": "content/ja/propDisclosure.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default guest first sees Maren at time2 and is early for writer; keeper sees Arel only on actual read6, not copy delivery5.",
        "Sealed ancestor blocks inner reading while exterior remains visible; opening never itself reads.",
        "Wrong custodian or duplicate copy ID has no side effects; same-time events follow input order.",
        "Nested two-seal access retains concrete blocking path; missing ancestors and unsupported/null events fail clearly.",
        "Cutoff1 has no exposures and pending windows; deadline8 without reads reports missing.",
        "Actual edits must change replay, unknown/invalid input clears results, and private copy/export/project/compare flows require browser records.",
        "Both localized long-form guides and four viewport submissions must pass."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:903",
      "profileSource": "data/profiles.json#manuscript-audit",
      "specBatch": "batch-17",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Strict bounded containment/custody state machine, atomic event failures, dynamic copy IDs/lineage and first-exposure window evaluation."
      },
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "propDisclosure",
        "engineFiles": [
          "web/prop-disclosure.mjs",
          "web/prop-disclosure-tool.mjs",
          "web/prop-disclosure-view.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/prop-disclosure.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "actors",
          "label": [
            "Actors · JSON",
            "登場人物・JSON"
          ],
          "type": "textarea",
          "default": "[{\"id\":\"maker\",\"label\":\"Letter writer\"},{\"id\":\"guest\",\"label\":\"Invited reader\"},{\"id\":\"keeper\",\"label\":\"Archive keeper\"}]",
          "help": [
            "1–30 unique {id,label} objects. Actor IDs identify custodians and observers, not inferred identity owners.",
            "固有の{id,label}を1〜30件。人物IDは保管者・読む人を示し、名前の持ち主を推測しません。"
          ],
          "maxLength": 7000
        },
        {
          "key": "props",
          "label": [
            "Initial physical surfaces · JSON",
            "初期の物理的な面・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"envelope\",\n    \"label\": \"Outer envelope\",\n    \"kind\": \"container\",\n    \"parent\": null,\n    \"form\": \"Maren\",\n    \"identity\": \"writer\",\n    \"sealed\": true,\n    \"holder\": \"maker\"\n  },\n  {\n    \"id\": \"dedication\",\n    \"label\": \"Inner dedication\",\n    \"kind\": \"text\",\n    \"parent\": \"envelope\",\n    \"form\": \"Arel\",\n    \"identity\": \"writer\",\n    \"sealed\": false,\n    \"holder\": null\n  }\n]",
          "help": [
            "1–40 exact {id,label,kind,parent,form,identity,sealed,holder}. kind=container/text. Only roots have actor holders; children use null. Parent must be a container. Blank container form requires identity=null. Text needs a name and cannot be sealed. Every form→identity association is your fictional declaration.",
            "{id,label,kind,parent,form,identity,sealed,holder}だけを1〜40件。kindはcontainer/text。保管者は根だけ、子はnull。親は容器。容器の表示が空ならidentity=null。textは名前が必要で封鎖不可。表示と身元の対応は作者の架空の指定です。"
          ],
          "maxLength": 22000
        },
        {
          "key": "events",
          "label": [
            "Chronological physical actions · JSON",
            "時系列の物理動作・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"lend\",\n    \"at\": 1,\n    \"actor\": \"maker\",\n    \"action\": \"transfer\",\n    \"target\": \"envelope\",\n    \"to\": \"guest\"\n  },\n  {\n    \"id\": \"outer-read\",\n    \"at\": 2,\n    \"actor\": \"guest\",\n    \"action\": \"read\",\n    \"target\": \"envelope\"\n  },\n  {\n    \"id\": \"open\",\n    \"at\": 4,\n    \"actor\": \"guest\",\n    \"action\": \"open\",\n    \"target\": \"envelope\"\n  },\n  {\n    \"id\": \"copy\",\n    \"at\": 5,\n    \"actor\": \"guest\",\n    \"action\": \"copy\",\n    \"target\": \"dedication\",\n    \"to\": \"keeper\",\n    \"copyId\": \"archive-copy\"\n  },\n  {\n    \"id\": \"archive-read\",\n    \"at\": 6,\n    \"actor\": \"keeper\",\n    \"action\": \"read\",\n    \"target\": \"archive-copy\"\n  }\n]",
          "help": [
            "≤120 unique events; integer at 0–1,000,000, nondecreasing. Every event: id/at/actor/action/target. transfer/show add to; copy adds to/copyId; open/close/read add nothing. No extra fields. Equal times use supplied order. Failed actions do not mutate state.",
            "固有出来事120以内、整数atは0〜1,000,000の非降順。共通項目はid/at/actor/action/target。transfer/showはtoを追加、copyはto/copyIdを追加、open/close/readは追加なし。他項目不可。同時刻は入力順、拒否した動作は状態を変えません。"
          ],
          "maxLength": 25000
        },
        {
          "key": "windows",
          "label": [
            "Intended first-exposure windows · JSON",
            "最初の開示を予定する期間・JSON"
          ],
          "type": "textarea",
          "default": "[{\"observer\":\"guest\",\"identity\":\"writer\",\"earliest\":4,\"latest\":8},{\"observer\":\"keeper\",\"identity\":\"writer\",\"earliest\":6,\"latest\":8}]",
          "help": [
            "≤60 unique {observer,identity,earliest,latest}. Existing actors and initial identity IDs; integer 0–1,000,000. First exposure to any declared form counts. Pending is distinct from a missed deadline.",
            "固有の{observer,identity,earliest,latest}を60以内。既知人物と初期の身元ID、整数0〜1,000,000。指定身元のどの表示でも最初の開示を数えます。未到達と期限超過を分けます。"
          ],
          "maxLength": 10000
        },
        {
          "key": "through",
          "label": [
            "Replay through time · 0–1,000,000",
            "再生する時刻上限・0〜1,000,000"
          ],
          "type": "number",
          "default": 8,
          "help": null
        },
        {
          "key": "context",
          "label": [
            "Private scene purpose and limits",
            "非公開の場面目的・制限"
          ],
          "type": "textarea",
          "default": "The envelope uses the writer’s fictional public form Maren, while its dedication uses Arel. Receiving the sealed envelope should not reveal the dedication, but the outer label is already a declared form of the same identity.",
          "help": [
            "≤1000 units, retained in private copies and audit. The model tracks authored exposure, not comprehension, memory or whether a clue is fair.",
            "1000単位以内、非公開コピーと検証に残します。作者指定の開示を追うもので、理解、記憶、手掛かりの公正さは推定しません。"
          ],
          "maxLength": 1000
        }
      ]
    },
    {
      "id": "nw-manuscript-spoiler-safe-search-report",
      "slug": "manuscript-spoiler-safe-search-report",
      "name": "Manuscript spoiler safe search report",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-spoiler-safe-search-report/",
        "ja": "/ja/tools/manuscript-spoiler-safe-search-report/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Hide true identity fields from a selected reviewer view",
      "task": "Hide true identity fields from a selected reviewer view",
      "searchIntent": {
        "primary": "Complete the task: Hide true identity fields from a selected reviewer view",
        "queryHypothesis": "manuscript spoiler safe search report",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to hide true identity fields from a selected reviewer view?",
        "When should manuscript spoiler safe search report be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Hide true identity fields from a selected reviewer view",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Hide true identity fields from a selected reviewer view. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pseudonymous-manuscript-mystery",
          "score": 0.1090909090909091,
          "sharedProfile": false,
          "difference": "Hide true identity fields from a selected reviewer view versus Track author identity evidence and competing interpretations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Hide true identity fields from a selected reviewer view versus Hide reader identity while preserving production clarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-marriage-event-names",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Hide true identity fields from a selected reviewer view versus Update selected fields while preserving preevent references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Hide true identity fields from a selected reviewer view",
        "outline": [
          "Explain the specific decision: Hide true identity fields from a selected reviewer view",
          "Define the applicable contract and limits for Manuscript spoiler safe search report",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Hide true identity fields from a selected reviewer view; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Hide true identity fields from a selected reviewer view",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:904",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-draft-label-cleanup",
      "slug": "manuscript-draft-label-cleanup",
      "name": "Manuscript draft label cleanup",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-draft-label-cleanup/",
        "ja": "/ja/tools/manuscript-draft-label-cleanup/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Find temporary labels using a project supplied list",
      "task": "Find temporary labels using a project supplied list",
      "searchIntent": {
        "primary": "Complete the task: Find temporary labels using a project supplied list",
        "queryHypothesis": "manuscript draft label cleanup",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find temporary labels using a project supplied list?",
        "When should manuscript draft label cleanup be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find temporary labels using a project supplied list",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find temporary labels using a project supplied list. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cast-role-label-transition",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Find temporary labels using a project supplied list versus Replace temporary draft labels without losing scene references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-dialogue-label-name-policy",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Find temporary labels using a project supplied list versus Separate screenplay speaker labels from spoken names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-address-continuity-audit",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Find temporary labels using a project supplied list versus Find speaker pairs using unearned levels of familiarity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find temporary labels using a project supplied list",
        "outline": [
          "Explain the specific decision: Find temporary labels using a project supplied list",
          "Define the applicable contract and limits for Manuscript draft label cleanup",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find temporary labels using a project supplied list; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find temporary labels using a project supplied list",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:905",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-name-editorial-signoff",
      "slug": "manuscript-name-editorial-signoff",
      "name": "Manuscript name editorial signoff",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-editorial-signoff/",
        "ja": "/ja/tools/manuscript-name-editorial-signoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Require a named reviewer and unresolved issue disposition",
      "task": "Require a named reviewer and unresolved issue disposition",
      "searchIntent": {
        "primary": "Complete the task: Require a named reviewer and unresolved issue disposition",
        "queryHypothesis": "manuscript name editorial signoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require a named reviewer and unresolved issue disposition?",
        "When should manuscript name editorial signoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require a named reviewer and unresolved issue disposition",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require a named reviewer and unresolved issue disposition. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-character-split-revision",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Require a named reviewer and unresolved issue disposition versus Separate a combined draft role into distinct named characters; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-namesake-ambiguity",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Require a named reviewer and unresolved issue disposition versus Identify repeated names whose referents require context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-spoiler-safe-search-report",
          "score": 0.10416666666666666,
          "sharedProfile": true,
          "difference": "Require a named reviewer and unresolved issue disposition versus Hide true identity fields from a selected reviewer view; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require a named reviewer and unresolved issue disposition",
        "outline": [
          "Explain the specific decision: Require a named reviewer and unresolved issue disposition",
          "Define the applicable contract and limits for Manuscript name editorial signoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require a named reviewer and unresolved issue disposition; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require a named reviewer and unresolved issue disposition",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:906",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-manuscript-pronunciation-handoff",
      "slug": "manuscript-pronunciation-handoff",
      "name": "Manuscript pronunciation handoff",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-pronunciation-handoff/",
        "ja": "/ja/tools/manuscript-pronunciation-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Export approved reading notes with uncertainty markers",
      "task": "Export approved reading notes with uncertainty markers",
      "searchIntent": {
        "primary": "Complete the task: Export approved reading notes with uncertainty markers",
        "queryHypothesis": "manuscript pronunciation handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export approved reading notes with uncertainty markers?",
        "When should manuscript pronunciation handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export approved reading notes with uncertainty markers",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export approved reading notes with uncertainty markers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-pronunciation",
          "score": 0.1525,
          "sharedProfile": false,
          "difference": "Export approved reading notes with uncertainty markers versus Produce an author approved spoken introduction and ambiguity notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Export approved reading notes with uncertainty markers versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-npc-pronunciation-metadata",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Export approved reading notes with uncertainty markers versus Export approved pronunciations with dialogue assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export approved reading notes with uncertainty markers",
        "outline": [
          "Explain the specific decision: Export approved reading notes with uncertainty markers",
          "Define the applicable contract and limits for Manuscript pronunciation handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export approved reading notes with uncertainty markers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export approved reading notes with uncertainty markers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:907",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-series-cast-change-diff",
      "slug": "series-cast-change-diff",
      "name": "Series cast change diff",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/series-cast-change-diff/",
        "ja": "/ja/tools/series-cast-change-diff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Coauthors, serial comic teams, game writers and editors reconciling parallel naming revisions.",
      "scenario": "Current draft chooses Ivara Sel and retains a witness; incoming chooses Ivara Tarn with a reading bound to that name and deletes the witness. Naive field merging would mix incompatible story decisions.",
      "task": "Reconcile explicit base/current/incoming naming snapshots, preserve compatible changes, resolve whole-record and field conflicts under current locks, and validate reading ownership before exporting a complete ledger.",
      "searchIntent": {
        "primary": "Resolve naming conflicts between coauthors’ parallel cast ledgers.",
        "queryHypothesis": "merge character name changes between drafts",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "Can one-sided reading edits become invalid after another branch renames a character?",
        "How should an imported change respect current locked names?",
        "Why does a source change make an earlier decision stale?"
      ],
      "inputs": [
        {
          "key": "base",
          "use": "Author-declared ancestry, not verified history. 1–40 total IDs across all drafts. Each record has exactly id/name/reading/short; reading is null or {for,text}, short is null or nonblank text. Notes are authored, not pronunciation certificates."
        },
        {
          "key": "left",
          "use": "left is the current side protected by locks. IDs start with an ASCII letter and use ≤40 letters/digits/_/-. Different IDs never merge because their names look alike."
        },
        {
          "key": "right",
          "use": "Missing records represent deletion from this supplied snapshot. No omitted field is silently interpreted as unchanged. Preserve the real source before editing a fixture."
        },
        {
          "key": "locks",
          "use": "person/field. Locks refer to existing left records and name/reading/short only. A lock blocks a changed value or removal; the tool never silently unlocks it."
        },
        {
          "key": "resolutions",
          "use": "Use the decision controls beside the results. Resolve name before its reading. Captured expectations detect changed source cells, lock state and the merged name bound to a reading. Removing a decision is explicit."
        }
      ],
      "rules": [
        "Validate complete bounded snapshots with stable author-declared IDs and explicit name/reading/short fields. Reject omitted and extra record fields rather than dropping them.",
        "When all three records exist, retain equal fields or one-sided changes; differing changes on both sides remain conflicts.",
        "Treat same-ID independent additions and delete-versus-edit cases as whole-record decisions, not mixed identities.",
        "Current locks prevent changed values and record removal; no import silently unlocks them.",
        "Readings are authored null or {for,text}; for must exactly equal the selected name. No Unicode normalization, pronunciation generation or source certification.",
        "Captured expectations bind relevant base/current/incoming values and locks. Reading choices also bind the selected name. Changed expectations are stale and never silently reused.",
        "Guard capture against relevant source edits made after rendering. Unmatched decisions remain visible and block final output until explicitly removed.",
        "Always provide a private audit; offer a complete resolved snapshot only after all required conflicts, locks, stale choices and reading bindings are resolved. Same-label IDs remain separate."
      ],
      "requiredData": [
        {
          "description": "Original fictional three-draft courier/witness fixtures and exact field expectations",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "User-authored complete naming snapshots and declared current locks; no external name or approval service",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Validate complete bounded snapshots with stable author-declared IDs and explicit name/reading/short fields. Reject omitted and extra record fields rather than dropping them.",
        "When all three records exist, retain equal fields or one-sided changes; differing changes on both sides remain conflicts.",
        "Treat same-ID independent additions and delete-versus-edit cases as whole-record decisions, not mixed identities.",
        "Current locks prevent changed values and record removal; no import silently unlocks them.",
        "Readings are authored null or {for,text}; for must exactly equal the selected name. No Unicode normalization, pronunciation generation or source certification.",
        "Captured expectations bind relevant base/current/incoming values and locks. Reading choices also bind the selected name. Changed expectations are stale and never silently reused.",
        "Guard capture against relevant source edits made after rendering. Unmatched decisions remain visible and block final output until explicitly removed.",
        "Always provide a private audit; offer a complete resolved snapshot only after all required conflicts, locks, stale choices and reading bindings are resolved. Same-label IDs remain separate."
      ],
      "outputs": [
        "Per-field source values, automatic classification, exact captured context and current decision state",
        "Whole-record addition/deletion conflict outcomes and provisional retained/removed records",
        "Reading-binding and stale/unmatched decision issues, with exact same-label diagnostics",
        "Private full audit and complete resolved naming snapshot with unsupplied readings listed"
      ],
      "capabilities": [
        "Reconcile simultaneous naming edits with current-field locks and atomic delete/add conflict choices, without overwriting source drafts.",
        "Invalidate old decisions against exact relevant contexts and detect a reading copied onto a different merged name before allowing a complete handoff."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "The primary task is to decide which parallel naming changes to carry forward. It needs three snapshots, exact-context decisions, add/delete semantics, current-side locks, name-bound reading validation and a complete-export gate. Manuscript replacement locates occurrences; localization maps edition forms; credit governance records publication approvals. None of those computes three-way naming conflicts or a guarded resolved snapshot.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "character-name-replacement",
          "difference": "Replacement audits actual authored occurrences and protected spans. Reconciliation compares parallel record states against an explicit base, with one-sided/agreed/conflicting cases, atomic independent additions and delete/edit choices, stale decision contexts, current locks and reading-for/name binding. A completed naming merge does not change manuscript text."
        }
      },
      "nearestTools": [
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Reconcile explicit base/current/incoming naming snapshots, preserve compatible changes, resolve whole-record and field conflicts under current locks, and validate reading ownership before exporting a complete ledger. versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.12826086956521737,
          "sharedProfile": false,
          "difference": "Reconcile explicit base/current/incoming naming snapshots, preserve compatible changes, resolve whole-record and field conflicts under current locks, and validate reading ownership before exporting a complete ledger. versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-new-cast-collision",
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Reconcile explicit base/current/incoming naming snapshots, preserve compatible changes, resolve whole-record and field conflicts under current locks, and validate reading ownership before exporting a complete ledger. versus Compare a proposed cast against previous installments; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A structurally compatible field edit can still describe the wrong name, so merging naming drafts must preserve author decisions and exact reading ownership.",
        "outline": [
          "Separate creative choice from data reconciliation",
          "An original kite-post courier comic and a public chosen name",
          "Prepare explicit complete snapshots",
          "Read one-sided, agreed, conflicting and whole-record cases",
          "Preserve current locks when importing",
          "Resolve the default name/reading/witness decisions",
          "Invalidate old contexts and remove unmatched decisions explicitly",
          "Export private resolved data and verify real production assets separately"
        ],
        "story": "Coauthors revise a rooftop kite-post race comic. One chooses Ivara Sel as independence from a sponsor and retains Soren’s public acknowledgment; the other keeps Tarn, its performance note and removes the witness. A naive merge fits neither authored scene.",
        "storyAnalysis": "Changing Sel back to Tarn changes what Ivara refuses; deleting Soren needs a different visible acknowledgment. Preserving the incoming short label does not imply accepting its surname or reading. All names and conventions are fictional.",
        "evidence": "Complete original EN/JA kite-post courier guides and explicit counterfactual, MERGE-01–21, MERGE-HTML, 30 actual browser cases and four final viewport submissions. No contributor consent, real pronunciation or demand claim.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/castMerge.md",
        "localizedBodies": {
          "en": "content/en/castMerge.md",
          "ja": "content/ja/castMerge.md"
        }
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default courier name and witness deletion remain conflicts and withhold complete export.",
        "Keep current name, explicitly clear reading and keep current witness produce the documented complete snapshot.",
        "Locked field imports and locked record deletion stop; explicitly keeping current completes a clean import fixture.",
        "Source or lock changes stale previous decisions; reading decisions also stale when the chosen name changes.",
        "Independent same-ID additions are atomic; equal-name different IDs remain distinct; complete deliberate deletion can yield an empty snapshot.",
        "Real keyboard capture, blocked choice, custom reading, stale control guard, project recovery, downloads, copy/compare/favorites and both localized mobile pages require checks."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:908",
      "profileSource": "data/profiles.json#manuscript-audit",
      "specBatch": "batch-10",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Three-way and whole-record semantics, exact scoped decision expectations, cross-field reading ownership, guarded interactive capture and complete original bilingual documentation; no fabricated effort estimate."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-naming-project-restore-conflict",
          "input": "Explicit complete base/current/incoming id/name/reading/short snapshots, current person/field locks and scoped resolutions. Equal base/current models the import fixture.",
          "rule": "A one-sided incoming change cannot overwrite an exact current locked field or remove a record containing a lock. Keep-current is explicit; no automatic unlock or identity inference.",
          "output": "Blocked field or deletion evidence and a complete private snapshot only after constraints and exact-context decisions resolve.",
          "acceptance": "With base/current Nera Vosk locked on name and incoming Nera Senn, automatic overwrite is blocked. Explicit keep-current produces a downloaded complete snapshot containing Nera Vosk. Source snapshots remain unchanged.",
          "evidence": [
            "MERGE-04",
            "MERGE-05",
            "MERGE-06",
            "reports/cast-merge-browser-qa.json import-current-lock-module-blocks-overwrite",
            "reports/cast-merge-browser-qa.json import-current-lock-module-completes"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "castMerge",
        "engineFiles": [
          "web/cast-merge.mjs",
          "web/cast-merge-tool.mjs",
          "web/cast-merge-view.mjs",
          "web/cast-merge-ui.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/cast-merge.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "base",
          "label": [
            "Declared common base · JSON",
            "共通と宣言する底稿・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"courier\",\n    \"name\": \"Ivara Pell\",\n    \"reading\": {\n      \"for\": \"Ivara Pell\",\n      \"text\": \"ee-VAH-ra pel\"\n    },\n    \"short\": \"Iva\"\n  },\n  {\n    \"id\": \"witness\",\n    \"name\": \"Soren Dask\",\n    \"reading\": null,\n    \"short\": \"Sor\"\n  }\n]",
          "help": [
            "Author-declared ancestry, not verified history. 1–40 total IDs across all drafts. Each record has exactly id/name/reading/short; reading is null or {for,text}, short is null or nonblank text. Notes are authored, not pronunciation certificates.",
            "共通の履歴は作者の宣言です。全稿で異なるIDは1〜40件。各記録はid/name/reading/shortだけを持ち、readingはnullか{for,text}、shortはnullか空でない文字列です。読みのメモは作者指定で、発音を認証しません。"
          ],
          "maxLength": 200000
        },
        {
          "key": "left",
          "label": [
            "Current draft · JSON",
            "現在の稿・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"courier\",\n    \"name\": \"Ivara Sel\",\n    \"reading\": {\n      \"for\": \"Ivara Pell\",\n      \"text\": \"ee-VAH-ra pel\"\n    },\n    \"short\": \"Iva\"\n  },\n  {\n    \"id\": \"witness\",\n    \"name\": \"Soren Dask\",\n    \"reading\": null,\n    \"short\": \"Soren\"\n  }\n]",
          "help": [
            "left is the current side protected by locks. IDs start with an ASCII letter and use ≤40 letters/digits/_/-. Different IDs never merge because their names look alike.",
            "leftはロックで保護する現在稿です。IDは英字で始まる英数字・_・-の40文字以内。同じ表示名でも異なるIDを統合しません。"
          ],
          "maxLength": 200000
        },
        {
          "key": "right",
          "label": [
            "Incoming collaborator draft · JSON",
            "合作者から受け取った稿・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"courier\",\n    \"name\": \"Ivara Tarn\",\n    \"reading\": {\n      \"for\": \"Ivara Tarn\",\n      \"text\": \"ee-VAH-ra tarn\"\n    },\n    \"short\": \"Vara\"\n  }\n]",
          "help": [
            "Missing records represent deletion from this supplied snapshot. No omitted field is silently interpreted as unchanged. Preserve the real source before editing a fixture.",
            "この版にない記録は削除として比較します。欄の省略を変更なしとは解釈しません。例を編集する前に実際の原本を残してください。"
          ],
          "maxLength": 200000
        },
        {
          "key": "locks",
          "label": [
            "Current fields to preserve · JSON",
            "現在稿で保持する項目・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"person\": \"courier\",\n    \"field\": \"name\"\n  },\n  {\n    \"person\": \"witness\",\n    \"field\": \"short\"\n  }\n]",
          "help": [
            "person/field. Locks refer to existing left records and name/reading/short only. A lock blocks a changed value or removal; the tool never silently unlocks it.",
            "person/field。leftにある人物のname/reading/shortだけを指定。値の変更や記録削除を止め、勝手にロックを外しません。"
          ],
          "maxLength": 200000
        },
        {
          "key": "resolutions",
          "label": [
            "Exact-context author decisions · JSON",
            "正確な文脈に結び付く作者の判断・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Use the decision controls beside the results. Resolve name before its reading. Captured expectations detect changed source cells, lock state and the merged name bound to a reading. Removing a decision is explicit.",
            "結果の判断欄を使い、名前を先に、読みを後に決めます。記録した前提は元の値、ロック、読みが付く統合後の姓名の変化を検出します。判断の削除も明示して行います。"
          ],
          "maxLength": 200000
        }
      ]
    },
    {
      "id": "nw-manuscript-name-reading-rehearsal",
      "slug": "manuscript-name-reading-rehearsal",
      "name": "Manuscript name reading rehearsal",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-reading-rehearsal/",
        "ja": "/ja/tools/manuscript-name-reading-rehearsal/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Produce scene bounded name lists for a human read through",
      "task": "Produce scene bounded name lists for a human read through",
      "searchIntent": {
        "primary": "Complete the task: Produce scene bounded name lists for a human read through",
        "queryHypothesis": "manuscript name reading rehearsal",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce scene bounded name lists for a human read through?",
        "When should manuscript name reading rehearsal be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce scene bounded name lists for a human read through",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce scene bounded name lists for a human read through. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-name-variant-audit",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Produce scene bounded name lists for a human read through versus Find spelling variants for human identity confirmation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Produce scene bounded name lists for a human read through versus Check a dated reference ledger against scene identity states; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-secret-parentage-name-clues",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Produce scene bounded name lists for a human read through versus Place bounded clues without proving lineage through a name alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce scene bounded name lists for a human read through",
        "outline": [
          "Explain the specific decision: Produce scene bounded name lists for a human read through",
          "Define the applicable contract and limits for Manuscript name reading rehearsal",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce scene bounded name lists for a human read through; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce scene bounded name lists for a human read through",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:909",
      "profileSource": "data/profiles.json#manuscript-audit"
    },
    {
      "id": "nw-name-shortlist-blind-test",
      "slug": "name-shortlist-blind-test",
      "name": "Name shortlist blind test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-shortlist-blind-test/",
        "ja": "/ja/tools/name-shortlist-blind-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Collect unaided impressions without showing author explanations",
      "task": "Collect unaided impressions without showing author explanations",
      "searchIntent": {
        "primary": "Complete the task: Collect unaided impressions without showing author explanations",
        "queryHypothesis": "name shortlist blind test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect unaided impressions without showing author explanations?",
        "When should name shortlist blind test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Rotate candidate order without altering candidate strings",
        "Collect optional pseudonymous responses rather than legal identity"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect unaided impressions without showing author explanations",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations",
        "Counterbalanced worksheets",
        "Minimized response schema"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect unaided impressions without showing author explanations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Collect unaided impressions without showing author explanations versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-text-to-speech-test",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Collect unaided impressions without showing author explanations versus Collect recorded or reviewed pronunciations without accuracy claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-pronunciation-expectation-test",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Collect unaided impressions without showing author explanations versus Collect readings before exposing the approved pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect unaided impressions without showing author explanations",
        "outline": [
          "Explain the specific decision: Collect unaided impressions without showing author explanations",
          "Define the applicable contract and limits for Name shortlist blind test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect unaided impressions without showing author explanations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect unaided impressions without showing author explanations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Every candidate appears in every position across a full rotation",
        "No legal name is required"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:912",
      "profileSource": "data/profiles.json#reader-tests",
      "absorbedModules": [
        {
          "sourceId": "nw-name-test-counterbalancing",
          "input": "candidateOrder",
          "rule": "Rotate candidate order without altering candidate strings",
          "output": "Counterbalanced worksheets",
          "acceptance": "Every candidate appears in every position across a full rotation",
          "status": "design-integrated-not-implemented"
        },
        {
          "sourceId": "nw-name-test-respondent-privacy",
          "input": "responseFields",
          "rule": "Collect optional pseudonymous responses rather than legal identity",
          "output": "Minimized response schema",
          "acceptance": "No legal name is required",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-cast-delayed-recall-test",
      "slug": "cast-delayed-recall-test",
      "name": "Cast delayed recall test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/cast-delayed-recall-test/",
        "ja": "/ja/tools/cast-delayed-recall-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Test recall after a defined reading passage and delay",
      "task": "Test recall after a defined reading passage and delay",
      "searchIntent": {
        "primary": "Complete the task: Test recall after a defined reading passage and delay",
        "queryHypothesis": "cast delayed recall test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test recall after a defined reading passage and delay?",
        "When should cast delayed recall test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test recall after a defined reading passage and delay",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test recall after a defined reading passage and delay. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-cast-onboarding-reader-test",
          "score": 0.23484848484848486,
          "sharedProfile": false,
          "difference": "Test recall after a defined reading passage and delay versus Generate recall tasks after staged introductions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-test-revision-comparison",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Test recall after a defined reading passage and delay versus Compare before and after candidates with disclosed test conditions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-memory-test",
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Test recall after a defined reading passage and delay versus Compare reader recall using language specific test prompts; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test recall after a defined reading passage and delay",
        "outline": [
          "Explain the specific decision: Test recall after a defined reading passage and delay",
          "Define the applicable contract and limits for Cast delayed recall test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test recall after a defined reading passage and delay; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test recall after a defined reading passage and delay",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:913",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-spelling-dictation-test",
      "slug": "name-spelling-dictation-test",
      "name": "Name spelling dictation test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-spelling-dictation-test/",
        "ja": "/ja/tools/name-spelling-dictation-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Compare intended spelling against listener transcriptions",
      "task": "Compare intended spelling against listener transcriptions",
      "searchIntent": {
        "primary": "Complete the task: Compare intended spelling against listener transcriptions",
        "queryHypothesis": "name spelling dictation test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare intended spelling against listener transcriptions?",
        "When should name spelling dictation test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare intended spelling against listener transcriptions",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare intended spelling against listener transcriptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-first-impression",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Compare intended spelling against listener transcriptions versus Compare intended characterization against reader supplied impressions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-spelling-ledger",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Compare intended spelling against listener transcriptions versus Preserve source spelling, normalized form and editorial decision; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-list-spoiler-test",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare intended spelling against listener transcriptions versus Compare cast list entries against mystery disclosure timing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare intended spelling against listener transcriptions",
        "outline": [
          "Explain the specific decision: Compare intended spelling against listener transcriptions",
          "Define the applicable contract and limits for Name spelling dictation test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare intended spelling against listener transcriptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare intended spelling against listener transcriptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:914",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-pronunciation-expectation-test",
      "slug": "name-pronunciation-expectation-test",
      "name": "Name pronunciation expectation test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-pronunciation-expectation-test/",
        "ja": "/ja/tools/name-pronunciation-expectation-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Collect readings before exposing the approved pronunciation",
      "task": "Collect readings before exposing the approved pronunciation",
      "searchIntent": {
        "primary": "Complete the task: Collect readings before exposing the approved pronunciation",
        "queryHypothesis": "name pronunciation expectation test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to collect readings before exposing the approved pronunciation?",
        "When should name pronunciation expectation test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Collect readings before exposing the approved pronunciation",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Collect readings before exposing the approved pronunciation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-series-pronunciation-revisions",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Collect readings before exposing the approved pronunciation versus Record changed readings and downstream audio assets; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-test-revision-comparison",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Collect readings before exposing the approved pronunciation versus Compare before and after candidates with disclosed test conditions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-voice-cast-name-pronunciation-sheet",
          "score": 0.13055555555555554,
          "sharedProfile": false,
          "difference": "Collect readings before exposing the approved pronunciation versus Package author readings and uncertainty for performers; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Collect readings before exposing the approved pronunciation",
        "outline": [
          "Explain the specific decision: Collect readings before exposing the approved pronunciation",
          "Define the applicable contract and limits for Name pronunciation expectation test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Collect readings before exposing the approved pronunciation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Collect readings before exposing the approved pronunciation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:915",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-character-role-association-test",
      "slug": "character-role-association-test",
      "name": "Character role association test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/character-role-association-test/",
        "ja": "/ja/tools/character-role-association-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Compare reader associations with intended role without claiming objectivity",
      "task": "Compare reader associations with intended role without claiming objectivity",
      "searchIntent": {
        "primary": "Complete the task: Compare reader associations with intended role without claiming objectivity",
        "queryHypothesis": "character role association test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reader associations with intended role without claiming objectivity?",
        "When should character role association test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reader associations with intended role without claiming objectivity",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reader associations with intended role without claiming objectivity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.2356060606060606,
          "sharedProfile": false,
          "difference": "Compare reader associations with intended role without claiming objectivity versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-emotional-association-test",
          "score": 0.23409090909090907,
          "sharedProfile": true,
          "difference": "Compare reader associations with intended role without claiming objectivity versus Separate reader responses from asserted linguistic meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-decision-evidence-summary",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Compare reader associations with intended role without claiming objectivity versus Combine authored constraints and reader feedback without claiming certainty; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reader associations with intended role without claiming objectivity",
        "outline": [
          "Explain the specific decision: Compare reader associations with intended role without claiming objectivity",
          "Define the applicable contract and limits for Character role association test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reader associations with intended role without claiming objectivity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reader associations with intended role without claiming objectivity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:916",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-similarity-pair-test",
      "slug": "name-similarity-pair-test",
      "name": "Name similarity pair test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-similarity-pair-test/",
        "ja": "/ja/tools/name-similarity-pair-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Ask readers whether two supplied names refer to different people",
      "task": "Ask readers whether two supplied names refer to different people",
      "searchIntent": {
        "primary": "Complete the task: Ask readers whether two supplied names refer to different people",
        "queryHypothesis": "name similarity pair test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to ask readers whether two supplied names refer to different people?",
        "When should name similarity pair test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Ask readers whether two supplied names refer to different people",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Ask readers whether two supplied names refer to different people. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-identity-matching-test",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Ask readers whether two supplied names refer to different people versus Ask readers to match source and localized character forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-world-culture-grouping-test",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Ask readers whether two supplied names refer to different people versus Test whether readers group invented names according to authored cultures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-relation-inference-test",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Ask readers whether two supplied names refer to different people versus Check what a shared structure leads readers to infer; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Ask readers whether two supplied names refer to different people",
        "outline": [
          "Explain the specific decision: Ask readers whether two supplied names refer to different people",
          "Define the applicable contract and limits for Name similarity pair test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Ask readers whether two supplied names refer to different people; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Ask readers whether two supplied names refer to different people",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:917",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-cast-introduction-comprehension",
      "slug": "cast-introduction-comprehension",
      "name": "Cast introduction comprehension",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/cast-introduction-comprehension/",
        "ja": "/ja/tools/cast-introduction-comprehension/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Measure who readers think was introduced after a scene",
      "task": "Measure who readers think was introduced after a scene",
      "searchIntent": {
        "primary": "Complete the task: Measure who readers think was introduced after a scene",
        "queryHypothesis": "cast introduction comprehension",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to measure who readers think was introduced after a scene?",
        "When should cast introduction comprehension be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Measure who readers think was introduced after a scene",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Measure who readers think was introduced after a scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-large-cast-introduction-pacing",
          "score": 0.1670833333333333,
          "sharedProfile": false,
          "difference": "Measure who readers think was introduced after a scene versus Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-departure-return-names",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Measure who readers think was introduced after a scene versus Reintroduce a returning character after a long narrative absence; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-name-relationship-heatmap",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Measure who readers think was introduced after a scene versus Combine scene proximity with similarity for targeted review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Measure who readers think was introduced after a scene",
        "outline": [
          "Explain the specific decision: Measure who readers think was introduced after a scene",
          "Define the applicable contract and limits for Cast introduction comprehension",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Measure who readers think was introduced after a scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Measure who readers think was introduced after a scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:918",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-alias-reveal-comprehension",
      "slug": "alias-reveal-comprehension",
      "name": "Alias reveal comprehension",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/alias-reveal-comprehension/",
        "ja": "/ja/tools/alias-reveal-comprehension/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Test whether readers understand an identity connection at the intended moment",
      "task": "Test whether readers understand an identity connection at the intended moment",
      "searchIntent": {
        "primary": "Complete the task: Test whether readers understand an identity connection at the intended moment",
        "queryHypothesis": "alias reveal comprehension",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test whether readers understand an identity connection at the intended moment?",
        "When should alias reveal comprehension be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test whether readers understand an identity connection at the intended moment",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test whether readers understand an identity connection at the intended moment. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-alias-rename-counterfactual",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Test whether readers understand an identity connection at the intended moment versus Test whether a mystery remains fair after a naming change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-anonymous-narrator-reveal",
          "score": 0.16285714285714287,
          "sharedProfile": false,
          "difference": "Test whether readers understand an identity connection at the intended moment versus Test earlier self references against a later identity disclosure; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-world-culture-grouping-test",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Test whether readers understand an identity connection at the intended moment versus Test whether readers group invented names according to authored cultures; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test whether readers understand an identity connection at the intended moment",
        "outline": [
          "Explain the specific decision: Test whether readers understand an identity connection at the intended moment",
          "Define the applicable contract and limits for Alias reveal comprehension",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test whether readers understand an identity connection at the intended moment; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test whether readers understand an identity connection at the intended moment",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:919",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-family-relation-inference-test",
      "slug": "family-relation-inference-test",
      "name": "Family relation inference test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/family-relation-inference-test/",
        "ja": "/ja/tools/family-relation-inference-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Check what a shared structure leads readers to infer",
      "task": "Check what a shared structure leads readers to infer",
      "searchIntent": {
        "primary": "Complete the task: Check what a shared structure leads readers to infer",
        "queryHypothesis": "family relation inference test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check what a shared structure leads readers to infer?",
        "When should family relation inference test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check what a shared structure leads readers to infer",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check what a shared structure leads readers to infer. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-family-name-planner",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Check what a shared structure leads readers to infer versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-possession-naming-test",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Check what a shared structure leads readers to infer versus State what a name test can and cannot establish in the fictional rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-estranged-sibling-name-clues",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Check what a shared structure leads readers to infer versus Control how much shared structure reveals relatedness; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check what a shared structure leads readers to infer",
        "outline": [
          "Explain the specific decision: Check what a shared structure leads readers to infer",
          "Define the applicable contract and limits for Family relation inference test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check what a shared structure leads readers to infer; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check what a shared structure leads readers to infer",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:920",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-world-culture-grouping-test",
      "slug": "world-culture-grouping-test",
      "name": "World culture grouping test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/world-culture-grouping-test/",
        "ja": "/ja/tools/world-culture-grouping-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Test whether readers group invented names according to authored cultures",
      "task": "Test whether readers group invented names according to authored cultures",
      "searchIntent": {
        "primary": "Complete the task: Test whether readers group invented names according to authored cultures",
        "queryHypothesis": "world culture grouping test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test whether readers group invented names according to authored cultures?",
        "When should world culture grouping test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test whether readers group invented names according to authored cultures",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test whether readers group invented names according to authored cultures. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-culture-naming-contrast",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Test whether readers group invented names according to authored cultures versus Compare two invented cultures using explicit structural rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-similarity-pair-test",
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Test whether readers group invented names according to authored cultures versus Ask readers whether two supplied names refer to different people; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-comprehension",
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Test whether readers group invented names according to authored cultures versus Test whether readers understand an identity connection at the intended moment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test whether readers group invented names according to authored cultures",
        "outline": [
          "Explain the specific decision: Test whether readers group invented names according to authored cultures",
          "Define the applicable contract and limits for World culture grouping test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test whether readers group invented names according to authored cultures; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test whether readers group invented names according to authored cultures",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:921",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-emotional-association-test",
      "slug": "name-emotional-association-test",
      "name": "Name emotional association test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-emotional-association-test/",
        "ja": "/ja/tools/name-emotional-association-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Separate reader responses from asserted linguistic meaning",
      "task": "Separate reader responses from asserted linguistic meaning",
      "searchIntent": {
        "primary": "Complete the task: Separate reader responses from asserted linguistic meaning",
        "queryHypothesis": "name emotional association test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate reader responses from asserted linguistic meaning?",
        "When should name emotional association test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate reader responses from asserted linguistic meaning",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate reader responses from asserted linguistic meaning. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-role-association-test",
          "score": 0.23409090909090907,
          "sharedProfile": true,
          "difference": "Separate reader responses from asserted linguistic meaning versus Compare reader associations with intended role without claiming objectivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-beta-reader-test",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Separate reader responses from asserted linguistic meaning versus Generate blind comparison prompts and record reader confusion; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-hypothesis-preregistration",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Separate reader responses from asserted linguistic meaning versus Write the intended difference before collecting reader responses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate reader responses from asserted linguistic meaning",
        "outline": [
          "Explain the specific decision: Separate reader responses from asserted linguistic meaning",
          "Define the applicable contract and limits for Name emotional association test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate reader responses from asserted linguistic meaning; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate reader responses from asserted linguistic meaning",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:922",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-manga-balloon-name-recognition",
      "slug": "manga-balloon-name-recognition",
      "name": "Manga balloon name recognition",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/manga-balloon-name-recognition/",
        "ja": "/ja/tools/manga-balloon-name-recognition/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Test names in an actual panel layout",
      "task": "Test names in an actual panel layout",
      "searchIntent": {
        "primary": "Complete the task: Test names in an actual panel layout",
        "queryHypothesis": "manga balloon name recognition",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test names in an actual panel layout?",
        "When should manga balloon name recognition be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test names in an actual panel layout",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test names in an actual panel layout. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-recognition-trigger",
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Test names in an actual panel layout versus Test which observer can recognize which form and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-editor-name-correction-sheet",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Test names in an actual panel layout versus Track corrections with page and panel references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-crowd-shouted-name-clarity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Test names in an actual panel layout versus Test distinguishability against other names in the scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test names in an actual panel layout",
        "outline": [
          "Explain the specific decision: Test names in an actual panel layout",
          "Define the applicable contract and limits for Manga balloon name recognition",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test names in an actual panel layout; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test names in an actual panel layout",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:924",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-audio-cast-recognition-test",
      "slug": "audio-cast-recognition-test",
      "name": "Audio cast recognition test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/audio-cast-recognition-test/",
        "ja": "/ja/tools/audio-cast-recognition-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "Audio-drama, motion-comic and voiced-game creators checking spoken identity cues.",
      "scenario": "A local clip names a character; a listener chooses the perceived identity from declared options, and the author needs a confusion matrix rather than spelling recall.",
      "task": "Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence.",
      "searchIntent": {
        "primary": "Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence.",
        "queryHypothesis": "audio cast recognition test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "How do I separate an identity swap from a trial that was never played?",
        "What does a confusion count show without claiming a measured cause or population rate?"
      ],
      "inputs": [
        {
          "key": "identities",
          "use": "Stable character IDs and public response-option labels; no phonetic or gender inference."
        },
        {
          "key": "trials",
          "use": "Clip ID, intended identity and declared allowed choice set/condition."
        },
        {
          "key": "localClips",
          "use": "User-selected audio files kept locally, with actual load/playback failures and no upload."
        },
        {
          "key": "anonymousSession",
          "use": "A local anonymous trial session, without collecting names or contact details."
        },
        {
          "key": "responses",
          "use": "Observed choices, uncertainty, skipped trials and replay events; no fabricated defaults."
        }
      ],
      "rules": [
        "No observation rows exist until a trial is actually recorded.",
        "Keep intended identity out of the ordinary response view until the session is closed; this is display separation, not a secure exam system.",
        "Record actual playback/load state, not an inferred exposure time.",
        "A skipped or unplayed trial is not counted as an incorrect identity response.",
        "Confusion matrices separate conditions and intended identities; do not pool into a name-quality ranking.",
        "Choices must belong to the trial’s declared identity set; missing cells remain unknown.",
        "Project restoration requires users to reselect local files rather than inventing persistent audio access.",
        "No recruitment, uploads, population inference or measured intelligibility claim from synthetic QA."
      ],
      "requiredData": [
        {
          "description": "Creator-owned local clips and authored trial metadata",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Actual anonymous session observations; empty by default",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "No observation rows exist until a trial is actually recorded.",
        "Keep intended identity out of the ordinary response view until the session is closed; this is display separation, not a secure exam system.",
        "Record actual playback/load state, not an inferred exposure time.",
        "A skipped or unplayed trial is not counted as an incorrect identity response.",
        "Confusion matrices separate conditions and intended identities; do not pool into a name-quality ranking.",
        "Choices must belong to the trial’s declared identity set; missing cells remain unknown.",
        "Project restoration requires users to reselect local files rather than inventing persistent audio access.",
        "No recruitment, uploads, population inference or measured intelligibility claim from synthetic QA."
      ],
      "outputs": [
        "Private response ledger with playback/skip/replay states",
        "Per-condition intended-versus-selected count matrix and explicit denominators",
        "Missing exposure and incomplete-session diagnostics",
        "Local session handoff without raw audio or private filesystem paths"
      ],
      "capabilities": [
        "Distinguish systematic identity swaps from spelling mistakes and from trials never played.",
        "Run an ordinary response view that withholds intended identity while preserving the author’s private analysis separately."
      ],
      "contractScope": "implemented-task-scope; original-plan-and-limitations-retained",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "This task presents actual local clips and records identity attribution trials. Spelling recall and performer pronunciation preparation do not administer the same response task or produce intended-by-selected confusion cells.",
        "proposedDifferenceAxes": [
          "inputs",
          "data",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive.",
        "designComparison": {
          "nearest": "character-name-memorability-test",
          "difference": "Recall preserves raw spelling answers and timing inclusion. This tool uses supplied clip/trial IDs, identity-choice sets, actual playback state and intended-versus-selected responses, separating non-playback, skip and uncertain choices; no comprehension probability is predicted."
        }
      },
      "nearestTools": [
        {
          "id": "nw-dialogue-only-cast-test",
          "score": 0.1476190476190476,
          "sharedProfile": false,
          "difference": "Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence. versus Identify speakers using names without descriptive tags; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-spelling-dictation-test",
          "score": 0.1267543859649123,
          "sharedProfile": true,
          "difference": "Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence. versus Compare intended spelling against listener transcriptions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-memorability-test",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Administer a bounded local listening-identity exercise and summarize observed intended-versus-selected character responses without inventing listener evidence. versus Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "original-bilingual-long-form-manuscript",
        "theme": "A listener selecting the wrong person is a different observation from failing to reproduce a spelling.",
        "outline": [
          "Design the identity-choice task before recording",
          "Keep playback and answer states separate",
          "Read a confusion cell without inventing a cause",
          "Original scene: the handover at the radio desk",
          "Use observations to revise a cue, not declare a best name"
        ],
        "story": "A radio scene contains a handover that two listeners attribute to different named characters. The writer compares the actual clip and choice conditions, revising the reference cue rather than presenting a similarity heuristic as measured hearing.",
        "storyAnalysis": "Changing one spelling might leave the spoken cue unchanged. Distinguish an identity-attribution task, a script revision and a causal explanation that the observations alone cannot prove.",
        "evidence": "Local original audio QA fixtures and empty public observation defaults; no real listener study fabricated.",
        "evidenceStatus": "autonomous-content-and-behavior-checks-recorded; no human expert signature asserted",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": "content/read.mjs",
        "storyPath": "content/en/listening.md",
        "localizedBodies": {
          "en": "content/en/listening.md",
          "ja": "content/ja/listening.md"
        }
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Default matrix has no invented listeners or trials counted as observed.",
        "A missing or unreadable clip blocks playback and cannot create a completed response.",
        "A real choice increments only the correct condition/intended/selected cell.",
        "Skipped/unplayed/uncertain states remain distinct.",
        "A local-file restore asks for reselection without claiming prior audio is loaded.",
        "Synthetic browser QA is labeled synthetic and never reported as user research."
      ],
      "status": "candidate",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "implemented-autonomous-review",
        "ja": "implemented-autonomous-review"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Original bilingual long-form manuscripts and AI-assisted story edits exist; autonomous editorial checks proceed; no independent human expert review is asserted.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:925",
      "profileSource": "data/profiles.json#reader-tests",
      "specBatch": "batch-03",
      "implementationDifficulty": {
        "level": "high",
        "reason": "Dedicated state, scoped references and failure handling; no production time or cost estimate fabricated."
      },
      "absorbedModules": [
        {
          "sourceId": "nw-audio-nickname-confusion-test",
          "input": "Actual creator-selected local clips, neutral trial prompts, explicit public identity choices, intended identities, anonymous session tokens and frozen protocols.",
          "rule": "Record identity/uncertain answers only after browser ended/played coverage; keep skipped/unplayed/missing separate. Never infer pronunciation or hearing from spellings.",
          "output": "Condition/intended/selected counts from matching closed sessions, actual playback-state records and private no-audio handoff.",
          "acceptance": "No default observations; damaged or missing audio cannot produce identity answers; a chosen ID updates only its intended/selected cell; restoring clears live file access.",
          "evidence": [
            "LISTEN-01",
            "LISTEN-02",
            "LISTEN-04",
            "LISTEN-06",
            "LISTEN-10",
            "LISTEN-HTML",
            "reports/listening-browser-qa.json"
          ],
          "status": "implemented-under-acceptance-review"
        }
      ],
      "implementation": {
        "status": "local-delivery-candidate-under-review",
        "engineType": "listening",
        "engineFiles": [
          "web/listening-ledger.mjs",
          "web/listening-ui.js",
          "scripts/render-listening.mjs"
        ],
        "tests": [
          "test/engines.test.mjs",
          "test/advanced.test.mjs",
          "test/workflows.test.mjs",
          "test/listening.test.mjs"
        ],
        "trace": "reports/pilot-acceptance.json",
        "fullSpecAccepted": false
      },
      "implementedInputs": [
        {
          "key": "identities",
          "label": [
            "Identity options · JSON",
            "人物の選択肢・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"a\",\n    \"label\": \"Neri\"\n  },\n  {\n    \"id\": \"b\",\n    \"label\": \"Nera\"\n  }\n]",
          "help": [
            "Stable id and public label. Exact duplicate option labels within a trial are rejected; no pronunciation is guessed.",
            "固有のidと公開ラベル。同じ試行の完全に同じラベルは拒否し、読みは推測しません。"
          ],
          "maxLength": 50000,
          "requiredInProject": true
        },
        {
          "key": "trials",
          "label": [
            "Private trial key · JSON",
            "非公開の試行と正解・JSON"
          ],
          "type": "textarea",
          "default": "[\n  {\n    \"id\": \"t1\",\n    \"clip\": \"clip01\",\n    \"condition\": \"clean\",\n    \"prompt\": \"Clip 1\",\n    \"intended\": \"a\",\n    \"choices\": [\n      \"a\",\n      \"b\"\n    ]\n  },\n  {\n    \"id\": \"t2\",\n    \"clip\": \"clip02\",\n    \"condition\": \"clean\",\n    \"prompt\": \"Clip 2\",\n    \"intended\": \"b\",\n    \"choices\": [\n      \"a\",\n      \"b\"\n    ]\n  }\n]",
          "help": [
            "id, neutral clip/condition IDs, neutral prompt, intended identity and allowed choices. Fixed supplied order, not randomized research. Do not place the answer in clip IDs or prompts.",
            "id、中立なclipとconditionのID、中立なprompt、intended、choices。入力順で、無作為化した研究ではありません。clip IDやpromptに正解を書かないでください。"
          ],
          "maxLength": 50000,
          "requiredInProject": true
        },
        {
          "key": "sessions",
          "label": [
            "Private frozen sessions · JSON",
            "非公開の条件付きセッション・JSON"
          ],
          "type": "textarea",
          "default": "[]",
          "help": [
            "Empty until you explicitly open and record a session. Each session retains its exact protocol. Closed matching sessions only enter current counts; no raw audio or filenames are stored.",
            "明示してセッションを開くまでは空です。各セッションは正確な条件を保持し、現在と一致する終了セッションだけを集計します。生の音声やファイル名は保存しません。"
          ],
          "maxLength": 180000,
          "requiredInProject": true
        }
      ]
    },
    {
      "id": "nw-bilingual-identity-matching-test",
      "slug": "bilingual-identity-matching-test",
      "name": "Bilingual identity matching test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/bilingual-identity-matching-test/",
        "ja": "/ja/tools/bilingual-identity-matching-test/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Ask readers to match source and localized character forms",
      "task": "Ask readers to match source and localized character forms",
      "searchIntent": {
        "primary": "Complete the task: Ask readers to match source and localized character forms",
        "queryHypothesis": "bilingual identity matching test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to ask readers to match source and localized character forms?",
        "When should bilingual identity matching test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Ask readers to match source and localized character forms",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Ask readers to match source and localized character forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-similarity-pair-test",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Ask readers to match source and localized character forms versus Ask readers whether two supplied names refer to different people; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-identity-under-fame",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Ask readers to match source and localized character forms versus Separate public shorthand from private relationship forms; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-port-city-migrant-identities",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Ask readers to match source and localized character forms versus Track source names and contact forms without random cultural mixing; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Ask readers to match source and localized character forms",
        "outline": [
          "Explain the specific decision: Ask readers to match source and localized character forms",
          "Define the applicable contract and limits for Bilingual identity matching test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Ask readers to match source and localized character forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Ask readers to match source and localized character forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:926",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-accessibility-comparison",
      "slug": "name-accessibility-comparison",
      "name": "Name accessibility comparison",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-accessibility-comparison/",
        "ja": "/ja/tools/name-accessibility-comparison/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Record participant specific difficulties without generalizing to a diagnosis",
      "task": "Record participant specific difficulties without generalizing to a diagnosis",
      "searchIntent": {
        "primary": "Complete the task: Record participant specific difficulties without generalizing to a diagnosis",
        "queryHypothesis": "name accessibility comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record participant specific difficulties without generalizing to a diagnosis?",
        "When should name accessibility comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record participant specific difficulties without generalizing to a diagnosis",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record participant specific difficulties without generalizing to a diagnosis. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-candidate-comparison",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Record participant specific difficulties without generalizing to a diagnosis versus Compare a fixed shortlist against task specific criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-accessibility",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Record participant specific difficulties without generalizing to a diagnosis versus Provide a fair alternative when a clue relies on visual or audio distinction; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-craft-comparison",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Record participant specific difficulties without generalizing to a diagnosis versus Compare two approaches using the same story constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record participant specific difficulties without generalizing to a diagnosis",
        "outline": [
          "Explain the specific decision: Record participant specific difficulties without generalizing to a diagnosis",
          "Define the applicable contract and limits for Name accessibility comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record participant specific difficulties without generalizing to a diagnosis; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record participant specific difficulties without generalizing to a diagnosis",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:927",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-character-name-preference-study",
      "slug": "character-name-preference-study",
      "name": "Character name preference study",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/character-name-preference-study/",
        "ja": "/ja/tools/character-name-preference-study/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Compare choices with reasons and disclose sample limitations",
      "task": "Compare choices with reasons and disclose sample limitations",
      "searchIntent": {
        "primary": "Complete the task: Compare choices with reasons and disclose sample limitations",
        "queryHypothesis": "character name preference study",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare choices with reasons and disclose sample limitations?",
        "When should character name preference study be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare choices with reasons and disclose sample limitations",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare choices with reasons and disclose sample limitations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-court-name-forms",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare choices with reasons and disclose sample limitations versus Record local conventions with explicit evidence limitations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-edit-decision-log",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare choices with reasons and disclose sample limitations versus Preserve reasons, reviewers and affected passages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-fictional-legal-name-note",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Compare choices with reasons and disclose sample limitations versus Separate creative choices from real name registration advice; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare choices with reasons and disclose sample limitations",
        "outline": [
          "Explain the specific decision: Compare choices with reasons and disclose sample limitations",
          "Define the applicable contract and limits for Character name preference study",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare choices with reasons and disclose sample limitations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare choices with reasons and disclose sample limitations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:928",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-hypothesis-preregistration",
      "slug": "name-hypothesis-preregistration",
      "name": "Name hypothesis preregistration",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-hypothesis-preregistration/",
        "ja": "/ja/tools/name-hypothesis-preregistration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Write the intended difference before collecting reader responses",
      "task": "Write the intended difference before collecting reader responses",
      "searchIntent": {
        "primary": "Complete the task: Write the intended difference before collecting reader responses",
        "queryHypothesis": "name hypothesis preregistration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to write the intended difference before collecting reader responses?",
        "When should name hypothesis preregistration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Write the intended difference before collecting reader responses",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Write the intended difference before collecting reader responses. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-first-impression",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Write the intended difference before collecting reader responses versus Compare intended characterization against reader supplied impressions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-emotional-association-test",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Write the intended difference before collecting reader responses versus Separate reader responses from asserted linguistic meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-role-association-test",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Write the intended difference before collecting reader responses versus Compare reader associations with intended role without claiming objectivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Write the intended difference before collecting reader responses",
        "outline": [
          "Explain the specific decision: Write the intended difference before collecting reader responses",
          "Define the applicable contract and limits for Name hypothesis preregistration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Write the intended difference before collecting reader responses; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Write the intended difference before collecting reader responses",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:929",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-test-small-sample-report",
      "slug": "name-test-small-sample-report",
      "name": "Name test small sample report",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-small-sample-report/",
        "ja": "/ja/tools/name-test-small-sample-report/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Show raw responses and uncertainty without significance claims",
      "task": "Show raw responses and uncertainty without significance claims",
      "searchIntent": {
        "primary": "Complete the task: Show raw responses and uncertainty without significance claims",
        "queryHypothesis": "name test small sample report",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show raw responses and uncertainty without significance claims?",
        "When should name test small sample report be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show raw responses and uncertainty without significance claims",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show raw responses and uncertainty without significance claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-name-text-to-speech-test",
          "score": 0.15833333333333333,
          "sharedProfile": false,
          "difference": "Show raw responses and uncertainty without significance claims versus Collect recorded or reviewed pronunciations without accuracy claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Show raw responses and uncertainty without significance claims versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-emotional-association-test",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Show raw responses and uncertainty without significance claims versus Separate reader responses from asserted linguistic meaning; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show raw responses and uncertainty without significance claims",
        "outline": [
          "Explain the specific decision: Show raw responses and uncertainty without significance claims",
          "Define the applicable contract and limits for Name test small sample report",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show raw responses and uncertainty without significance claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show raw responses and uncertainty without significance claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:932",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-test-contradictory-feedback",
      "slug": "name-test-contradictory-feedback",
      "name": "Name test contradictory feedback",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-contradictory-feedback/",
        "ja": "/ja/tools/name-test-contradictory-feedback/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Preserve disagreement instead of collapsing it into one score",
      "task": "Preserve disagreement instead of collapsing it into one score",
      "searchIntent": {
        "primary": "Complete the task: Preserve disagreement instead of collapsing it into one score",
        "queryHypothesis": "name test contradictory feedback",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve disagreement instead of collapsing it into one score?",
        "When should name test contradictory feedback be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve disagreement instead of collapsing it into one score",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve disagreement instead of collapsing it into one score. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-creation-name-feedback",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve disagreement instead of collapsing it into one score versus Explain constraints before a player submits an invalid name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-memorability-test",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve disagreement instead of collapsing it into one score versus Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-possession-naming-test",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Preserve disagreement instead of collapsing it into one score versus State what a name test can and cannot establish in the fictional rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve disagreement instead of collapsing it into one score",
        "outline": [
          "Explain the specific decision: Preserve disagreement instead of collapsing it into one score",
          "Define the applicable contract and limits for Name test contradictory feedback",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve disagreement instead of collapsing it into one score; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve disagreement instead of collapsing it into one score",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:933",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-test-revision-comparison",
      "slug": "name-test-revision-comparison",
      "name": "Name test revision comparison",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-revision-comparison/",
        "ja": "/ja/tools/name-test-revision-comparison/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Compare before and after candidates with disclosed test conditions",
      "task": "Compare before and after candidates with disclosed test conditions",
      "searchIntent": {
        "primary": "Complete the task: Compare before and after candidates with disclosed test conditions",
        "queryHypothesis": "name test revision comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare before and after candidates with disclosed test conditions?",
        "When should name test revision comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare before and after candidates with disclosed test conditions",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare before and after candidates with disclosed test conditions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-cast-delayed-recall-test",
          "score": 0.1765151515151515,
          "sharedProfile": true,
          "difference": "Compare before and after candidates with disclosed test conditions versus Test recall after a defined reading passage and delay; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-possession-naming-test",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Compare before and after candidates with disclosed test conditions versus State what a name test can and cannot establish in the fictional rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-pronunciation-expectation-test",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Compare before and after candidates with disclosed test conditions versus Collect readings before exposing the approved pronunciation; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare before and after candidates with disclosed test conditions",
        "outline": [
          "Explain the specific decision: Compare before and after candidates with disclosed test conditions",
          "Define the applicable contract and limits for Name test revision comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare before and after candidates with disclosed test conditions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare before and after candidates with disclosed test conditions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:934",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-test-cultural-review-questions",
      "slug": "name-test-cultural-review-questions",
      "name": "Name test cultural review questions",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-cultural-review-questions/",
        "ja": "/ja/tools/name-test-cultural-review-questions/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Prepare context specific questions for a qualified reviewer",
      "task": "Prepare context specific questions for a qualified reviewer",
      "searchIntent": {
        "primary": "Complete the task: Prepare context specific questions for a qualified reviewer",
        "queryHypothesis": "name test cultural review questions",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prepare context specific questions for a qualified reviewer?",
        "When should name test cultural review questions be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prepare context specific questions for a qualified reviewer",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prepare context specific questions for a qualified reviewer. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-sensitivity-query-list",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Prepare context specific questions for a qualified reviewer versus Collect specific cultural uncertainties for a qualified reader; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-memorability-test",
          "score": 0.11333333333333333,
          "sharedProfile": false,
          "difference": "Prepare context specific questions for a qualified reviewer versus Prepare and record a bounded recall exercise with exposure, response and missing-observation states kept separate.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-naming-sensitivity-review",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Prepare context specific questions for a qualified reviewer versus Require context and native language review for cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prepare context specific questions for a qualified reviewer",
        "outline": [
          "Explain the specific decision: Prepare context specific questions for a qualified reviewer",
          "Define the applicable contract and limits for Name test cultural review questions",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prepare context specific questions for a qualified reviewer; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prepare context specific questions for a qualified reviewer",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:935",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-heuristic-score-explainer",
      "slug": "name-heuristic-score-explainer",
      "name": "Name heuristic score explainer",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-heuristic-score-explainer/",
        "ja": "/ja/tools/name-heuristic-score-explainer/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Expose weights and component calculations for a supplied shortlist",
      "task": "Expose weights and component calculations for a supplied shortlist",
      "searchIntent": {
        "primary": "Complete the task: Expose weights and component calculations for a supplied shortlist",
        "queryHypothesis": "name heuristic score explainer",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to expose weights and component calculations for a supplied shortlist?",
        "When should name heuristic score explainer be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Show component formula and ranking changes when weights change"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Expose weights and component calculations for a supplied shortlist",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations",
        "Sensitivity table"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Expose weights and component calculations for a supplied shortlist. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-invented-achievement-names",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Expose weights and component calculations for a supplied shortlist versus Derive an earned component from a documented story action; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-candidate-comparison",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Expose weights and component calculations for a supplied shortlist versus Compare a fixed shortlist against task specific criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-candidate-decision",
          "score": 0.065,
          "sharedProfile": false,
          "difference": "Expose weights and component calculations for a supplied shortlist versus Compare a fixed shortlist using published heuristic criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Expose weights and component calculations for a supplied shortlist",
        "outline": [
          "Explain the specific decision: Expose weights and component calculations for a supplied shortlist",
          "Define the applicable contract and limits for Name heuristic score explainer",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Expose weights and component calculations for a supplied shortlist; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Expose weights and component calculations for a supplied shortlist",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Weight-only changes leave candidate strings fixed"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:936",
      "profileSource": "data/profiles.json#reader-tests",
      "absorbedModules": [
        {
          "sourceId": "nw-name-scoring-sensitivity",
          "input": "weights",
          "rule": "Show component formula and ranking changes when weights change",
          "output": "Sensitivity table",
          "acceptance": "Weight-only changes leave candidate strings fixed",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-cast-confusion-severity-triage",
      "slug": "cast-confusion-severity-triage",
      "name": "Cast confusion severity triage",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/cast-confusion-severity-triage/",
        "ja": "/ja/tools/cast-confusion-severity-triage/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Prioritize reader reported collisions by actual scene consequences",
      "task": "Prioritize reader reported collisions by actual scene consequences",
      "searchIntent": {
        "primary": "Complete the task: Prioritize reader reported collisions by actual scene consequences",
        "queryHypothesis": "cast confusion severity triage",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prioritize reader reported collisions by actual scene consequences?",
        "When should cast confusion severity triage be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prioritize reader reported collisions by actual scene consequences",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prioritize reader reported collisions by actual scene consequences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-cousin-reunion-cast-names",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Prioritize reader reported collisions by actual scene consequences versus Avoid collisions during a large family gathering scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-honorific-policy",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Prioritize reader reported collisions by actual scene consequences versus Compare retained, translated and omitted forms with scene consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-scene-cooccurrence-name-audit",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Prioritize reader reported collisions by actual scene consequences versus Prioritize collisions between characters who share scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prioritize reader reported collisions by actual scene consequences",
        "outline": [
          "Explain the specific decision: Prioritize reader reported collisions by actual scene consequences",
          "Define the applicable contract and limits for Cast confusion severity triage",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prioritize reader reported collisions by actual scene consequences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prioritize reader reported collisions by actual scene consequences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:938",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-name-decision-evidence-summary",
      "slug": "name-decision-evidence-summary",
      "name": "Name decision evidence summary",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-decision-evidence-summary/",
        "ja": "/ja/tools/name-decision-evidence-summary/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Combine authored constraints and reader feedback without claiming certainty",
      "task": "Combine authored constraints and reader feedback without claiming certainty",
      "searchIntent": {
        "primary": "Complete the task: Combine authored constraints and reader feedback without claiming certainty",
        "queryHypothesis": "name decision evidence summary",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to combine authored constraints and reader feedback without claiming certainty?",
        "When should name decision evidence summary be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Combine authored constraints and reader feedback without claiming certainty",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Combine authored constraints and reader feedback without claiming certainty. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-role-association-test",
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Combine authored constraints and reader feedback without claiming certainty versus Compare reader associations with intended role without claiming objectivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-arc-reader-interpretation-test",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Combine authored constraints and reader feedback without claiming certainty versus Collect reader explanations without claiming universal symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-surname-locality-check",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Combine authored constraints and reader feedback without claiming certainty versus Record geographic evidence without claiming universal distribution; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Combine authored constraints and reader feedback without claiming certainty",
        "outline": [
          "Explain the specific decision: Combine authored constraints and reader feedback without claiming certainty",
          "Define the applicable contract and limits for Name decision evidence summary",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Combine authored constraints and reader feedback without claiming certainty; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Combine authored constraints and reader feedback without claiming certainty",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:939",
      "profileSource": "data/profiles.json#reader-tests"
    },
    {
      "id": "nw-naming-scene-laboratory",
      "slug": "naming-scene-laboratory",
      "name": "Naming scene laboratory",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/naming-scene-laboratory/",
        "ja": "/ja/tools/naming-scene-laboratory/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare one scene written with three explicitly different naming decisions",
      "task": "Compare one scene written with three explicitly different naming decisions",
      "searchIntent": {
        "primary": "Complete the task: Compare one scene written with three explicitly different naming decisions",
        "queryHypothesis": "naming scene laboratory",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare one scene written with three explicitly different naming decisions?",
        "When should naming scene laboratory be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Vary one naming decision and explain the narrative consequence"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare one scene written with three explicitly different naming decisions",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work",
        "Before-after annotation"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare one scene written with three explicitly different naming decisions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-address-scene-audit",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Compare one scene written with three explicitly different naming decisions versus Check speaker relationship and source limits for one scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Compare one scene written with three explicitly different naming decisions versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare one scene written with three explicitly different naming decisions versus Track knowledge of identity across a mistaken identity scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare one scene written with three explicitly different naming decisions",
        "outline": [
          "Explain the specific decision: Compare one scene written with three explicitly different naming decisions",
          "Define the applicable contract and limits for Naming scene laboratory",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare one scene written with three explicitly different naming decisions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare one scene written with three explicitly different naming decisions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "A changed name with unchanged consequence is an incomplete exercise"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:942",
      "profileSource": "data/profiles.json#editorial-content",
      "absorbedModules": [
        {
          "sourceId": "nw-naming-method-transfer-exercise",
          "input": "originalScene; decisionVariable",
          "rule": "Vary one naming decision and explain the narrative consequence",
          "output": "Before-after annotation",
          "acceptance": "A changed name with unchanged consequence is an incomplete exercise",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-character-introduction-rewrite",
      "slug": "character-introduction-rewrite",
      "name": "Character introduction rewrite",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/character-introduction-rewrite/",
        "ja": "/ja/tools/character-introduction-rewrite/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Revise a supplied introduction to make identity clear sooner",
      "task": "Revise a supplied introduction to make identity clear sooner",
      "searchIntent": {
        "primary": "Complete the task: Revise a supplied introduction to make identity clear sooner",
        "queryHypothesis": "character introduction rewrite",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to revise a supplied introduction to make identity clear sooner?",
        "When should character introduction rewrite be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Revise a supplied introduction to make identity clear sooner",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Revise a supplied introduction to make identity clear sooner. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-disguise-introduction-name",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Revise a supplied introduction to make identity clear sooner versus Choose a name that fits what an observer can plausibly know; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-large-cast-introduction-pacing",
          "score": 0.09954545454545455,
          "sharedProfile": false,
          "difference": "Revise a supplied introduction to make identity clear sooner versus Schedule author-declared identity and label introductions across scene slots while respecting dependencies, locked placements and explicit per-scene editorial budgets.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-introduction-comprehension",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Revise a supplied introduction to make identity clear sooner versus Measure who readers think was introduced after a scene; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Revise a supplied introduction to make identity clear sooner",
        "outline": [
          "Explain the specific decision: Revise a supplied introduction to make identity clear sooner",
          "Define the applicable contract and limits for Character introduction rewrite",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Revise a supplied introduction to make identity clear sooner; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Revise a supplied introduction to make identity clear sooner",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:943",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-family-naming-scene-exercise",
      "slug": "family-naming-scene-exercise",
      "name": "Family naming scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/family-naming-scene-exercise/",
        "ja": "/ja/tools/family-naming-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Show a shared surname creating a specific relationship inference",
      "task": "Show a shared surname creating a specific relationship inference",
      "searchIntent": {
        "primary": "Complete the task: Show a shared surname creating a specific relationship inference",
        "queryHypothesis": "family naming scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show a shared surname creating a specific relationship inference?",
        "When should family naming scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show a shared surname creating a specific relationship inference",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show a shared surname creating a specific relationship inference. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-memory-scene-exercise",
          "score": 0.2833333333333333,
          "sharedProfile": true,
          "difference": "Show a shared surname creating a specific relationship inference versus Show how a remembered form reveals relationship history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-name-planner",
          "score": 0.2056818181818182,
          "sharedProfile": false,
          "difference": "Show a shared surname creating a specific relationship inference versus Assign shared surnames across a relationship graph; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nickname-consent-scene-exercise",
          "score": 0.19416666666666665,
          "sharedProfile": true,
          "difference": "Show a shared surname creating a specific relationship inference versus Show acceptance and refusal through dialogue consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show a shared surname creating a specific relationship inference",
        "outline": [
          "Explain the specific decision: Show a shared surname creating a specific relationship inference",
          "Define the applicable contract and limits for Family naming scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show a shared surname creating a specific relationship inference; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show a shared surname creating a specific relationship inference",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:944",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-alias-reveal-scene-exercise",
      "slug": "alias-reveal-scene-exercise",
      "name": "Alias reveal scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/alias-reveal-scene-exercise/",
        "ja": "/ja/tools/alias-reveal-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare fair clue placement before a controlled reveal",
      "task": "Compare fair clue placement before a controlled reveal",
      "searchIntent": {
        "primary": "Complete the task: Compare fair clue placement before a controlled reveal",
        "queryHypothesis": "alias reveal scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare fair clue placement before a controlled reveal?",
        "When should alias reveal scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare fair clue placement before a controlled reveal",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare fair clue placement before a controlled reveal. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-alias-reveal-parity",
          "score": 0.17575757575757575,
          "sharedProfile": false,
          "difference": "Compare fair clue placement before a controlled reveal versus Keep clue timing comparable across language editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-comprehension",
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Compare fair clue placement before a controlled reveal versus Test whether readers understand an identity connection at the intended moment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Compare fair clue placement before a controlled reveal versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare fair clue placement before a controlled reveal",
        "outline": [
          "Explain the specific decision: Compare fair clue placement before a controlled reveal",
          "Define the applicable contract and limits for Alias reveal scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare fair clue placement before a controlled reveal; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare fair clue placement before a controlled reveal",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:945",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-nickname-consent-scene-exercise",
      "slug": "nickname-consent-scene-exercise",
      "name": "Nickname consent scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/nickname-consent-scene-exercise/",
        "ja": "/ja/tools/nickname-consent-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Show acceptance and refusal through dialogue consequences",
      "task": "Show acceptance and refusal through dialogue consequences",
      "searchIntent": {
        "primary": "Complete the task: Show acceptance and refusal through dialogue consequences",
        "queryHypothesis": "nickname consent scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show acceptance and refusal through dialogue consequences?",
        "When should nickname consent scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show acceptance and refusal through dialogue consequences",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show acceptance and refusal through dialogue consequences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.19416666666666665,
          "sharedProfile": true,
          "difference": "Show acceptance and refusal through dialogue consequences versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "score": 0.19416666666666665,
          "sharedProfile": true,
          "difference": "Show acceptance and refusal through dialogue consequences versus Show how a remembered form reveals relationship history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.15833333333333333,
          "sharedProfile": true,
          "difference": "Show acceptance and refusal through dialogue consequences versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show acceptance and refusal through dialogue consequences",
        "outline": [
          "Explain the specific decision: Show acceptance and refusal through dialogue consequences",
          "Define the applicable contract and limits for Nickname consent scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show acceptance and refusal through dialogue consequences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show acceptance and refusal through dialogue consequences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:946",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-title-rejection-scene-exercise",
      "slug": "title-rejection-scene-exercise",
      "name": "Title rejection scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/title-rejection-scene-exercise/",
        "ja": "/ja/tools/title-rejection-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Make a rejected title affect subsequent character treatment",
      "task": "Make a rejected title affect subsequent character treatment",
      "searchIntent": {
        "primary": "Complete the task: Make a rejected title affect subsequent character treatment",
        "queryHypothesis": "title rejection scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to make a rejected title affect subsequent character treatment?",
        "When should title rejection scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Make a rejected title affect subsequent character treatment",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Make a rejected title affect subsequent character treatment. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Make a rejected title affect subsequent character treatment versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Make a rejected title affect subsequent character treatment versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-inheritance-scene-exercise",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Make a rejected title affect subsequent character treatment versus Contrast gratitude, obligation and resistance within a namesake decision; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Make a rejected title affect subsequent character treatment",
        "outline": [
          "Explain the specific decision: Make a rejected title affect subsequent character treatment",
          "Define the applicable contract and limits for Title rejection scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Make a rejected title affect subsequent character treatment; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Make a rejected title affect subsequent character treatment",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:947",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-chosen-name-scene-exercise",
      "slug": "chosen-name-scene-exercise",
      "name": "Chosen name scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/chosen-name-scene-exercise/",
        "ja": "/ja/tools/chosen-name-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Connect self naming to agency without prescribing one emotional response",
      "task": "Connect self naming to agency without prescribing one emotional response",
      "searchIntent": {
        "primary": "Complete the task: Connect self naming to agency without prescribing one emotional response",
        "queryHypothesis": "chosen name scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to connect self naming to agency without prescribing one emotional response?",
        "When should chosen name scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Connect self naming to agency without prescribing one emotional response",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Connect self naming to agency without prescribing one emotional response. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-coming-of-age-chosen-name",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Connect self naming to agency without prescribing one emotional response versus Connect a name decision to a specific act of agency; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-deliberate-misnaming-scene",
          "score": 0.17833333333333334,
          "sharedProfile": false,
          "difference": "Connect self naming to agency without prescribing one emotional response versus Track intent, harm and response without normalizing the act; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Connect self naming to agency without prescribing one emotional response versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Connect self naming to agency without prescribing one emotional response",
        "outline": [
          "Explain the specific decision: Connect self naming to agency without prescribing one emotional response",
          "Define the applicable contract and limits for Chosen name scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Connect self naming to agency without prescribing one emotional response; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Connect self naming to agency without prescribing one emotional response",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:948",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-misunderstanding-repair-scene",
      "slug": "name-misunderstanding-repair-scene",
      "name": "Name misunderstanding repair scene",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-misunderstanding-repair-scene/",
        "ja": "/ja/tools/name-misunderstanding-repair-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Resolve a misunderstanding through established information",
      "task": "Resolve a misunderstanding through established information",
      "searchIntent": {
        "primary": "Complete the task: Resolve a misunderstanding through established information",
        "queryHypothesis": "name misunderstanding repair scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to resolve a misunderstanding through established information?",
        "When should name misunderstanding repair scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Resolve a misunderstanding through established information",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Resolve a misunderstanding through established information. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-island-community-name-collisions",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Resolve a misunderstanding through established information versus Resolve a small pool through authored relationship based references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nickname-consent-scene-exercise",
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Resolve a misunderstanding through established information versus Show acceptance and refusal through dialogue consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Resolve a misunderstanding through established information versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Resolve a misunderstanding through established information",
        "outline": [
          "Explain the specific decision: Resolve a misunderstanding through established information",
          "Define the applicable contract and limits for Name misunderstanding repair scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Resolve a misunderstanding through established information; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Resolve a misunderstanding through established information",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:949",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-inheritance-scene-exercise",
      "slug": "name-inheritance-scene-exercise",
      "name": "Name inheritance scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-inheritance-scene-exercise/",
        "ja": "/ja/tools/name-inheritance-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Contrast gratitude, obligation and resistance within a namesake decision",
      "task": "Contrast gratitude, obligation and resistance within a namesake decision",
      "searchIntent": {
        "primary": "Complete the task: Contrast gratitude, obligation and resistance within a namesake decision",
        "queryHypothesis": "name inheritance scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast gratitude, obligation and resistance within a namesake decision?",
        "When should name inheritance scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast gratitude, obligation and resistance within a namesake decision",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast gratitude, obligation and resistance within a namesake decision. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Contrast gratitude, obligation and resistance within a namesake decision versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Contrast gratitude, obligation and resistance within a namesake decision versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Contrast gratitude, obligation and resistance within a namesake decision versus Show how a remembered form reveals relationship history; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast gratitude, obligation and resistance within a namesake decision",
        "outline": [
          "Explain the specific decision: Contrast gratitude, obligation and resistance within a namesake decision",
          "Define the applicable contract and limits for Name inheritance scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast gratitude, obligation and resistance within a namesake decision; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast gratitude, obligation and resistance within a namesake decision",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:950",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-memory-scene-exercise",
      "slug": "name-memory-scene-exercise",
      "name": "Name memory scene exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-memory-scene-exercise/",
        "ja": "/ja/tools/name-memory-scene-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Show how a remembered form reveals relationship history",
      "task": "Show how a remembered form reveals relationship history",
      "searchIntent": {
        "primary": "Complete the task: Show how a remembered form reveals relationship history",
        "queryHypothesis": "name memory scene exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show how a remembered form reveals relationship history?",
        "When should name memory scene exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show how a remembered form reveals relationship history",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show how a remembered form reveals relationship history. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.2833333333333333,
          "sharedProfile": true,
          "difference": "Show how a remembered form reveals relationship history versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nickname-consent-scene-exercise",
          "score": 0.19416666666666665,
          "sharedProfile": true,
          "difference": "Show how a remembered form reveals relationship history versus Show acceptance and refusal through dialogue consequences; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Show how a remembered form reveals relationship history versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show how a remembered form reveals relationship history",
        "outline": [
          "Explain the specific decision: Show how a remembered form reveals relationship history",
          "Define the applicable contract and limits for Name memory scene exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show how a remembered form reveals relationship history; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show how a remembered form reveals relationship history",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:951",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-signature-ending-exercise",
      "slug": "signature-ending-exercise",
      "name": "Signature ending exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/signature-ending-exercise/",
        "ja": "/ja/tools/signature-ending-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Revise a final signature to reflect an established character arc",
      "task": "Revise a final signature to reflect an established character arc",
      "searchIntent": {
        "primary": "Complete the task: Revise a final signature to reflect an established character arc",
        "queryHypothesis": "signature ending exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to revise a final signature to reflect an established character arc?",
        "When should signature ending exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Revise a final signature to reflect an established character arc",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Revise a final signature to reflect an established character arc. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-ending-signature",
          "score": 0.37777777777777777,
          "sharedProfile": false,
          "difference": "Revise a final signature to reflect an established character arc versus Compare the final signature with the opening identity state; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Revise a final signature to reflect an established character arc versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-signature-consistency",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Revise a final signature to reflect an established character arc versus Keep a drawn signature recognizable across localized editions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Revise a final signature to reflect an established character arc",
        "outline": [
          "Explain the specific decision: Revise a final signature to reflect an established character arc",
          "Define the applicable contract and limits for Signature ending exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Revise a final signature to reflect an established character arc; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Revise a final signature to reflect an established character arc",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:952",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-unnamed-character-viewpoint-exercise",
      "slug": "unnamed-character-viewpoint-exercise",
      "name": "Unnamed character viewpoint exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/unnamed-character-viewpoint-exercise/",
        "ja": "/ja/tools/unnamed-character-viewpoint-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare intimacy and distance without adding a name",
      "task": "Compare intimacy and distance without adding a name",
      "searchIntent": {
        "primary": "Complete the task: Compare intimacy and distance without adding a name",
        "queryHypothesis": "unnamed character viewpoint exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare intimacy and distance without adding a name?",
        "When should unnamed character viewpoint exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare intimacy and distance without adding a name",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare intimacy and distance without adding a name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Compare intimacy and distance without adding a name versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-ritual-viewpoint",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare intimacy and distance without adding a name versus Show how participants interpret the same ceremony differently; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-audio-only-identity-introduction",
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Compare intimacy and distance without adding a name versus Introduce characters without relying on visual name cards; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare intimacy and distance without adding a name",
        "outline": [
          "Explain the specific decision: Compare intimacy and distance without adding a name",
          "Define the applicable contract and limits for Unnamed character viewpoint exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare intimacy and distance without adding a name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare intimacy and distance without adding a name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:953",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-exposition-reduction",
      "slug": "name-exposition-reduction",
      "name": "Name exposition reduction",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-exposition-reduction/",
        "ja": "/ja/tools/name-exposition-reduction/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Replace unnecessary explanation with an observable naming consequence",
      "task": "Replace unnecessary explanation with an observable naming consequence",
      "searchIntent": {
        "primary": "Complete the task: Replace unnecessary explanation with an observable naming consequence",
        "queryHypothesis": "name exposition reduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to replace unnecessary explanation with an observable naming consequence?",
        "When should name exposition reduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Replace unnecessary explanation with an observable naming consequence",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Replace unnecessary explanation with an observable naming consequence. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-story-annotation",
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Replace unnecessary explanation with an observable naming consequence versus Label each naming choice and its observable consequence in a supplied passage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-clue-revision-exercise",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Replace unnecessary explanation with an observable naming consequence versus Replace an arbitrary coincidence with an established rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-replacement",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Replace unnecessary explanation with an observable naming consequence versus Replace one established name while preserving story dependencies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Replace unnecessary explanation with an observable naming consequence",
        "outline": [
          "Explain the specific decision: Replace unnecessary explanation with an observable naming consequence",
          "Define the applicable contract and limits for Name exposition reduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Replace unnecessary explanation with an observable naming consequence; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Replace unnecessary explanation with an observable naming consequence",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:954",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-symbolism-restraint-exercise",
      "slug": "name-symbolism-restraint-exercise",
      "name": "Name symbolism restraint exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-symbolism-restraint-exercise/",
        "ja": "/ja/tools/name-symbolism-restraint-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Remove overdetermined motifs while preserving relevant story function",
      "task": "Remove overdetermined motifs while preserving relevant story function",
      "searchIntent": {
        "primary": "Complete the task: Remove overdetermined motifs while preserving relevant story function",
        "queryHypothesis": "name symbolism restraint exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to remove overdetermined motifs while preserving relevant story function?",
        "When should name symbolism restraint exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Remove overdetermined motifs while preserving relevant story function",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Remove overdetermined motifs while preserving relevant story function. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-replacement",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Remove overdetermined motifs while preserving relevant story function versus Replace one established name while preserving story dependencies; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-pun-name-tradeoff",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Remove overdetermined motifs while preserving relevant story function versus Compare sound, meaning and story function with explicit losses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-name-case-endings",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Remove overdetermined motifs while preserving relevant story function versus Build and audit explicit fictional name inflection paradigms by grammatical function while preserving the person ID and declared stem variants.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Remove overdetermined motifs while preserving relevant story function",
        "outline": [
          "Explain the specific decision: Remove overdetermined motifs while preserving relevant story function",
          "Define the applicable contract and limits for Name symbolism restraint exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Remove overdetermined motifs while preserving relevant story function; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Remove overdetermined motifs while preserving relevant story function",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:955",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-cast-rename-counterfactual",
      "slug": "cast-rename-counterfactual",
      "name": "Cast rename counterfactual",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/cast-rename-counterfactual/",
        "ja": "/ja/tools/cast-rename-counterfactual/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Trace what changes if one major name is replaced",
      "task": "Trace what changes if one major name is replaced",
      "searchIntent": {
        "primary": "Complete the task: Trace what changes if one major name is replaced",
        "queryHypothesis": "cast rename counterfactual",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace what changes if one major name is replaced?",
        "When should cast rename counterfactual be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace what changes if one major name is replaced",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace what changes if one major name is replaced. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-alias-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Trace what changes if one major name is replaced versus Test whether a mystery remains fair after a naming change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Trace what changes if one major name is replaced versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-naming-change-impact",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Trace what changes if one major name is replaced versus Trace a proposed rename across relationships and scenes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace what changes if one major name is replaced",
        "outline": [
          "Explain the specific decision: Trace what changes if one major name is replaced",
          "Define the applicable contract and limits for Cast rename counterfactual",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace what changes if one major name is replaced; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace what changes if one major name is replaced",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:956",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-family-rename-counterfactual",
      "slug": "family-rename-counterfactual",
      "name": "Family rename counterfactual",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/family-rename-counterfactual/",
        "ja": "/ja/tools/family-rename-counterfactual/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Show effects on lineage clues and relationship references",
      "task": "Show effects on lineage clues and relationship references",
      "searchIntent": {
        "primary": "Complete the task: Show effects on lineage clues and relationship references",
        "queryHypothesis": "family rename counterfactual",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show effects on lineage clues and relationship references?",
        "When should family rename counterfactual be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show effects on lineage clues and relationship references",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show effects on lineage clues and relationship references. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-scene-exercise",
          "score": 0.18818181818181817,
          "sharedProfile": true,
          "difference": "Show effects on lineage clues and relationship references versus Show a shared surname creating a specific relationship inference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Show effects on lineage clues and relationship references versus Test whether a mystery remains fair after a naming change; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-cast-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Show effects on lineage clues and relationship references versus Trace what changes if one major name is replaced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show effects on lineage clues and relationship references",
        "outline": [
          "Explain the specific decision: Show effects on lineage clues and relationship references",
          "Define the applicable contract and limits for Family rename counterfactual",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show effects on lineage clues and relationship references; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show effects on lineage clues and relationship references",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:957",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-alias-rename-counterfactual",
      "slug": "alias-rename-counterfactual",
      "name": "Alias rename counterfactual",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/alias-rename-counterfactual/",
        "ja": "/ja/tools/alias-rename-counterfactual/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Test whether a mystery remains fair after a naming change",
      "task": "Test whether a mystery remains fair after a naming change",
      "searchIntent": {
        "primary": "Complete the task: Test whether a mystery remains fair after a naming change",
        "queryHypothesis": "alias rename counterfactual",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test whether a mystery remains fair after a naming change?",
        "When should alias rename counterfactual be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test whether a mystery remains fair after a naming change",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test whether a mystery remains fair after a naming change. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-cast-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Test whether a mystery remains fair after a naming change versus Trace what changes if one major name is replaced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-rename-counterfactual",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Test whether a mystery remains fair after a naming change versus Show effects on lineage clues and relationship references; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-reveal-comprehension",
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Test whether a mystery remains fair after a naming change versus Test whether readers understand an identity connection at the intended moment; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test whether a mystery remains fair after a naming change",
        "outline": [
          "Explain the specific decision: Test whether a mystery remains fair after a naming change",
          "Define the applicable contract and limits for Alias rename counterfactual",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test whether a mystery remains fair after a naming change; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test whether a mystery remains fair after a naming change",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:958",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-pen-name-positioning-exercise",
      "slug": "pen-name-positioning-exercise",
      "name": "Pen name positioning exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/pen-name-positioning-exercise/",
        "ja": "/ja/tools/pen-name-positioning-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare byline presentations using a declared audience brief",
      "task": "Compare byline presentations using a declared audience brief",
      "searchIntent": {
        "primary": "Complete the task: Compare byline presentations using a declared audience brief",
        "queryHypothesis": "pen name positioning exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare byline presentations using a declared audience brief?",
        "When should pen name positioning exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare byline presentations using a declared audience brief",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare byline presentations using a declared audience brief. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-genre-positioning",
          "score": 0.22916666666666666,
          "sharedProfile": false,
          "difference": "Compare byline presentations using a declared audience brief versus Compare intended shelf signals without guaranteeing audience response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-designer",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Compare byline presentations using a declared audience brief versus Match an author brief to readable signature candidates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-candidate-decision",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Compare byline presentations using a declared audience brief versus Compare a fixed shortlist using published heuristic criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare byline presentations using a declared audience brief",
        "outline": [
          "Explain the specific decision: Compare byline presentations using a declared audience brief",
          "Define the applicable contract and limits for Pen name positioning exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare byline presentations using a declared audience brief; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare byline presentations using a declared audience brief",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:959",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-world-naming-consistency-exercise",
      "slug": "world-naming-consistency-exercise",
      "name": "World naming consistency exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/world-naming-consistency-exercise/",
        "ja": "/ja/tools/world-naming-consistency-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Repair a deliberately inconsistent fictional mini corpus",
      "task": "Repair a deliberately inconsistent fictional mini corpus",
      "searchIntent": {
        "primary": "Complete the task: Repair a deliberately inconsistent fictional mini corpus",
        "queryHypothesis": "world naming consistency exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to repair a deliberately inconsistent fictional mini corpus?",
        "When should world naming consistency exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Repair a deliberately inconsistent fictional mini corpus",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Repair a deliberately inconsistent fictional mini corpus. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-invented-name-corpus-consistency",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Repair a deliberately inconsistent fictional mini corpus versus Check a supplied corpus against authored grammar rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-name-tradeoff-exercise",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Repair a deliberately inconsistent fictional mini corpus versus Explain what a localization preserves and loses; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-chosen-name-scene-exercise",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Repair a deliberately inconsistent fictional mini corpus versus Connect self naming to agency without prescribing one emotional response; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Repair a deliberately inconsistent fictional mini corpus",
        "outline": [
          "Explain the specific decision: Repair a deliberately inconsistent fictional mini corpus",
          "Define the applicable contract and limits for World naming consistency exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Repair a deliberately inconsistent fictional mini corpus; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Repair a deliberately inconsistent fictional mini corpus",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:960",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-bilingual-name-tradeoff-exercise",
      "slug": "bilingual-name-tradeoff-exercise",
      "name": "Bilingual name tradeoff exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/bilingual-name-tradeoff-exercise/",
        "ja": "/ja/tools/bilingual-name-tradeoff-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Explain what a localization preserves and loses",
      "task": "Explain what a localization preserves and loses",
      "searchIntent": {
        "primary": "Complete the task: Explain what a localization preserves and loses",
        "queryHypothesis": "bilingual name tradeoff exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain what a localization preserves and loses?",
        "When should bilingual name tradeoff exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain what a localization preserves and loses",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain what a localization preserves and loses. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-theft-magic-contract",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Explain what a localization preserves and loses versus Model who loses what when an invented name is stolen; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-story-naming-exception",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Explain what a localization preserves and loses versus Explain an intentional departure in an editorial note; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-numerical-name-grammar",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Explain what a localization preserves and loses versus Explain how sequence and individuality coexist in names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain what a localization preserves and loses",
        "outline": [
          "Explain the specific decision: Explain what a localization preserves and loses",
          "Define the applicable contract and limits for Bilingual name tradeoff exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain what a localization preserves and loses; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain what a localization preserves and loses",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:961",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-based-conflict-outline",
      "slug": "name-based-conflict-outline",
      "name": "Name based conflict outline",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-based-conflict-outline/",
        "ja": "/ja/tools/name-based-conflict-outline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Build a conflict from specific naming authority and character stakes",
      "task": "Build a conflict from specific naming authority and character stakes",
      "searchIntent": {
        "primary": "Complete the task: Build a conflict from specific naming authority and character stakes",
        "queryHypothesis": "name based conflict outline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to build a conflict from specific naming authority and character stakes?",
        "When should name based conflict outline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Build a conflict from specific naming authority and character stakes",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Build a conflict from specific naming authority and character stakes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Build a conflict from specific naming authority and character stakes versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-identity-growth-outline",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Build a conflict from specific naming authority and character stakes versus Link name choices to concrete decisions over an arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-stolen-family-name-motive",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Build a conflict from specific naming authority and character stakes versus Connect naming conflict to character stakes rather than a puzzle alone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Build a conflict from specific naming authority and character stakes",
        "outline": [
          "Explain the specific decision: Build a conflict from specific naming authority and character stakes",
          "Define the applicable contract and limits for Name based conflict outline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Build a conflict from specific naming authority and character stakes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Build a conflict from specific naming authority and character stakes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:962",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-based-reconciliation-outline",
      "slug": "name-based-reconciliation-outline",
      "name": "Name based reconciliation outline",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-based-reconciliation-outline/",
        "ja": "/ja/tools/name-based-reconciliation-outline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Require behavior as well as a changed form of address",
      "task": "Require behavior as well as a changed form of address",
      "searchIntent": {
        "primary": "Complete the task: Require behavior as well as a changed form of address",
        "queryHypothesis": "name based reconciliation outline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to require behavior as well as a changed form of address?",
        "When should name based reconciliation outline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Require behavior as well as a changed form of address",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Require behavior as well as a changed form of address. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-reconciliation-name-return",
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Require behavior as well as a changed form of address versus Make the return of a form of address legible; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-conflict-outline",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Require behavior as well as a changed form of address versus Build a conflict from specific naming authority and character stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-identity-growth-outline",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Require behavior as well as a changed form of address versus Link name choices to concrete decisions over an arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Require behavior as well as a changed form of address",
        "outline": [
          "Explain the specific decision: Require behavior as well as a changed form of address",
          "Define the applicable contract and limits for Name based reconciliation outline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Require behavior as well as a changed form of address; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Require behavior as well as a changed form of address",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:963",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-based-social-status-scene",
      "slug": "name-based-social-status-scene",
      "name": "Name based social status scene",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-based-social-status-scene/",
        "ja": "/ja/tools/name-based-social-status-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Show a fictional hierarchy through who may use which form",
      "task": "Show a fictional hierarchy through who may use which form",
      "searchIntent": {
        "primary": "Complete the task: Show a fictional hierarchy through who may use which form",
        "queryHypothesis": "name based social status scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show a fictional hierarchy through who may use which form?",
        "When should name based social status scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show a fictional hierarchy through who may use which form",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show a fictional hierarchy through who may use which form. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-consent-map",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Show a fictional hierarchy through who may use which form versus Record who may use a chosen, former or intimate name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sacred-name-avoidance",
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Show a fictional hierarchy through who may use which form versus Define who may speak which name in which context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-nickname-relationship",
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Show a fictional hierarchy through who may use which form versus Preserve who may use each nickname across languages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show a fictional hierarchy through who may use which form",
        "outline": [
          "Explain the specific decision: Show a fictional hierarchy through who may use which form",
          "Define the applicable contract and limits for Name based social status scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show a fictional hierarchy through who may use which form; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show a fictional hierarchy through who may use which form",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:964",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-based-identity-growth-outline",
      "slug": "name-based-identity-growth-outline",
      "name": "Name based identity growth outline",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-based-identity-growth-outline/",
        "ja": "/ja/tools/name-based-identity-growth-outline/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Link name choices to concrete decisions over an arc",
      "task": "Link name choices to concrete decisions over an arc",
      "searchIntent": {
        "primary": "Complete the task: Link name choices to concrete decisions over an arc",
        "queryHypothesis": "name based identity growth outline",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to link name choices to concrete decisions over an arc?",
        "When should name based identity growth outline be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Link name choices to concrete decisions over an arc",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Link name choices to concrete decisions over an arc. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-conflict-outline",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Link name choices to concrete decisions over an arc versus Build a conflict from specific naming authority and character stakes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-based-reconciliation-outline",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Link name choices to concrete decisions over an arc versus Require behavior as well as a changed form of address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-in-farewell-dialogue",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Link name choices to concrete decisions over an arc versus Compare last address choices against the relationship arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Link name choices to concrete decisions over an arc",
        "outline": [
          "Explain the specific decision: Link name choices to concrete decisions over an arc",
          "Define the applicable contract and limits for Name based identity growth outline",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Link name choices to concrete decisions over an arc; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Link name choices to concrete decisions over an arc",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:965",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-based-belonging-scene",
      "slug": "name-based-belonging-scene",
      "name": "Name based belonging scene",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-based-belonging-scene/",
        "ja": "/ja/tools/name-based-belonging-scene/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare inclusion and coercion in a group naming ritual",
      "task": "Compare inclusion and coercion in a group naming ritual",
      "searchIntent": {
        "primary": "Complete the task: Compare inclusion and coercion in a group naming ritual",
        "queryHypothesis": "name based belonging scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare inclusion and coercion in a group naming ritual?",
        "When should name based belonging scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare inclusion and coercion in a group naming ritual",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare inclusion and coercion in a group naming ritual. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-based-social-status-scene",
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Compare inclusion and coercion in a group naming ritual versus Show a fictional hierarchy through who may use which form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-magic-school-house-identity",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Compare inclusion and coercion in a group naming ritual versus Separate group affiliation from personal and family names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-in-confession-scene",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Compare inclusion and coercion in a group naming ritual versus Control who is identified by an emotionally loaded address; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare inclusion and coercion in a group naming ritual",
        "outline": [
          "Explain the specific decision: Compare inclusion and coercion in a group naming ritual",
          "Define the applicable contract and limits for Name based belonging scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare inclusion and coercion in a group naming ritual; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare inclusion and coercion in a group naming ritual",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:966",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-clue-revision-exercise",
      "slug": "name-clue-revision-exercise",
      "name": "Name clue revision exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-clue-revision-exercise/",
        "ja": "/ja/tools/name-clue-revision-exercise/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Replace an arbitrary coincidence with an established rule",
      "task": "Replace an arbitrary coincidence with an established rule",
      "searchIntent": {
        "primary": "Complete the task: Replace an arbitrary coincidence with an established rule",
        "queryHypothesis": "name clue revision exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to replace an arbitrary coincidence with an established rule?",
        "When should name clue revision exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Replace an arbitrary coincidence with an established rule",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Replace an arbitrary coincidence with an established rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-miswritten-clue",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Replace an arbitrary coincidence with an established rule versus Separate plausible graphic confusion from arbitrary substitutions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-wrong-honorific-clue",
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Replace an arbitrary coincidence with an established rule versus Ground the clue in an established in story convention; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-signature-ending-exercise",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Replace an arbitrary coincidence with an established rule versus Revise a final signature to reflect an established character arc; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Replace an arbitrary coincidence with an established rule",
        "outline": [
          "Explain the specific decision: Replace an arbitrary coincidence with an established rule",
          "Define the applicable contract and limits for Name clue revision exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Replace an arbitrary coincidence with an established rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Replace an arbitrary coincidence with an established rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:967",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-name-story-annotation",
      "slug": "name-story-annotation",
      "name": "Name story annotation",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/name-story-annotation/",
        "ja": "/ja/tools/name-story-annotation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Label each naming choice and its observable consequence in a supplied passage",
      "task": "Label each naming choice and its observable consequence in a supplied passage",
      "searchIntent": {
        "primary": "Complete the task: Label each naming choice and its observable consequence in a supplied passage",
        "queryHypothesis": "name story annotation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to label each naming choice and its observable consequence in a supplied passage?",
        "When should name story annotation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Label each naming choice and its observable consequence in a supplied passage",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Label each naming choice and its observable consequence in a supplied passage. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-fact-annotation",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Label each naming choice and its observable consequence in a supplied passage versus Label attestation, inference and invention at claim level; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-story-editorial-critique",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Label each naming choice and its observable consequence in a supplied passage versus Check whether an original example actually demonstrates its naming method; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-merchant-family-trade-names",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Label each naming choice and its observable consequence in a supplied passage versus Separate a business label from each household member; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Label each naming choice and its observable consequence in a supplied passage",
        "outline": [
          "Explain the specific decision: Label each naming choice and its observable consequence in a supplied passage",
          "Define the applicable contract and limits for Name story annotation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Label each naming choice and its observable consequence in a supplied passage; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Label each naming choice and its observable consequence in a supplied passage",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:968",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-naming-craft-comparison",
      "slug": "naming-craft-comparison",
      "name": "Naming craft comparison",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/naming-craft-comparison/",
        "ja": "/ja/tools/naming-craft-comparison/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Compare two approaches using the same story constraints",
      "task": "Compare two approaches using the same story constraints",
      "searchIntent": {
        "primary": "Complete the task: Compare two approaches using the same story constraints",
        "queryHypothesis": "naming craft comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare two approaches using the same story constraints?",
        "When should naming craft comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare two approaches using the same story constraints",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare two approaches using the same story constraints. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-corpus-comparison",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Compare two approaches using the same story constraints versus Measure overlap between two supplied resources with transparent normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-culture-naming-contrast",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Compare two approaches using the same story constraints versus Compare two invented cultures using explicit structural rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-accessibility-comparison",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Compare two approaches using the same story constraints versus Record participant specific difficulties without generalizing to a diagnosis; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare two approaches using the same story constraints",
        "outline": [
          "Explain the specific decision: Compare two approaches using the same story constraints",
          "Define the applicable contract and limits for Naming craft comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare two approaches using the same story constraints; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare two approaches using the same story constraints",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:969",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-naming-story-editorial-critique",
      "slug": "naming-story-editorial-critique",
      "name": "Naming story editorial critique",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/naming-story-editorial-critique/",
        "ja": "/ja/tools/naming-story-editorial-critique/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Check whether an original example actually demonstrates its naming method",
      "task": "Check whether an original example actually demonstrates its naming method",
      "searchIntent": {
        "primary": "Complete the task: Check whether an original example actually demonstrates its naming method",
        "queryHypothesis": "naming story editorial critique",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to check whether an original example actually demonstrates its naming method?",
        "When should naming story editorial critique be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Check whether an original example actually demonstrates its naming method",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Check whether an original example actually demonstrates its naming method. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-story-annotation",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Check whether an original example actually demonstrates its naming method versus Label each naming choice and its observable consequence in a supplied passage; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-bilingual-cast-collision-audit",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Check whether an original example actually demonstrates its naming method versus Check whether distinct source names merge in the target language; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-story-naming-exception",
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Check whether an original example actually demonstrates its naming method versus Explain an intentional departure in an editorial note; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Check whether an original example actually demonstrates its naming method",
        "outline": [
          "Explain the specific decision: Check whether an original example actually demonstrates its naming method",
          "Define the applicable contract and limits for Naming story editorial critique",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Check whether an original example actually demonstrates its naming method; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Check whether an original example actually demonstrates its naming method",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:971",
      "profileSource": "data/profiles.json#editorial-content"
    },
    {
      "id": "nw-personal-name-dataset-intake",
      "slug": "personal-name-dataset-intake",
      "name": "Personal name dataset intake",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/personal-name-dataset-intake/",
        "ja": "/ja/tools/personal-name-dataset-intake/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Validate provenance, permitted use and structural fields before import",
      "task": "Validate provenance, permitted use and structural fields before import",
      "searchIntent": {
        "primary": "Complete the task: Validate provenance, permitted use and structural fields before import",
        "queryHypothesis": "personal name dataset intake",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to validate provenance, permitted use and structural fields before import?",
        "When should personal name dataset intake be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Validate provenance, permitted use and structural fields before import",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Validate provenance, permitted use and structural fields before import. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-census-candidate-extraction",
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Validate provenance, permitted use and structural fields before import versus Log provenance and license before importing name data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-academic-fictional-honorific",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Validate provenance, permitted use and structural fields before import versus Separate a fictional qualification from personal name fields; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.0590909090909091,
          "sharedProfile": false,
          "difference": "Validate provenance, permitted use and structural fields before import versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Validate provenance, permitted use and structural fields before import",
        "outline": [
          "Explain the specific decision: Validate provenance, permitted use and structural fields before import",
          "Define the applicable contract and limits for Personal name dataset intake",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Validate provenance, permitted use and structural fields before import; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Validate provenance, permitted use and structural fields before import",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:974",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-source-license-ledger",
      "slug": "name-source-license-ledger",
      "name": "Name source license ledger",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-source-license-ledger/",
        "ja": "/ja/tools/name-source-license-ledger/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Track dataset versions and redistribution conditions",
      "task": "Track dataset versions and redistribution conditions",
      "searchIntent": {
        "primary": "Complete the task: Track dataset versions and redistribution conditions",
        "queryHypothesis": "name source license ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track dataset versions and redistribution conditions?",
        "When should name source license ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track dataset versions and redistribution conditions",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track dataset versions and redistribution conditions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Track dataset versions and redistribution conditions versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-comic-masked-speaker-labels",
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Track dataset versions and redistribution conditions versus Preserve concealed identity in production and reader facing versions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.07222222222222222,
          "sharedProfile": true,
          "difference": "Track dataset versions and redistribution conditions versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track dataset versions and redistribution conditions",
        "outline": [
          "Explain the specific decision: Track dataset versions and redistribution conditions",
          "Define the applicable contract and limits for Name source license ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track dataset versions and redistribution conditions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track dataset versions and redistribution conditions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:975",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-claim-evidence-mapping",
      "slug": "name-claim-evidence-mapping",
      "name": "Name claim evidence mapping",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-claim-evidence-mapping/",
        "ja": "/ja/tools/name-claim-evidence-mapping/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Attach sources to individual readings, meanings and cultural claims",
      "task": "Attach sources to individual readings, meanings and cultural claims",
      "searchIntent": {
        "primary": "Complete the task: Attach sources to individual readings, meanings and cultural claims",
        "queryHypothesis": "name claim evidence mapping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to attach sources to individual readings, meanings and cultural claims?",
        "When should name claim evidence mapping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Record attestation, inference and invention independently",
        "Separate narrative associations from externally supported claims"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Attach sources to individual readings, meanings and cultural claims",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons",
        "Claim-level evidence table",
        "Typed creative notes"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Attach sources to individual readings, meanings and cultural claims. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "score": 0.2175,
          "sharedProfile": false,
          "difference": "Attach sources to individual readings, meanings and cultural claims versus Separate verified cultural claims from author associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Attach sources to individual readings, meanings and cultural claims versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Attach sources to individual readings, meanings and cultural claims versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Attach sources to individual readings, meanings and cultural claims",
        "outline": [
          "Explain the specific decision: Attach sources to individual readings, meanings and cultural claims",
          "Define the applicable contract and limits for Name claim evidence mapping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Attach sources to individual readings, meanings and cultural claims; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Attach sources to individual readings, meanings and cultural claims",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "One attested reading does not attest every spelling combination",
        "Creative note cannot pass fact-source validation"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:976",
      "profileSource": "data/profiles.json#data-methods",
      "absorbedModules": [
        {
          "sourceId": "nw-name-data-attestation-levels",
          "input": "evidenceStatus",
          "rule": "Record attestation, inference and invention independently",
          "output": "Claim-level evidence table",
          "acceptance": "One attested reading does not attest every spelling combination",
          "status": "design-integrated-not-implemented"
        },
        {
          "sourceId": "nw-name-data-creative-interpretation",
          "input": "creativeNotes",
          "rule": "Separate narrative associations from externally supported claims",
          "output": "Typed creative notes",
          "acceptance": "Creative note cannot pass fact-source validation",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-name-data-reading-uncertainty",
      "slug": "name-data-reading-uncertainty",
      "name": "Name data reading uncertainty",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-reading-uncertainty/",
        "ja": "/ja/tools/name-data-reading-uncertainty/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Preserve multiple readings with source specific confidence notes",
      "task": "Preserve multiple readings with source specific confidence notes",
      "searchIntent": {
        "primary": "Complete the task: Preserve multiple readings with source specific confidence notes",
        "queryHypothesis": "name data reading uncertainty",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve multiple readings with source specific confidence notes?",
        "When should name data reading uncertainty be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve multiple readings with source specific confidence notes",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve multiple readings with source specific confidence notes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-archive-name-uncertainty",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Preserve multiple readings with source specific confidence notes versus Store competing readings and confidence with source images; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-glyph-fidelity",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve multiple readings with source specific confidence notes versus Preserve source glyphs separately from search normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Preserve multiple readings with source specific confidence notes versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve multiple readings with source specific confidence notes",
        "outline": [
          "Explain the specific decision: Preserve multiple readings with source specific confidence notes",
          "Define the applicable contract and limits for Name data reading uncertainty",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve multiple readings with source specific confidence notes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve multiple readings with source specific confidence notes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:978",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-identity-ambiguity",
      "slug": "name-data-identity-ambiguity",
      "name": "Name data identity ambiguity",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-identity-ambiguity/",
        "ja": "/ja/tools/name-data-identity-ambiguity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Avoid merging different people solely because names match",
      "task": "Avoid merging different people solely because names match",
      "searchIntent": {
        "primary": "Complete the task: Avoid merging different people solely because names match",
        "queryHypothesis": "name data identity ambiguity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to avoid merging different people solely because names match?",
        "When should name data identity ambiguity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Avoid merging different people solely because names match",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Avoid merging different people solely because names match. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-exiled-ruler-identity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Avoid merging different people solely because names match versus Track titles claimed, rejected and recognized by different factions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-inherited-mantle-identity",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Avoid merging different people solely because names match versus Track successive people using one hero title; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-geographic-scope",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Avoid merging different people solely because names match versus Record coverage and avoid projecting a sample across a culture; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Avoid merging different people solely because names match",
        "outline": [
          "Explain the specific decision: Avoid merging different people solely because names match",
          "Define the applicable contract and limits for Name data identity ambiguity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Avoid merging different people solely because names match; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Avoid merging different people solely because names match",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:980",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-geographic-scope",
      "slug": "name-data-geographic-scope",
      "name": "Name data geographic scope",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-geographic-scope/",
        "ja": "/ja/tools/name-data-geographic-scope/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Record coverage and avoid projecting a sample across a culture",
      "task": "Record coverage and avoid projecting a sample across a culture",
      "searchIntent": {
        "primary": "Complete the task: Record coverage and avoid projecting a sample across a culture",
        "queryHypothesis": "name data geographic scope",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record coverage and avoid projecting a sample across a culture?",
        "When should name data geographic scope be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record coverage and avoid projecting a sample across a culture",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record coverage and avoid projecting a sample across a culture. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-identity-ambiguity",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Record coverage and avoid projecting a sample across a culture versus Avoid merging different people solely because names match; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-marriage-name-research",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Record coverage and avoid projecting a sample across a culture versus Avoid projecting current naming conventions onto past settings; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-data-version-pin",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Record coverage and avoid projecting a sample across a culture versus Make save generated names reproducible across data updates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record coverage and avoid projecting a sample across a culture",
        "outline": [
          "Explain the specific decision: Record coverage and avoid projecting a sample across a culture",
          "Define the applicable contract and limits for Name data geographic scope",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record coverage and avoid projecting a sample across a culture; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record coverage and avoid projecting a sample across a culture",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:981",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-time-coverage",
      "slug": "name-data-time-coverage",
      "name": "Name data time coverage",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-time-coverage/",
        "ja": "/ja/tools/name-data-time-coverage/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Track source dates and prohibit unsupported era filtering",
      "task": "Track source dates and prohibit unsupported era filtering",
      "searchIntent": {
        "primary": "Complete the task: Track source dates and prohibit unsupported era filtering",
        "queryHypothesis": "name data time coverage",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track source dates and prohibit unsupported era filtering?",
        "When should name data time coverage be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track source dates and prohibit unsupported era filtering",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track source dates and prohibit unsupported era filtering. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-glyph-fidelity",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Track source dates and prohibit unsupported era filtering versus Preserve source glyphs separately from search normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-reading-uncertainty",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Track source dates and prohibit unsupported era filtering versus Preserve multiple readings with source specific confidence notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-time-traveler-cover-names",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Track source dates and prohibit unsupported era filtering versus Check alias references against story dates and social context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track source dates and prohibit unsupported era filtering",
        "outline": [
          "Explain the specific decision: Track source dates and prohibit unsupported era filtering",
          "Define the applicable contract and limits for Name data time coverage",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track source dates and prohibit unsupported era filtering; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track source dates and prohibit unsupported era filtering",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:982",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-cohort-bias",
      "slug": "name-data-cohort-bias",
      "name": "Name data cohort bias",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-cohort-bias/",
        "ja": "/ja/tools/name-data-cohort-bias/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Explain which populations are absent from a supplied dataset",
      "task": "Explain which populations are absent from a supplied dataset",
      "searchIntent": {
        "primary": "Complete the task: Explain which populations are absent from a supplied dataset",
        "queryHypothesis": "name data cohort bias",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain which populations are absent from a supplied dataset?",
        "When should name data cohort bias be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain which populations are absent from a supplied dataset",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain which populations are absent from a supplied dataset. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-frequency-caveat",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Explain which populations are absent from a supplied dataset versus Explain archive bias and missing populations in supplied data; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-character-name-ambiguity-budget",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Explain which populations are absent from a supplied dataset versus Decide which confusions are intentional and which need repair; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-generation-audit-trail",
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Explain which populations are absent from a supplied dataset versus Export which entries and rules produced a candidate; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain which populations are absent from a supplied dataset",
        "outline": [
          "Explain the specific decision: Explain which populations are absent from a supplied dataset",
          "Define the applicable contract and limits for Name data cohort bias",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain which populations are absent from a supplied dataset; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain which populations are absent from a supplied dataset",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:983",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-exclusion-governance",
      "slug": "name-data-exclusion-governance",
      "name": "Name data exclusion governance",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-exclusion-governance/",
        "ja": "/ja/tools/name-data-exclusion-governance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Record who excluded a token and why without universalizing taste",
      "task": "Record who excluded a token and why without universalizing taste",
      "searchIntent": {
        "primary": "Complete the task: Record who excluded a token and why without universalizing taste",
        "queryHypothesis": "name data exclusion governance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record who excluded a token and why without universalizing taste?",
        "When should name data exclusion governance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record who excluded a token and why without universalizing taste",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record who excluded a token and why without universalizing taste. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-evidence-completeness",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Record who excluded a token and why without universalizing taste versus Report missing claim level evidence without inventing sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-public-figure-collision",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Record who excluded a token and why without universalizing taste versus Structure external checks without claiming uniqueness or clearance; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Record who excluded a token and why without universalizing taste versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record who excluded a token and why without universalizing taste",
        "outline": [
          "Explain the specific decision: Record who excluded a token and why without universalizing taste",
          "Define the applicable contract and limits for Name data exclusion governance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record who excluded a token and why without universalizing taste; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record who excluded a token and why without universalizing taste",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:985",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-offensive-association-review",
      "slug": "name-data-offensive-association-review",
      "name": "Name data offensive association review",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-offensive-association-review/",
        "ja": "/ja/tools/name-data-offensive-association-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Route context dependent issues to human review",
      "task": "Route context dependent issues to human review",
      "searchIntent": {
        "primary": "Complete the task: Route context dependent issues to human review",
        "queryHypothesis": "name data offensive association review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to route context dependent issues to human review?",
        "When should name data offensive association review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Route context dependent issues to human review",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Route context dependent issues to human review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-negative-association-review",
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Route context dependent issues to human review versus Structure human checks for unintended associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cultural-reviewer-queue",
          "score": 0.18,
          "sharedProfile": true,
          "difference": "Route context dependent issues to human review versus Package uncertain claims for named human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-naming-sensitivity-review",
          "score": 0.1765151515151515,
          "sharedProfile": false,
          "difference": "Route context dependent issues to human review versus Require context and native language review for cultural claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Route context dependent issues to human review",
        "outline": [
          "Explain the specific decision: Route context dependent issues to human review",
          "Define the applicable contract and limits for Name data offensive association review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Route context dependent issues to human review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Route context dependent issues to human review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:986",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-pronunciation-provenance",
      "slug": "name-data-pronunciation-provenance",
      "name": "Name data pronunciation provenance",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-pronunciation-provenance/",
        "ja": "/ja/tools/name-data-pronunciation-provenance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Attach approved audio or reading evidence to each entry",
      "task": "Attach approved audio or reading evidence to each entry",
      "searchIntent": {
        "primary": "Complete the task: Attach approved audio or reading evidence to each entry",
        "queryHypothesis": "name data pronunciation provenance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to attach approved audio or reading evidence to each entry?",
        "When should name data pronunciation provenance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Attach approved audio or reading evidence to each entry",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Attach approved audio or reading evidence to each entry. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-given-name-reading-choice",
          "score": 0.37142857142857144,
          "sharedProfile": false,
          "difference": "Attach approved audio or reading evidence to each entry versus Attach evidence to each candidate reading; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-transliteration-provenance",
          "score": 0.24,
          "sharedProfile": true,
          "difference": "Attach approved audio or reading evidence to each entry versus Record the system and manual exceptions for each form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-example-provenance",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Attach approved audio or reading evidence to each entry versus Mark static examples as authored, generated or externally sourced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Attach approved audio or reading evidence to each entry",
        "outline": [
          "Explain the specific decision: Attach approved audio or reading evidence to each entry",
          "Define the applicable contract and limits for Name data pronunciation provenance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Attach approved audio or reading evidence to each entry; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Attach approved audio or reading evidence to each entry",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:987",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-transliteration-provenance",
      "slug": "name-data-transliteration-provenance",
      "name": "Name data transliteration provenance",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-transliteration-provenance/",
        "ja": "/ja/tools/name-data-transliteration-provenance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Record the system and manual exceptions for each form",
      "task": "Record the system and manual exceptions for each form",
      "searchIntent": {
        "primary": "Complete the task: Record the system and manual exceptions for each form",
        "queryHypothesis": "name data transliteration provenance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record the system and manual exceptions for each form?",
        "When should name data transliteration provenance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record the system and manual exceptions for each form",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record the system and manual exceptions for each form. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-pronunciation-provenance",
          "score": 0.24,
          "sharedProfile": true,
          "difference": "Record the system and manual exceptions for each form versus Attach approved audio or reading evidence to each entry; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-example-provenance",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Record the system and manual exceptions for each form versus Mark static examples as authored, generated or externally sourced; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-transliteration-decision-log",
          "score": 0.1025,
          "sharedProfile": false,
          "difference": "Record the system and manual exceptions for each form versus Encode or decode names in an authored variable-length symbol system, expose alternative parses and prove exact round-trip behavior for displayed outputs.; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record the system and manual exceptions for each form",
        "outline": [
          "Explain the specific decision: Record the system and manual exceptions for each form",
          "Define the applicable contract and limits for Name data transliteration provenance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record the system and manual exceptions for each form; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record the system and manual exceptions for each form",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:988",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-glyph-fidelity",
      "slug": "name-data-glyph-fidelity",
      "name": "Name data glyph fidelity",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-glyph-fidelity/",
        "ja": "/ja/tools/name-data-glyph-fidelity/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Preserve source glyphs separately from search normalization",
      "task": "Preserve source glyphs separately from search normalization",
      "searchIntent": {
        "primary": "Complete the task: Preserve source glyphs separately from search normalization",
        "queryHypothesis": "name data glyph fidelity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve source glyphs separately from search normalization?",
        "When should name data glyph fidelity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve source glyphs separately from search normalization",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve source glyphs separately from search normalization. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-obsolete-glyph-handling",
          "score": 0.13958333333333334,
          "sharedProfile": false,
          "difference": "Preserve source glyphs separately from search normalization versus Preserve original and readable fallback separately; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-reading-uncertainty",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve source glyphs separately from search normalization versus Preserve multiple readings with source specific confidence notes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-time-coverage",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Preserve source glyphs separately from search normalization versus Track source dates and prohibit unsupported era filtering; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve source glyphs separately from search normalization",
        "outline": [
          "Explain the specific decision: Preserve source glyphs separately from search normalization",
          "Define the applicable contract and limits for Name data glyph fidelity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve source glyphs separately from search normalization; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve source glyphs separately from search normalization",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:989",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-public-figure-collision",
      "slug": "name-data-public-figure-collision",
      "name": "Name data public figure collision",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-public-figure-collision/",
        "ja": "/ja/tools/name-data-public-figure-collision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Structure external checks without claiming uniqueness or clearance",
      "task": "Structure external checks without claiming uniqueness or clearance",
      "searchIntent": {
        "primary": "Complete the task: Structure external checks without claiming uniqueness or clearance",
        "queryHypothesis": "name data public figure collision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to structure external checks without claiming uniqueness or clearance?",
        "When should name data public figure collision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Structure external checks without claiming uniqueness or clearance",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Structure external checks without claiming uniqueness or clearance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-search-collision-log",
          "score": 0.33888888888888885,
          "sharedProfile": false,
          "difference": "Structure external checks without claiming uniqueness or clearance versus Record dated external checks without claiming exclusivity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "score": 0.28888888888888886,
          "sharedProfile": false,
          "difference": "Structure external checks without claiming uniqueness or clearance versus Record the scope of external checks without clearance claims; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-pen-name-negative-association-review",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Structure external checks without claiming uniqueness or clearance versus Structure human checks for unintended associations; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Structure external checks without claiming uniqueness or clearance",
        "outline": [
          "Explain the specific decision: Structure external checks without claiming uniqueness or clearance",
          "Define the applicable contract and limits for Name data public figure collision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Structure external checks without claiming uniqueness or clearance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Structure external checks without claiming uniqueness or clearance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:990",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-corpus-comparison",
      "slug": "name-data-corpus-comparison",
      "name": "Name data corpus comparison",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-corpus-comparison/",
        "ja": "/ja/tools/name-data-corpus-comparison/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Measure overlap between two supplied resources with transparent normalization",
      "task": "Measure overlap between two supplied resources with transparent normalization",
      "searchIntent": {
        "primary": "Complete the task: Measure overlap between two supplied resources with transparent normalization",
        "queryHypothesis": "name data corpus comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to measure overlap between two supplied resources with transparent normalization?",
        "When should name data corpus comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Measure overlap between two supplied resources with transparent normalization",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Measure overlap between two supplied resources with transparent normalization. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-craft-comparison",
          "score": 0.14166666666666666,
          "sharedProfile": false,
          "difference": "Measure overlap between two supplied resources with transparent normalization versus Compare two approaches using the same story constraints; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-glyph-fidelity",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Measure overlap between two supplied resources with transparent normalization versus Preserve source glyphs separately from search normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-accessibility-comparison",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Measure overlap between two supplied resources with transparent normalization versus Record participant specific difficulties without generalizing to a diagnosis; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Measure overlap between two supplied resources with transparent normalization",
        "outline": [
          "Explain the specific decision: Measure overlap between two supplied resources with transparent normalization",
          "Define the applicable contract and limits for Name data corpus comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Measure overlap between two supplied resources with transparent normalization; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Measure overlap between two supplied resources with transparent normalization",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:991",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-generation-audit-trail",
      "slug": "name-data-generation-audit-trail",
      "name": "Name data generation audit trail",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-generation-audit-trail/",
        "ja": "/ja/tools/name-data-generation-audit-trail/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Export which entries and rules produced a candidate",
      "task": "Export which entries and rules produced a candidate",
      "searchIntent": {
        "primary": "Complete the task: Export which entries and rules produced a candidate",
        "queryHypothesis": "name data generation audit trail",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export which entries and rules produced a candidate?",
        "When should name data generation audit trail be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export which entries and rules produced a candidate",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export which entries and rules produced a candidate. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Export which entries and rules produced a candidate versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-setting-name-rule-exception-map",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Export which entries and rules produced a candidate versus Identify which characters violate local rules and why; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-naming-bible",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Export which entries and rules produced a candidate versus Export people, naming rules and exception decisions as one reference; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export which entries and rules produced a candidate",
        "outline": [
          "Explain the specific decision: Export which entries and rules produced a candidate",
          "Define the applicable contract and limits for Name data generation audit trail",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export which entries and rules produced a candidate; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export which entries and rules produced a candidate",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:992",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-reproducibility-bundle",
      "slug": "name-data-reproducibility-bundle",
      "name": "Name data reproducibility bundle",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-reproducibility-bundle/",
        "ja": "/ja/tools/name-data-reproducibility-bundle/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Pin corpus, rule and seed versions for later regeneration",
      "task": "Pin corpus, rule and seed versions for later regeneration",
      "searchIntent": {
        "primary": "Complete the task: Pin corpus, rule and seed versions for later regeneration",
        "queryHypothesis": "name data reproducibility bundle",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to pin corpus, rule and seed versions for later regeneration?",
        "When should name data reproducibility bundle be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Pin corpus, rule and seed versions for later regeneration",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Pin corpus, rule and seed versions for later regeneration. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Pin corpus, rule and seed versions for later regeneration versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-corpus-comparison",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Pin corpus, rule and seed versions for later regeneration versus Measure overlap between two supplied resources with transparent normalization; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-evidence-completeness",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Pin corpus, rule and seed versions for later regeneration versus Report missing claim level evidence without inventing sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Pin corpus, rule and seed versions for later regeneration",
        "outline": [
          "Explain the specific decision: Pin corpus, rule and seed versions for later regeneration",
          "Define the applicable contract and limits for Name data reproducibility bundle",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Pin corpus, rule and seed versions for later regeneration; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Pin corpus, rule and seed versions for later regeneration",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:993",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-cultural-reviewer-queue",
      "slug": "name-data-cultural-reviewer-queue",
      "name": "Name data cultural reviewer queue",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-cultural-reviewer-queue/",
        "ja": "/ja/tools/name-data-cultural-reviewer-queue/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Package uncertain claims for named human review",
      "task": "Package uncertain claims for named human review",
      "searchIntent": {
        "primary": "Complete the task: Package uncertain claims for named human review",
        "queryHypothesis": "name data cultural reviewer queue",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package uncertain claims for named human review?",
        "When should name data cultural reviewer queue be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package uncertain claims for named human review",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package uncertain claims for named human review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-offensive-association-review",
          "score": 0.18,
          "sharedProfile": true,
          "difference": "Package uncertain claims for named human review versus Route context dependent issues to human review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-name-specialist-handoff",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Package uncertain claims for named human review versus Package exact questions and candidate evidence for review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-era-mismatch-review",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Package uncertain claims for named human review versus Flag unsupported period claims for a specialist review; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package uncertain claims for named human review",
        "outline": [
          "Explain the specific decision: Package uncertain claims for named human review",
          "Define the applicable contract and limits for Name data cultural reviewer queue",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package uncertain claims for named human review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package uncertain claims for named human review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:994",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-example-provenance",
      "slug": "name-data-example-provenance",
      "name": "Name data example provenance",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-example-provenance/",
        "ja": "/ja/tools/name-data-example-provenance/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Mark static examples as authored, generated or externally sourced",
      "task": "Mark static examples as authored, generated or externally sourced",
      "searchIntent": {
        "primary": "Complete the task: Mark static examples as authored, generated or externally sourced",
        "queryHypothesis": "name data example provenance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to mark static examples as authored, generated or externally sourced?",
        "When should name data example provenance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Mark static examples as authored, generated or externally sourced",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Mark static examples as authored, generated or externally sourced. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-pronunciation-provenance",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Mark static examples as authored, generated or externally sourced versus Attach approved audio or reading evidence to each entry; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-transliteration-provenance",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Mark static examples as authored, generated or externally sourced versus Record the system and manual exceptions for each form; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-name-data-version-pin",
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Mark static examples as authored, generated or externally sourced versus Make save generated names reproducible across data updates; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Mark static examples as authored, generated or externally sourced",
        "outline": [
          "Explain the specific decision: Mark static examples as authored, generated or externally sourced",
          "Define the applicable contract and limits for Name data example provenance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Mark static examples as authored, generated or externally sourced; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Mark static examples as authored, generated or externally sourced",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:995",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-name-data-evidence-completeness",
      "slug": "name-data-evidence-completeness",
      "name": "Name data evidence completeness",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-evidence-completeness/",
        "ja": "/ja/tools/name-data-evidence-completeness/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Report missing claim level evidence without inventing sources",
      "task": "Report missing claim level evidence without inventing sources",
      "searchIntent": {
        "primary": "Complete the task: Report missing claim level evidence without inventing sources",
        "queryHypothesis": "name data evidence completeness",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to report missing claim level evidence without inventing sources?",
        "When should name data evidence completeness be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Report missing claim level evidence without inventing sources",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Report missing claim level evidence without inventing sources. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-localized-historical-name-evidence",
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Report missing claim level evidence without inventing sources versus Track sources separately for each locale; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-historical-religious-name-evidence",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Report missing claim level evidence without inventing sources versus Require community and period specific sources; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Report missing claim level evidence without inventing sources versus Track dictionary evidence separately from creative symbolism; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Report missing claim level evidence without inventing sources",
        "outline": [
          "Explain the specific decision: Report missing claim level evidence without inventing sources",
          "Define the applicable contract and limits for Name data evidence completeness",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Report missing claim level evidence without inventing sources; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Report missing claim level evidence without inventing sources",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:996",
      "profileSource": "data/profiles.json#data-methods"
    },
    {
      "id": "nw-naming-project-brief",
      "slug": "naming-project-brief",
      "name": "Naming project brief",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-brief/",
        "ja": "/ja/tools/naming-project-brief/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Capture cast, language, world and publishing constraints in one editable brief",
      "task": "Capture cast, language, world and publishing constraints in one editable brief",
      "searchIntent": {
        "primary": "Complete the task: Capture cast, language, world and publishing constraints in one editable brief",
        "queryHypothesis": "naming project brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to capture cast, language, world and publishing constraints in one editable brief?",
        "When should naming project brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Apply configured matching semantics to every participating engine"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Capture cast, language, world and publishing constraints in one editable brief",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview",
        "Project exclusion manifest"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Capture cast, language, world and publishing constraints in one editable brief. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-character-naming-brief",
          "score": 0.21562499999999998,
          "sharedProfile": false,
          "difference": "Capture cast, language, world and publishing constraints in one editable brief versus Convert a role, setting and narrative distance into a testable name brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-publisher-handoff",
          "score": 0.13392857142857142,
          "sharedProfile": true,
          "difference": "Capture cast, language, world and publishing constraints in one editable brief versus Reconcile bylines, cast pages and public facing names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-rule-priorities",
          "score": 0.13083333333333333,
          "sharedProfile": true,
          "difference": "Capture cast, language, world and publishing constraints in one editable brief versus Order hard constraints and soft preferences with explicit conflict handling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Capture cast, language, world and publishing constraints in one editable brief",
        "outline": [
          "Explain the specific decision: Capture cast, language, world and publishing constraints in one editable brief",
          "Define the applicable contract and limits for Naming project brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Capture cast, language, world and publishing constraints in one editable brief; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Capture cast, language, world and publishing constraints in one editable brief",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Import preserves exclusion mode"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:999",
      "profileSource": "data/profiles.json#project-workflows",
      "absorbedModules": [
        {
          "sourceId": "nw-naming-project-exclusion-list",
          "input": "sharedExclusions",
          "rule": "Apply configured matching semantics to every participating engine",
          "output": "Project exclusion manifest",
          "acceptance": "Import preserves exclusion mode",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-naming-project-rule-priorities",
      "slug": "naming-project-rule-priorities",
      "name": "Naming project rule priorities",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-rule-priorities/",
        "ja": "/ja/tools/naming-project-rule-priorities/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Order hard constraints and soft preferences with explicit conflict handling",
      "task": "Order hard constraints and soft preferences with explicit conflict handling",
      "searchIntent": {
        "primary": "Complete the task: Order hard constraints and soft preferences with explicit conflict handling",
        "queryHypothesis": "naming project rule priorities",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to order hard constraints and soft preferences with explicit conflict handling?",
        "When should naming project rule priorities be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Order hard constraints and soft preferences with explicit conflict handling",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Order hard constraints and soft preferences with explicit conflict handling. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-rule-migration",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Order hard constraints and soft preferences with explicit conflict handling versus Compare outcomes before adopting a new shared naming grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-brief",
          "score": 0.13083333333333333,
          "sharedProfile": true,
          "difference": "Order hard constraints and soft preferences with explicit conflict handling versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-empty-pool-recovery",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Order hard constraints and soft preferences with explicit conflict handling versus Relax only user selected constraints with an audit trail; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Order hard constraints and soft preferences with explicit conflict handling",
        "outline": [
          "Explain the specific decision: Order hard constraints and soft preferences with explicit conflict handling",
          "Define the applicable contract and limits for Naming project rule priorities",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Order hard constraints and soft preferences with explicit conflict handling; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Order hard constraints and soft preferences with explicit conflict handling",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1000",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-locked-components",
      "slug": "naming-project-locked-components",
      "name": "Naming project locked components",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-locked-components/",
        "ja": "/ja/tools/naming-project-locked-components/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Preserve approved parts while revising unresolved components",
      "task": "Preserve approved parts while revising unresolved components",
      "searchIntent": {
        "primary": "Complete the task: Preserve approved parts while revising unresolved components",
        "queryHypothesis": "naming project locked components",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve approved parts while revising unresolved components?",
        "When should naming project locked components be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve approved parts while revising unresolved components",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve approved parts while revising unresolved components. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-translator-handoff",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Preserve approved parts while revising unresolved components versus Export stable IDs, evidence and unresolved localization decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-brief",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Preserve approved parts while revising unresolved components versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-decision-record",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Preserve approved parts while revising unresolved components versus Save chosen names with reasons and rejected alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve approved parts while revising unresolved components",
        "outline": [
          "Explain the specific decision: Preserve approved parts while revising unresolved components",
          "Define the applicable contract and limits for Naming project locked components",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve approved parts while revising unresolved components; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve approved parts while revising unresolved components",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1001",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-candidate-comparison",
      "slug": "naming-project-candidate-comparison",
      "name": "Naming project candidate comparison",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-candidate-comparison/",
        "ja": "/ja/tools/naming-project-candidate-comparison/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Compare a fixed shortlist against task specific criteria",
      "task": "Compare a fixed shortlist against task specific criteria",
      "searchIntent": {
        "primary": "Complete the task: Compare a fixed shortlist against task specific criteria",
        "queryHypothesis": "naming project candidate comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare a fixed shortlist against task specific criteria?",
        "When should naming project candidate comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Deduplicate only within the declared local scope"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare a fixed shortlist against task specific criteria",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview",
        "Duplicate explanation"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare a fixed shortlist against task specific criteria. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-candidate-decision",
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Compare a fixed shortlist against task specific criteria versus Compare a fixed shortlist using published heuristic criteria; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-accessibility-comparison",
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Compare a fixed shortlist against task specific criteria versus Record participant specific difficulties without generalizing to a diagnosis; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Compare a fixed shortlist against task specific criteria versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare a fixed shortlist against task specific criteria",
        "outline": [
          "Explain the specific decision: Compare a fixed shortlist against task specific criteria",
          "Define the applicable contract and limits for Naming project candidate comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare a fixed shortlist against task specific criteria; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare a fixed shortlist against task specific criteria",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation.",
        "Equivalent saved candidate is reported without claiming global uniqueness"
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1004",
      "profileSource": "data/profiles.json#project-workflows",
      "absorbedModules": [
        {
          "sourceId": "nw-naming-project-favorites-deduplication",
          "input": "savedCandidates",
          "rule": "Deduplicate only within the declared local scope",
          "output": "Duplicate explanation",
          "acceptance": "Equivalent saved candidate is reported without claiming global uniqueness",
          "status": "design-integrated-not-implemented"
        }
      ]
    },
    {
      "id": "nw-naming-project-decision-record",
      "slug": "naming-project-decision-record",
      "name": "Naming project decision record",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-decision-record/",
        "ja": "/ja/tools/naming-project-decision-record/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Save chosen names with reasons and rejected alternatives",
      "task": "Save chosen names with reasons and rejected alternatives",
      "searchIntent": {
        "primary": "Complete the task: Save chosen names with reasons and rejected alternatives",
        "queryHypothesis": "naming project decision record",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to save chosen names with reasons and rejected alternatives?",
        "When should naming project decision record be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Save chosen names with reasons and rejected alternatives",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Save chosen names with reasons and rejected alternatives. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-reopening-decision",
          "score": 0.2333333333333333,
          "sharedProfile": true,
          "difference": "Save chosen names with reasons and rejected alternatives versus List downstream work caused by changing an approved name; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-manuscript-name-edit-decision-log",
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Save chosen names with reasons and rejected alternatives versus Preserve reasons, reviewers and affected passages; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Save chosen names with reasons and rejected alternatives versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Save chosen names with reasons and rejected alternatives",
        "outline": [
          "Explain the specific decision: Save chosen names with reasons and rejected alternatives",
          "Define the applicable contract and limits for Naming project decision record",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Save chosen names with reasons and rejected alternatives; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Save chosen names with reasons and rejected alternatives",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1005",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-version-restore",
      "slug": "naming-project-version-restore",
      "name": "Naming project version restore",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-version-restore/",
        "ja": "/ja/tools/naming-project-version-restore/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Restore parameters and identity records from an explicit version",
      "task": "Restore parameters and identity records from an explicit version",
      "searchIntent": {
        "primary": "Complete the task: Restore parameters and identity records from an explicit version",
        "queryHypothesis": "naming project version restore",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to restore parameters and identity records from an explicit version?",
        "When should naming project version restore be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Restore parameters and identity records from an explicit version",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Restore parameters and identity records from an explicit version. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-spirit-place-bound-identity",
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Restore parameters and identity records from an explicit version versus Connect personal identity to a fictional place without merging records; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Restore parameters and identity records from an explicit version versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-alias-retirement-plan",
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Restore parameters and identity records from an explicit version versus Decide what records and relationships retain a retired identity; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Restore parameters and identity records from an explicit version",
        "outline": [
          "Explain the specific decision: Restore parameters and identity records from an explicit version",
          "Define the applicable contract and limits for Naming project version restore",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Restore parameters and identity records from an explicit version; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Restore parameters and identity records from an explicit version",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1006",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-collaboration-review",
      "slug": "naming-project-collaboration-review",
      "name": "Naming project collaboration review",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-collaboration-review/",
        "ja": "/ja/tools/naming-project-collaboration-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Prepare a commentable package without sending it to anyone",
      "task": "Prepare a commentable package without sending it to anyone",
      "searchIntent": {
        "primary": "Complete the task: Prepare a commentable package without sending it to anyone",
        "queryHypothesis": "naming project collaboration review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prepare a commentable package without sending it to anyone?",
        "When should naming project collaboration review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prepare a commentable package without sending it to anyone",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prepare a commentable package without sending it to anyone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-batch-review",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Prepare a commentable package without sending it to anyone versus Separate generated candidates from accepted character identities; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-review-handoff",
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Prepare a commentable package without sending it to anyone versus Package unresolved choices and evidence for a human translator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Prepare a commentable package without sending it to anyone versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prepare a commentable package without sending it to anyone",
        "outline": [
          "Explain the specific decision: Prepare a commentable package without sending it to anyone",
          "Define the applicable contract and limits for Naming project collaboration review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prepare a commentable package without sending it to anyone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prepare a commentable package without sending it to anyone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1007",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-editor-handoff",
      "slug": "naming-project-editor-handoff",
      "name": "Naming project editor handoff",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-editor-handoff/",
        "ja": "/ja/tools/naming-project-editor-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Export approved names and open questions for an editor",
      "task": "Export approved names and open questions for an editor",
      "searchIntent": {
        "primary": "Complete the task: Export approved names and open questions for an editor",
        "queryHypothesis": "naming project editor handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export approved names and open questions for an editor?",
        "When should naming project editor handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export approved names and open questions for an editor",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export approved names and open questions for an editor. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.2472222222222222,
          "sharedProfile": true,
          "difference": "Export approved names and open questions for an editor versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-translator-handoff",
          "score": 0.24,
          "sharedProfile": true,
          "difference": "Export approved names and open questions for an editor versus Export stable IDs, evidence and unresolved localization decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Export approved names and open questions for an editor versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export approved names and open questions for an editor",
        "outline": [
          "Explain the specific decision: Export approved names and open questions for an editor",
          "Define the applicable contract and limits for Naming project editor handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export approved names and open questions for an editor; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export approved names and open questions for an editor",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1008",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-illustrator-handoff",
      "slug": "naming-project-illustrator-handoff",
      "name": "Naming project illustrator handoff",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-illustrator-handoff/",
        "ja": "/ja/tools/naming-project-illustrator-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Package visible name props and identity references for an artist",
      "task": "Package visible name props and identity references for an artist",
      "searchIntent": {
        "primary": "Complete the task: Package visible name props and identity references for an artist",
        "queryHypothesis": "naming project illustrator handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to package visible name props and identity references for an artist?",
        "When should naming project illustrator handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Package visible name props and identity references for an artist",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Package visible name props and identity references for an artist. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Package visible name props and identity references for an artist versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Package visible name props and identity references for an artist versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-publisher-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Package visible name props and identity references for an artist versus Reconcile bylines, cast pages and public facing names; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Package visible name props and identity references for an artist",
        "outline": [
          "Explain the specific decision: Package visible name props and identity references for an artist",
          "Define the applicable contract and limits for Naming project illustrator handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Package visible name props and identity references for an artist; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Package visible name props and identity references for an artist",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1009",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-performer-handoff",
      "slug": "naming-project-performer-handoff",
      "name": "Naming project performer handoff",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-performer-handoff/",
        "ja": "/ja/tools/naming-project-performer-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Export readings and speaker specific address rules",
      "task": "Export readings and speaker specific address rules",
      "searchIntent": {
        "primary": "Complete the task: Export readings and speaker specific address rules",
        "queryHypothesis": "naming project performer handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export readings and speaker specific address rules?",
        "When should naming project performer handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export readings and speaker specific address rules",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export readings and speaker specific address rules. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.2472222222222222,
          "sharedProfile": true,
          "difference": "Export readings and speaker specific address rules versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-translator-handoff",
          "score": 0.22916666666666666,
          "sharedProfile": true,
          "difference": "Export readings and speaker specific address rules versus Export stable IDs, evidence and unresolved localization decisions; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Export readings and speaker specific address rules versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export readings and speaker specific address rules",
        "outline": [
          "Explain the specific decision: Export readings and speaker specific address rules",
          "Define the applicable contract and limits for Naming project performer handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export readings and speaker specific address rules; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export readings and speaker specific address rules",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1010",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-translator-handoff",
      "slug": "naming-project-translator-handoff",
      "name": "Naming project translator handoff",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-translator-handoff/",
        "ja": "/ja/tools/naming-project-translator-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Export stable IDs, evidence and unresolved localization decisions",
      "task": "Export stable IDs, evidence and unresolved localization decisions",
      "searchIntent": {
        "primary": "Complete the task: Export stable IDs, evidence and unresolved localization decisions",
        "queryHypothesis": "naming project translator handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export stable IDs, evidence and unresolved localization decisions?",
        "When should naming project translator handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export stable IDs, evidence and unresolved localization decisions",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export stable IDs, evidence and unresolved localization decisions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.24,
          "sharedProfile": true,
          "difference": "Export stable IDs, evidence and unresolved localization decisions versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.22916666666666666,
          "sharedProfile": true,
          "difference": "Export stable IDs, evidence and unresolved localization decisions versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-localized-name-review-handoff",
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Export stable IDs, evidence and unresolved localization decisions versus Package unresolved choices and evidence for a human translator; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export stable IDs, evidence and unresolved localization decisions",
        "outline": [
          "Explain the specific decision: Export stable IDs, evidence and unresolved localization decisions",
          "Define the applicable contract and limits for Naming project translator handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export stable IDs, evidence and unresolved localization decisions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export stable IDs, evidence and unresolved localization decisions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1011",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-publisher-handoff",
      "slug": "naming-project-publisher-handoff",
      "name": "Naming project publisher handoff",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-publisher-handoff/",
        "ja": "/ja/tools/naming-project-publisher-handoff/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Reconcile bylines, cast pages and public facing names",
      "task": "Reconcile bylines, cast pages and public facing names",
      "searchIntent": {
        "primary": "Complete the task: Reconcile bylines, cast pages and public facing names",
        "queryHypothesis": "naming project publisher handoff",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile bylines, cast pages and public facing names?",
        "When should naming project publisher handoff be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile bylines, cast pages and public facing names",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile bylines, cast pages and public facing names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-editor-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Reconcile bylines, cast pages and public facing names versus Export approved names and open questions for an editor; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-illustrator-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Reconcile bylines, cast pages and public facing names versus Package visible name props and identity references for an artist; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Reconcile bylines, cast pages and public facing names versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile bylines, cast pages and public facing names",
        "outline": [
          "Explain the specific decision: Reconcile bylines, cast pages and public facing names",
          "Define the applicable contract and limits for Naming project publisher handoff",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile bylines, cast pages and public facing names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile bylines, cast pages and public facing names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1012",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-conflict-explanation",
      "slug": "naming-project-conflict-explanation",
      "name": "Naming project conflict explanation",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-conflict-explanation/",
        "ja": "/ja/tools/naming-project-conflict-explanation/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Explain which rules make a request impossible and suggest bounded changes",
      "task": "Explain which rules make a request impossible and suggest bounded changes",
      "searchIntent": {
        "primary": "Complete the task: Explain which rules make a request impossible and suggest bounded changes",
        "queryHypothesis": "naming project conflict explanation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain which rules make a request impossible and suggest bounded changes?",
        "When should naming project conflict explanation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain which rules make a request impossible and suggest bounded changes",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain which rules make a request impossible and suggest bounded changes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-performer-handoff",
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Explain which rules make a request impossible and suggest bounded changes versus Export readings and speaker specific address rules; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-scope-freeze",
          "score": 0.11333333333333333,
          "sharedProfile": true,
          "difference": "Explain which rules make a request impossible and suggest bounded changes versus Record which names may still change before an editorial milestone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-name-data-cohort-bias",
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Explain which rules make a request impossible and suggest bounded changes versus Explain which populations are absent from a supplied dataset; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain which rules make a request impossible and suggest bounded changes",
        "outline": [
          "Explain the specific decision: Explain which rules make a request impossible and suggest bounded changes",
          "Define the applicable contract and limits for Naming project conflict explanation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain which rules make a request impossible and suggest bounded changes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain which rules make a request impossible and suggest bounded changes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1013",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-empty-pool-recovery",
      "slug": "naming-project-empty-pool-recovery",
      "name": "Naming project empty pool recovery",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-empty-pool-recovery/",
        "ja": "/ja/tools/naming-project-empty-pool-recovery/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Relax only user selected constraints with an audit trail",
      "task": "Relax only user selected constraints with an audit trail",
      "searchIntent": {
        "primary": "Complete the task: Relax only user selected constraints with an audit trail",
        "queryHypothesis": "naming project empty pool recovery",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to relax only user selected constraints with an audit trail?",
        "When should naming project empty pool recovery be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Relax only user selected constraints with an audit trail",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Relax only user selected constraints with an audit trail. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-brief",
          "score": 0.11333333333333333,
          "sharedProfile": true,
          "difference": "Relax only user selected constraints with an audit trail versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-rule-priorities",
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Relax only user selected constraints with an audit trail versus Order hard constraints and soft preferences with explicit conflict handling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-decision-record",
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Relax only user selected constraints with an audit trail versus Save chosen names with reasons and rejected alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Relax only user selected constraints with an audit trail",
        "outline": [
          "Explain the specific decision: Relax only user selected constraints with an audit trail",
          "Define the applicable contract and limits for Naming project empty pool recovery",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Relax only user selected constraints with an audit trail; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Relax only user selected constraints with an audit trail",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1014",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-batch-review",
      "slug": "naming-project-batch-review",
      "name": "Naming project batch review",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-batch-review/",
        "ja": "/ja/tools/naming-project-batch-review/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Separate generated candidates from accepted character identities",
      "task": "Separate generated candidates from accepted character identities",
      "searchIntent": {
        "primary": "Complete the task: Separate generated candidates from accepted character identities",
        "queryHypothesis": "naming project batch review",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate generated candidates from accepted character identities?",
        "When should naming project batch review be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate generated candidates from accepted character identities",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate generated candidates from accepted character identities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-collaboration-review",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Separate generated candidates from accepted character identities versus Prepare a commentable package without sending it to anyone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-game-generated-cast-import-diff",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate generated candidates from accepted character identities versus Compare approved and newly generated names before replacement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-nameless-rebellion-identity",
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Separate generated candidates from accepted character identities versus Coordinate collective and personal identities in an authored movement; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate generated candidates from accepted character identities",
        "outline": [
          "Explain the specific decision: Separate generated candidates from accepted character identities",
          "Define the applicable contract and limits for Naming project batch review",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate generated candidates from accepted character identities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate generated candidates from accepted character identities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1015",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-duplicate-exception",
      "slug": "naming-project-duplicate-exception",
      "name": "Naming project duplicate exception",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-duplicate-exception/",
        "ja": "/ja/tools/naming-project-duplicate-exception/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Permit an intentional duplicate with a stated story reason",
      "task": "Permit an intentional duplicate with a stated story reason",
      "searchIntent": {
        "primary": "Complete the task: Permit an intentional duplicate with a stated story reason",
        "queryHypothesis": "naming project duplicate exception",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to permit an intentional duplicate with a stated story reason?",
        "When should naming project duplicate exception be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Permit an intentional duplicate with a stated story reason",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Permit an intentional duplicate with a stated story reason. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-historical-story-naming-exception",
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Permit an intentional duplicate with a stated story reason versus Explain an intentional departure in an editorial note; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-family-inheritance-exception",
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Permit an intentional duplicate with a stated story reason versus Document the story event that overrides the default surname rule; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-brief",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Permit an intentional duplicate with a stated story reason versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Permit an intentional duplicate with a stated story reason",
        "outline": [
          "Explain the specific decision: Permit an intentional duplicate with a stated story reason",
          "Define the applicable contract and limits for Naming project duplicate exception",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Permit an intentional duplicate with a stated story reason; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Permit an intentional duplicate with a stated story reason",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1016",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-scope-freeze",
      "slug": "naming-project-scope-freeze",
      "name": "Naming project scope freeze",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-scope-freeze/",
        "ja": "/ja/tools/naming-project-scope-freeze/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Record which names may still change before an editorial milestone",
      "task": "Record which names may still change before an editorial milestone",
      "searchIntent": {
        "primary": "Complete the task: Record which names may still change before an editorial milestone",
        "queryHypothesis": "naming project scope freeze",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record which names may still change before an editorial milestone?",
        "When should naming project scope freeze be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record which names may still change before an editorial milestone",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record which names may still change before an editorial milestone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-rule-migration",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Record which names may still change before an editorial milestone versus Compare outcomes before adopting a new shared naming grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-invented-sacred-name-avoidance",
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Record which names may still change before an editorial milestone versus Define who may speak which name in which context; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-conflict-explanation",
          "score": 0.11333333333333333,
          "sharedProfile": true,
          "difference": "Record which names may still change before an editorial milestone versus Explain which rules make a request impossible and suggest bounded changes; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record which names may still change before an editorial milestone",
        "outline": [
          "Explain the specific decision: Record which names may still change before an editorial milestone",
          "Define the applicable contract and limits for Naming project scope freeze",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record which names may still change before an editorial milestone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record which names may still change before an editorial milestone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1017",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-reopening-decision",
      "slug": "naming-project-reopening-decision",
      "name": "Naming project reopening decision",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-reopening-decision/",
        "ja": "/ja/tools/naming-project-reopening-decision/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "List downstream work caused by changing an approved name",
      "task": "List downstream work caused by changing an approved name",
      "searchIntent": {
        "primary": "Complete the task: List downstream work caused by changing an approved name",
        "queryHypothesis": "naming project reopening decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to list downstream work caused by changing an approved name?",
        "When should naming project reopening decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: List downstream work caused by changing an approved name",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: List downstream work caused by changing an approved name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-decision-record",
          "score": 0.2333333333333333,
          "sharedProfile": true,
          "difference": "List downstream work caused by changing an approved name versus Save chosen names with reasons and rejected alternatives; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-marriage-name-decision",
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "List downstream work caused by changing an approved name versus Compare retained, combined and changed names in a fictional household; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-brief",
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "List downstream work caused by changing an approved name versus Capture cast, language, world and publishing constraints in one editable brief; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "List downstream work caused by changing an approved name",
        "outline": [
          "Explain the specific decision: List downstream work caused by changing an approved name",
          "Define the applicable contract and limits for Naming project reopening decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for List downstream work caused by changing an approved name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: List downstream work caused by changing an approved name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1018",
      "profileSource": "data/profiles.json#project-workflows"
    },
    {
      "id": "nw-naming-project-rule-migration",
      "slug": "naming-project-rule-migration",
      "name": "Naming project rule migration",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-rule-migration/",
        "ja": "/ja/tools/naming-project-rule-migration/"
      },
      "urlState": "reserved-paths-not-published",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Compare outcomes before adopting a new shared naming grammar",
      "task": "Compare outcomes before adopting a new shared naming grammar",
      "searchIntent": {
        "primary": "Complete the task: Compare outcomes before adopting a new shared naming grammar",
        "queryHypothesis": "naming project rule migration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare outcomes before adopting a new shared naming grammar?",
        "When should naming project rule migration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare outcomes before adopting a new shared naming grammar",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare outcomes before adopting a new shared naming grammar. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-rule-priorities",
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Compare outcomes before adopting a new shared naming grammar versus Order hard constraints and soft preferences with explicit conflict handling; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-naming-project-scope-freeze",
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Compare outcomes before adopting a new shared naming grammar versus Record which names may still change before an editorial milestone; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        },
        {
          "id": "nw-series-world-rule-regression",
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Compare outcomes before adopting a new shared naming grammar versus Compare newly added names against the current fictional grammar; behavioral distinction remains unapproved.",
          "resolution": "review-required"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare outcomes before adopting a new shared naming grammar",
        "outline": [
          "Explain the specific decision: Compare outcomes before adopting a new shared naming grammar",
          "Define the applicable contract and limits for Naming project rule migration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare outcomes before adopting a new shared naming grammar; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare outcomes before adopting a new shared naming grammar",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "candidate",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1019",
      "profileSource": "data/profiles.json#project-workflows"
    }
  ],
  "baselineCount": 967,
  "archive": [
    {
      "id": "nw-twin-character-names",
      "slug": "twin-character-names",
      "name": "Twin character names",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/twin-character-names/",
        "ja": "/ja/tools/twin-character-names/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Separate intentional pairing from mistaken identity mechanics",
      "task": "Separate intentional pairing from mistaken identity mechanics",
      "searchIntent": {
        "primary": "Complete the task: Separate intentional pairing from mistaken identity mechanics",
        "queryHypothesis": "twin character names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate intentional pairing from mistaken identity mechanics?",
        "When should twin character names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate intentional pairing from mistaken identity mechanics",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate intentional pairing from mistaken identity mechanics. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Sibling name differentiation. Number and birth relation alone do not establish a new main task. Add twin-specific resemblance and mistaken-identity settings to the sibling workflow.",
        "deskReview": {
          "candidate": "twin-character-names",
          "parent": "sibling-name-differentiation",
          "action": "merge-proposed",
          "reason": "Number and birth relation alone do not establish a new main task. Add twin-specific resemblance and mistaken-identity settings to the sibling workflow.",
          "reopenIf": "A tested knowledge-state mistaken-identity workflow requires different outputs.",
          "parentId": "nw-sibling-name-differentiation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-identical-twin-scene-labels",
          "title": 0.25,
          "task": 0.25,
          "score": 0.25,
          "sharedProfile": false,
          "difference": "Task A: Separate intentional pairing from mistaken identity mechanics. Task B: Track knowledge of identity across a mistaken identity scene. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-clan-branch-registry",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Separate intentional pairing from mistaken identity mechanics. Task B: Distinguish branch identity from individual personal names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-detective-notebook-identity-map",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Separate intentional pairing from mistaken identity mechanics. Task B: Separate hypothesis, testimony and corroborated identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate intentional pairing from mistaken identity mechanics",
        "outline": [
          "Explain the specific decision: Separate intentional pairing from mistaken identity mechanics",
          "Define the applicable contract and limits for Twin character names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate intentional pairing from mistaken identity mechanics; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate intentional pairing from mistaken identity mechanics",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Number and birth relation alone do not establish a new main task. Add twin-specific resemblance and mistaken-identity settings to the sibling workflow."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:41",
      "profileSource": "data/profiles.json#kinship",
      "disposition": {
        "action": "merged",
        "parentId": "nw-family-name-planner",
        "reason": "Number and birth relation alone do not establish a new main task. Add twin-specific resemblance and mistaken-identity settings to the sibling workflow.",
        "reopenIf": "A tested knowledge-state mistaken-identity workflow requires different outputs.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published",
        "parentHistory": [
          "nw-sibling-name-differentiation"
        ]
      }
    },
    {
      "id": "nw-triplet-introduction-names",
      "slug": "triplet-introduction-names",
      "name": "Triplet introduction names",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/triplet-introduction-names/",
        "ja": "/ja/tools/triplet-introduction-names/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Plan three distinct spoken and written introductions",
      "task": "Plan three distinct spoken and written introductions",
      "searchIntent": {
        "primary": "Complete the task: Plan three distinct spoken and written introductions",
        "queryHypothesis": "triplet introduction names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to plan three distinct spoken and written introductions?",
        "When should triplet introduction names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Plan three distinct spoken and written introductions",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Plan three distinct spoken and written introductions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Sibling name differentiation. Three siblings is a cardinality setting. Introduction pacing belongs in the group introduction workflow.",
        "deskReview": {
          "candidate": "triplet-introduction-names",
          "parent": "sibling-name-differentiation",
          "action": "merge-proposed",
          "reason": "Three siblings is a cardinality setting. Introduction pacing belongs in the group introduction workflow.",
          "reopenIf": "A distinct production or narrative workflow is demonstrated.",
          "parentId": "nw-sibling-name-differentiation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-audio-introduction",
          "title": 0.25,
          "task": 0.2222222222222222,
          "score": 0.23194444444444443,
          "sharedProfile": false,
          "difference": "Task A: Plan three distinct spoken and written introductions. Task B: Test host introductions and spoken acknowledgments. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-ensemble-name-separation",
          "title": 0,
          "task": 0.3333333333333333,
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Task A: Plan three distinct spoken and written introductions. Task B: Optimize a supplied cast for distinct written and spoken forms. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-introduction-naming",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Task A: Plan three distinct spoken and written introductions. Task B: Stage first reference, full introduction and later short forms. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Plan three distinct spoken and written introductions",
        "outline": [
          "Explain the specific decision: Plan three distinct spoken and written introductions",
          "Define the applicable contract and limits for Triplet introduction names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Plan three distinct spoken and written introductions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Plan three distinct spoken and written introductions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Three siblings is a cardinality setting. Introduction pacing belongs in the group introduction workflow."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:42",
      "profileSource": "data/profiles.json#kinship",
      "disposition": {
        "action": "merged",
        "parentId": "nw-family-name-planner",
        "reason": "Three siblings is a cardinality setting. Introduction pacing belongs in the group introduction workflow.",
        "reopenIf": "A distinct production or narrative workflow is demonstrated.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published",
        "parentHistory": [
          "nw-sibling-name-differentiation"
        ]
      }
    },
    {
      "id": "nw-matrilineal-fictional-inheritance",
      "slug": "matrilineal-fictional-inheritance",
      "name": "Matrilineal fictional inheritance",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/matrilineal-fictional-inheritance/",
        "ja": "/ja/tools/matrilineal-fictional-inheritance/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Derive surnames through a declared maternal rule",
      "task": "Derive surnames through a declared maternal rule",
      "searchIntent": {
        "primary": "Complete the task: Derive surnames through a declared maternal rule",
        "queryHypothesis": "matrilineal fictional inheritance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive surnames through a declared maternal rule?",
        "When should matrilineal fictional inheritance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive surnames through a declared maternal rule",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive surnames through a declared maternal rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Family name planner. Maternal inheritance is a rule choice in the same family graph task, not independent page value.",
        "deskReview": {
          "candidate": "matrilineal-fictional-inheritance",
          "parent": "family-name-planner",
          "action": "merge-proposed",
          "reason": "Maternal inheritance is a rule choice in the same family graph task, not independent page value.",
          "parentId": "nw-family-name-planner",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-patrilineal-fictional-inheritance",
          "title": 0.3333333333333333,
          "task": 0.7142857142857143,
          "score": 0.580952380952381,
          "sharedProfile": true,
          "difference": "Task A: Derive surnames through a declared maternal rule. Task B: Derive surnames through a declared paternal rule. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-matronymic-grammar",
          "title": 0,
          "task": 0.375,
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Task A: Derive surnames through a declared maternal rule. Task B: Derive names from maternal records with declared exceptions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-multilingual-household",
          "title": 0,
          "task": 0.2727272727272727,
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Task A: Derive surnames through a declared maternal rule. Task B: Combine two rule systems through declared family choices. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive surnames through a declared maternal rule",
        "outline": [
          "Explain the specific decision: Derive surnames through a declared maternal rule",
          "Define the applicable contract and limits for Matrilineal fictional inheritance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive surnames through a declared maternal rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive surnames through a declared maternal rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Maternal inheritance is a rule choice in the same family graph task, not independent page value."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:51",
      "profileSource": "data/profiles.json#kinship",
      "disposition": {
        "action": "merged",
        "parentId": "nw-family-name-planner",
        "reason": "Maternal inheritance is a rule choice in the same family graph task, not independent page value.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-patrilineal-fictional-inheritance",
      "slug": "patrilineal-fictional-inheritance",
      "name": "Patrilineal fictional inheritance",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/patrilineal-fictional-inheritance/",
        "ja": "/ja/tools/patrilineal-fictional-inheritance/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Derive surnames through a declared paternal rule",
      "task": "Derive surnames through a declared paternal rule",
      "searchIntent": {
        "primary": "Complete the task: Derive surnames through a declared paternal rule",
        "queryHypothesis": "patrilineal fictional inheritance",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive surnames through a declared paternal rule?",
        "When should patrilineal fictional inheritance be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive surnames through a declared paternal rule",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive surnames through a declared paternal rule. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Family name planner. Paternal inheritance changes a parameterized traversal rule within the family solver.",
        "deskReview": {
          "candidate": "patrilineal-fictional-inheritance",
          "parent": "family-name-planner",
          "action": "merge-proposed",
          "reason": "Paternal inheritance changes a parameterized traversal rule within the family solver.",
          "parentId": "nw-family-name-planner",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-matrilineal-fictional-inheritance",
          "title": 0.3333333333333333,
          "task": 0.7142857142857143,
          "score": 0.580952380952381,
          "sharedProfile": true,
          "difference": "Task A: Derive surnames through a declared paternal rule. Task B: Derive surnames through a declared maternal rule. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-multilingual-household",
          "title": 0,
          "task": 0.2727272727272727,
          "score": 0.17727272727272728,
          "sharedProfile": false,
          "difference": "Task A: Derive surnames through a declared paternal rule. Task B: Combine two rule systems through declared family choices. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-matronymic-grammar",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Derive surnames through a declared paternal rule. Task B: Derive names from maternal records with declared exceptions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive surnames through a declared paternal rule",
        "outline": [
          "Explain the specific decision: Derive surnames through a declared paternal rule",
          "Define the applicable contract and limits for Patrilineal fictional inheritance",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive surnames through a declared paternal rule; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive surnames through a declared paternal rule",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Paternal inheritance changes a parameterized traversal rule within the family solver."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:52",
      "profileSource": "data/profiles.json#kinship",
      "disposition": {
        "action": "merged",
        "parentId": "nw-family-name-planner",
        "reason": "Paternal inheritance changes a parameterized traversal rule within the family solver.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-dual-surname-family-system",
      "slug": "dual-surname-family-system",
      "name": "Dual surname family system",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/dual-surname-family-system/",
        "ja": "/ja/tools/dual-surname-family-system/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Track ordered components and how children inherit them",
      "task": "Track ordered components and how children inherit them",
      "searchIntent": {
        "primary": "Complete the task: Track ordered components and how children inherit them",
        "queryHypothesis": "dual surname family system",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track ordered components and how children inherit them?",
        "When should dual surname family system be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "relationship graph: establish actual kinship",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "household timeline: distinguish cohabitation from descent",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "inheritance policy: constrain shared components",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling"
      ],
      "requiredData": [
        {
          "description": "authored family graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned fictional inheritance grammar",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "dated naming events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track ordered components and how children inherit them",
        "derive inherited fields from directed relationships",
        "record explicit exceptions rather than infer parentage from spelling",
        "Proposed category workflow: graph → rule assignment → propagation preview → household scene review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "person keyed name table",
        "inheritance path and exceptions",
        "relative confusion warnings"
      ],
      "capabilities": [
        "propagate a parent name change through eligible descendants",
        "preview household forms before and after a dated event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track ordered components and how children inherit them. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Family name planner. Multiple inherited components require richer rule data but can fit the same primary family assignment task.",
        "deskReview": {
          "candidate": "dual-surname-family-system",
          "parent": "family-name-planner",
          "action": "merge-proposed",
          "reason": "Multiple inherited components require richer rule data but can fit the same primary family assignment task.",
          "parentId": "nw-family-name-planner",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-family-surname-extinction",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Track ordered components and how children inherit them. Task B: Model succession choices when a fictional line has no designated heir. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-fictional-house-identity-system",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Task A: Track ordered components and how children inherit them. Task B: Define house membership and inherited personal components. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-found-family-address-system",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": true,
          "difference": "Task A: Track ordered components and how children inherit them. Task B: Design elective kinship terms without implying blood relationship. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track ordered components and how children inherit them",
        "outline": [
          "Explain the specific decision: Track ordered components and how children inherit them",
          "Define the applicable contract and limits for Dual surname family system",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track ordered components and how children inherit them; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track ordered components and how children inherit them",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Multiple inherited components require richer rule data but can fit the same primary family assignment task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:53",
      "profileSource": "data/profiles.json#kinship",
      "disposition": {
        "action": "merged",
        "parentId": "nw-family-name-planner",
        "reason": "Multiple inherited components require richer rule data but can fit the same primary family assignment task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-cast-initial-collision-repair",
      "slug": "cast-initial-collision-repair",
      "name": "Cast initial collision repair",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-initial-collision-repair/",
        "ja": "/ja/tools/cast-initial-collision-repair/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Propose minimal revisions where abbreviated labels collide",
      "task": "Propose minimal revisions where abbreviated labels collide",
      "searchIntent": {
        "primary": "Complete the task: Propose minimal revisions where abbreviated labels collide",
        "queryHypothesis": "cast initial collision repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to propose minimal revisions where abbreviated labels collide?",
        "When should cast initial collision repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Propose minimal revisions where abbreviated labels collide",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Propose minimal revisions where abbreviated labels collide. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Ensemble name separation. Initial comparison is one collision view, not a new user task.",
        "deskReview": {
          "candidate": "cast-initial-collision-repair",
          "parent": "ensemble-name-separation",
          "action": "merge-proposed",
          "reason": "Initial comparison is one collision view, not a new user task.",
          "parentId": "nw-ensemble-name-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-cast-nickname-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Propose minimal revisions where abbreviated labels collide. Task B: Audit the short forms readers encounter in dialogue. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-sound-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Propose minimal revisions where abbreviated labels collide. Task B: Repair author confirmed pronunciation collisions with locked names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-visual-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Propose minimal revisions where abbreviated labels collide. Task B: Compare rendered letterforms rather than spelling distance alone. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Propose minimal revisions where abbreviated labels collide",
        "outline": [
          "Explain the specific decision: Propose minimal revisions where abbreviated labels collide",
          "Define the applicable contract and limits for Cast initial collision repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Propose minimal revisions where abbreviated labels collide; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Propose minimal revisions where abbreviated labels collide",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Initial comparison is one collision view, not a new user task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:115",
      "profileSource": "data/profiles.json#ensemble",
      "disposition": {
        "action": "merged",
        "parentId": "nw-ensemble-name-separation",
        "reason": "Initial comparison is one collision view, not a new user task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-cast-nickname-collision-repair",
      "slug": "cast-nickname-collision-repair",
      "name": "Cast nickname collision repair",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-nickname-collision-repair/",
        "ja": "/ja/tools/cast-nickname-collision-repair/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Audit the short forms readers encounter in dialogue",
      "task": "Audit the short forms readers encounter in dialogue",
      "searchIntent": {
        "primary": "Complete the task: Audit the short forms readers encounter in dialogue",
        "queryHypothesis": "cast nickname collision repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to audit the short forms readers encounter in dialogue?",
        "When should cast nickname collision repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Audit the short forms readers encounter in dialogue",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Audit the short forms readers encounter in dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Ensemble name separation. Short-form collisions belong inside the group comparison data model.",
        "deskReview": {
          "candidate": "cast-nickname-collision-repair",
          "parent": "ensemble-name-separation",
          "action": "merge-proposed",
          "reason": "Short-form collisions belong inside the group comparison data model.",
          "parentId": "nw-ensemble-name-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-audio-nickname-confusion-test",
          "title": 0.14285714285714285,
          "task": 0.25,
          "score": 0.2125,
          "sharedProfile": false,
          "difference": "Task A: Audit the short forms readers encounter in dialogue. Task B: Compare short forms in a supplied scene recording. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-initial-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Audit the short forms readers encounter in dialogue. Task B: Propose minimal revisions where abbreviated labels collide. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-sound-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Audit the short forms readers encounter in dialogue. Task B: Repair author confirmed pronunciation collisions with locked names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Audit the short forms readers encounter in dialogue",
        "outline": [
          "Explain the specific decision: Audit the short forms readers encounter in dialogue",
          "Define the applicable contract and limits for Cast nickname collision repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Audit the short forms readers encounter in dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Audit the short forms readers encounter in dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Short-form collisions belong inside the group comparison data model."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:118",
      "profileSource": "data/profiles.json#ensemble",
      "disposition": {
        "action": "merged",
        "parentId": "nw-ensemble-name-separation",
        "reason": "Short-form collisions belong inside the group comparison data model.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-cast-sound-collision-repair",
      "slug": "cast-sound-collision-repair",
      "name": "Cast sound collision repair",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-sound-collision-repair/",
        "ja": "/ja/tools/cast-sound-collision-repair/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Repair author confirmed pronunciation collisions with locked names",
      "task": "Repair author confirmed pronunciation collisions with locked names",
      "searchIntent": {
        "primary": "Complete the task: Repair author confirmed pronunciation collisions with locked names",
        "queryHypothesis": "cast sound collision repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to repair author confirmed pronunciation collisions with locked names?",
        "When should cast sound collision repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Repair author confirmed pronunciation collisions with locked names",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Repair author confirmed pronunciation collisions with locked names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Ensemble name separation. A sound component alone is a shared evaluation filter; a complete audio production workflow is separately testable.",
        "deskReview": {
          "candidate": "cast-sound-collision-repair",
          "parent": "ensemble-name-separation",
          "action": "merge-proposed",
          "reason": "A sound component alone is a shared evaluation filter; a complete audio production workflow is separately testable.",
          "parentId": "nw-ensemble-name-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-cast-initial-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Repair author confirmed pronunciation collisions with locked names. Task B: Propose minimal revisions where abbreviated labels collide. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-nickname-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Repair author confirmed pronunciation collisions with locked names. Task B: Audit the short forms readers encounter in dialogue. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-visual-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Repair author confirmed pronunciation collisions with locked names. Task B: Compare rendered letterforms rather than spelling distance alone. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Repair author confirmed pronunciation collisions with locked names",
        "outline": [
          "Explain the specific decision: Repair author confirmed pronunciation collisions with locked names",
          "Define the applicable contract and limits for Cast sound collision repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Repair author confirmed pronunciation collisions with locked names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Repair author confirmed pronunciation collisions with locked names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: A sound component alone is a shared evaluation filter; a complete audio production workflow is separately testable."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:116",
      "profileSource": "data/profiles.json#ensemble",
      "disposition": {
        "action": "merged",
        "parentId": "nw-ensemble-name-separation",
        "reason": "A sound component alone is a shared evaluation filter; a complete audio production workflow is separately testable.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-cast-visual-collision-repair",
      "slug": "cast-visual-collision-repair",
      "name": "Cast visual collision repair",
      "category": "ensemble",
      "urls": {
        "en": "/en/tools/cast-visual-collision-repair/",
        "ja": "/ja/tools/cast-visual-collision-repair/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "ensemble fiction and manga creators",
      "scenario": "Compare rendered letterforms rather than spelling distance alone",
      "task": "Compare rendered letterforms rather than spelling distance alone",
      "searchIntent": {
        "primary": "Complete the task: Compare rendered letterforms rather than spelling distance alone",
        "queryHypothesis": "cast visual collision repair",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare rendered letterforms rather than spelling distance alone?",
        "When should cast visual collision repair be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "cast with stable IDs: keep people distinct",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene cooccurrence: weight relevant collisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved pronunciations: avoid guessed sound",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance"
      ],
      "requiredData": [
        {
          "description": "cast and scene graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "author approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "rendered font measurements",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare rendered letterforms rather than spelling distance alone",
        "compare actual short forms as well as full names",
        "weight similarity by scene proximity and narrative importance",
        "Proposed category workflow: cast import → pair review → minimal edits → scene test",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pairwise collision table",
        "minimal revision options",
        "reader test scene packet"
      ],
      "capabilities": [
        "freeze accepted names while repairing nearby collisions",
        "compare both visual and approved spoken forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare rendered letterforms rather than spelling distance alone. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Ensemble name separation. Visual similarity is an evaluation axis unless a distinct production artifact and workflow are demonstrated.",
        "deskReview": {
          "candidate": "cast-visual-collision-repair",
          "parent": "ensemble-name-separation",
          "action": "merge-proposed",
          "reason": "Visual similarity is an evaluation axis unless a distinct production artifact and workflow are demonstrated.",
          "parentId": "nw-ensemble-name-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-cast-initial-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Compare rendered letterforms rather than spelling distance alone. Task B: Propose minimal revisions where abbreviated labels collide. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-nickname-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Compare rendered letterforms rather than spelling distance alone. Task B: Audit the short forms readers encounter in dialogue. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-sound-collision-repair",
          "title": 0.6,
          "task": 0,
          "score": 0.21,
          "sharedProfile": true,
          "difference": "Task A: Compare rendered letterforms rather than spelling distance alone. Task B: Repair author confirmed pronunciation collisions with locked names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare rendered letterforms rather than spelling distance alone",
        "outline": [
          "Explain the specific decision: Compare rendered letterforms rather than spelling distance alone",
          "Define the applicable contract and limits for Cast visual collision repair",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare rendered letterforms rather than spelling distance alone; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare rendered letterforms rather than spelling distance alone",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Visual similarity is an evaluation axis unless a distinct production artifact and workflow are demonstrated."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:117",
      "profileSource": "data/profiles.json#ensemble",
      "disposition": {
        "action": "merged",
        "parentId": "nw-ensemble-name-separation",
        "reason": "Visual similarity is an evaluation axis unless a distinct production artifact and workflow are demonstrated.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-alias-reveal-timing",
      "slug": "alias-reveal-timing",
      "name": "Alias reveal timing",
      "category": "identities",
      "urls": {
        "en": "/en/tools/alias-reveal-timing/",
        "ja": "/ja/tools/alias-reveal-timing/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Schedule forms of reference before and after a reveal",
      "task": "Schedule forms of reference before and after a reveal",
      "searchIntent": {
        "primary": "Complete the task: Schedule forms of reference before and after a reveal",
        "queryHypothesis": "alias reveal timing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to schedule forms of reference before and after a reveal?",
        "When should alias reveal timing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Schedule forms of reference before and after a reveal",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Schedule forms of reference before and after a reveal. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: True name alias bridge. Reveal time is already part of the bridge tool's knowledge-state contract.",
        "deskReview": {
          "candidate": "alias-reveal-timing",
          "parent": "true-name-alias-bridge",
          "action": "merge-proposed",
          "reason": "Reveal time is already part of the bridge tool's knowledge-state contract.",
          "parentId": "nw-true-name-alias-bridge",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-alias-reveal-scene-exercise",
          "title": 0.4,
          "task": 0.2,
          "score": 0.27,
          "sharedProfile": false,
          "difference": "Task A: Schedule forms of reference before and after a reveal. Task B: Compare fair clue placement before a controlled reveal. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-live-roleplay-alias-reveal",
          "title": 0.4,
          "task": 0.08333333333333333,
          "score": 0.19416666666666665,
          "sharedProfile": false,
          "difference": "Task A: Schedule forms of reference before and after a reveal. Task B: Schedule badge or roster changes at an agreed story event. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-alias-reveal-comprehension",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": false,
          "difference": "Task A: Schedule forms of reference before and after a reveal. Task B: Test whether readers understand an identity connection at the intended moment. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Schedule forms of reference before and after a reveal",
        "outline": [
          "Explain the specific decision: Schedule forms of reference before and after a reveal",
          "Define the applicable contract and limits for Alias reveal timing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Schedule forms of reference before and after a reveal; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Schedule forms of reference before and after a reveal",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Reveal time is already part of the bridge tool's knowledge-state contract."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:134",
      "profileSource": "data/profiles.json#identities",
      "disposition": {
        "action": "merged",
        "parentId": "nw-true-name-alias-bridge",
        "reason": "Reveal time is already part of the bridge tool's knowledge-state contract.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-alias-knowledge-ledger",
      "slug": "alias-knowledge-ledger",
      "name": "Alias knowledge ledger",
      "category": "identities",
      "urls": {
        "en": "/en/tools/alias-knowledge-ledger/",
        "ja": "/ja/tools/alias-knowledge-ledger/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Track who knows each identity at each scene",
      "task": "Track who knows each identity at each scene",
      "searchIntent": {
        "primary": "Complete the task: Track who knows each identity at each scene",
        "queryHypothesis": "alias knowledge ledger",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to track who knows each identity at each scene?",
        "When should alias knowledge ledger be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Track who knows each identity at each scene",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Track who knows each identity at each scene. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: True name alias bridge. The proposed bridge tool needs this ledger to function at all; extracting it risks fragmenting one task.",
        "deskReview": {
          "candidate": "alias-knowledge-ledger",
          "parent": "true-name-alias-bridge",
          "action": "merge-proposed",
          "reason": "The proposed bridge tool needs this ledger to function at all; extracting it risks fragmenting one task.",
          "parentId": "nw-true-name-alias-bridge",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-time-loop-remembered-names",
          "title": 0,
          "task": 0.3333333333333333,
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Task A: Track who knows each identity at each scene. Task B: Track who remembers which identity after each reset. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-alias-continuity",
          "title": 0.2,
          "task": 0.18181818181818182,
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Task A: Track who knows each identity at each scene. Task B: Check a dated reference ledger against scene identity states. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Track who knows each identity at each scene. Task B: Track knowledge of identity across a mistaken identity scene. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Track who knows each identity at each scene",
        "outline": [
          "Explain the specific decision: Track who knows each identity at each scene",
          "Define the applicable contract and limits for Alias knowledge ledger",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Track who knows each identity at each scene; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Track who knows each identity at each scene",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: The proposed bridge tool needs this ledger to function at all; extracting it risks fragmenting one task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:133",
      "profileSource": "data/profiles.json#identities",
      "disposition": {
        "action": "merged",
        "parentId": "nw-true-name-alias-bridge",
        "reason": "The proposed bridge tool needs this ledger to function at all; extracting it risks fragmenting one task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-first-name-transition-scene",
      "slug": "first-name-transition-scene",
      "name": "First name transition scene",
      "category": "address",
      "urls": {
        "en": "/en/tools/first-name-transition-scene/",
        "ja": "/ja/tools/first-name-transition-scene/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Mark the relationship event that licenses a less formal name",
      "task": "Mark the relationship event that licenses a less formal name",
      "searchIntent": {
        "primary": "Complete the task: Mark the relationship event that licenses a less formal name",
        "queryHypothesis": "first name transition scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to mark the relationship event that licenses a less formal name?",
        "When should first name transition scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Mark the relationship event that licenses a less formal name",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Mark the relationship event that licenses a less formal name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "merge-proposed: Address relationship graph. One transition event is an address graph preset plus an instructional scene.",
        "deskReview": {
          "candidate": "first-name-transition-scene",
          "parent": "address-relationship-graph",
          "action": "merge-proposed",
          "reason": "One transition event is an address graph preset plus an instructional scene.",
          "parentId": "nw-address-relationship-graph",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-scene-exercise",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Task A: Mark the relationship event that licenses a less formal name. Task B: Show a shared surname creating a specific relationship inference. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-arc-scene-checklist",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Task A: Mark the relationship event that licenses a less formal name. Task B: Link every address change to an earned story event. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Task A: Mark the relationship event that licenses a less formal name. Task B: Show how a remembered form reveals relationship history. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Mark the relationship event that licenses a less formal name",
        "outline": [
          "Explain the specific decision: Mark the relationship event that licenses a less formal name",
          "Define the applicable contract and limits for First name transition scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Mark the relationship event that licenses a less formal name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Mark the relationship event that licenses a less formal name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "merge-proposed: One transition event is an address graph preset plus an instructional scene."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:174",
      "profileSource": "data/profiles.json#address",
      "disposition": {
        "action": "merged",
        "parentId": "nw-address-relationship-graph",
        "reason": "One transition event is an address graph preset plus an instructional scene.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-surname-to-nickname-transition",
      "slug": "surname-to-nickname-transition",
      "name": "Surname to nickname transition",
      "category": "address",
      "urls": {
        "en": "/en/tools/surname-to-nickname-transition/",
        "ja": "/ja/tools/surname-to-nickname-transition/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Trace acceptance and resistance through dialogue",
      "task": "Trace acceptance and resistance through dialogue",
      "searchIntent": {
        "primary": "Complete the task: Trace acceptance and resistance through dialogue",
        "queryHypothesis": "surname to nickname transition",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to trace acceptance and resistance through dialogue?",
        "When should surname to nickname transition be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Trace acceptance and resistance through dialogue",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Trace acceptance and resistance through dialogue. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "merge-proposed: Address relationship graph. The same permission transition task differs only by selected address forms.",
        "deskReview": {
          "candidate": "surname-to-nickname-transition",
          "parent": "address-relationship-graph",
          "action": "merge-proposed",
          "reason": "The same permission transition task differs only by selected address forms.",
          "parentId": "nw-address-relationship-graph",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-nickname-consent-scene-exercise",
          "title": 0.16666666666666666,
          "task": 0.375,
          "score": 0.30208333333333337,
          "sharedProfile": false,
          "difference": "Task A: Trace acceptance and resistance through dialogue. Task B: Show acceptance and refusal through dialogue consequences. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-name-change-impact",
          "title": 0,
          "task": 0.3333333333333333,
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Task A: Trace acceptance and resistance through dialogue. Task B: Trace edits through dialogue, art props and credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-accepts-unwanted-nickname",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Trace acceptance and resistance through dialogue. Task B: Trace changed meaning and remaining boundaries. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Trace acceptance and resistance through dialogue",
        "outline": [
          "Explain the specific decision: Trace acceptance and resistance through dialogue",
          "Define the applicable contract and limits for Surname to nickname transition",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Trace acceptance and resistance through dialogue; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Trace acceptance and resistance through dialogue",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "merge-proposed: The same permission transition task differs only by selected address forms."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:175",
      "profileSource": "data/profiles.json#address",
      "disposition": {
        "action": "merged",
        "parentId": "nw-address-relationship-graph",
        "reason": "The same permission transition task differs only by selected address forms.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-full-name-reprimand",
      "slug": "full-name-reprimand",
      "name": "Full name reprimand",
      "category": "address",
      "urls": {
        "en": "/en/tools/full-name-reprimand/",
        "ja": "/ja/tools/full-name-reprimand/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "dialogue writers and manga letterers",
      "scenario": "Contrast usual address with an exceptional full name usage",
      "task": "Contrast usual address with an exceptional full name usage",
      "searchIntent": {
        "primary": "Complete the task: Contrast usual address with an exceptional full name usage",
        "queryHypothesis": "full name reprimand",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast usual address with an exceptional full name usage?",
        "When should full name reprimand be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "speaker listener graph: resolve directed relationships",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene date: select relationship state",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "address permissions: model consent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "address is directional rather than a person wide property",
        "changes require an authored relationship event"
      ],
      "requiredData": [
        {
          "description": "author approved address forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "relationship milestones",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "language specific reviewed style policy",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast usual address with an exceptional full name usage",
        "address is directional rather than a person wide property",
        "changes require an authored relationship event",
        "Proposed category workflow: relationship map → permissions → dialogue rehearsal → consistency review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speaker specific forms",
        "unearned familiarity warnings",
        "dialogue alternatives with implications"
      ],
      "capabilities": [
        "compare both directions of an unequal relationship",
        "replay address changes across a scene sequence"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast usual address with an exceptional full name usage. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "merge-proposed: Address relationship graph. A full-name reprimand is a context rule and story example, not a distinct primary operation.",
        "deskReview": {
          "candidate": "full-name-reprimand",
          "parent": "address-relationship-graph",
          "action": "merge-proposed",
          "reason": "A full-name reprimand is a context rule and story example, not a distinct primary operation.",
          "parentId": "nw-address-relationship-graph",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-fictional-ceremonial-full-style",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Contrast usual address with an exceptional full name usage. Task B: Construct long styles with a short reference policy. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-full-name-rhythm",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Contrast usual address with an exceptional full name usage. Task B: Compare mora patterns using author confirmed kana. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-full-name-overuse",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Contrast usual address with an exceptional full name usage. Task B: Flag repetitions using configurable editorial context. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast usual address with an exceptional full name usage",
        "outline": [
          "Explain the specific decision: Contrast usual address with an exceptional full name usage",
          "Define the applicable contract and limits for Full name reprimand",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast usual address with an exceptional full name usage; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast usual address with an exceptional full name usage",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "merge-proposed: A full-name reprimand is a context rule and story example, not a distinct primary operation."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:198",
      "profileSource": "data/profiles.json#address",
      "disposition": {
        "action": "merged",
        "parentId": "nw-address-relationship-graph",
        "reason": "A full-name reprimand is a context rule and story example, not a distinct primary operation.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-initials-decision",
      "slug": "pen-name-initials-decision",
      "name": "Pen name initials decision",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-initials-decision/",
        "ja": "/ja/tools/pen-name-initials-decision/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare initials, expansion and spoken mention tradeoffs",
      "task": "Compare initials, expansion and spoken mention tradeoffs",
      "searchIntent": {
        "primary": "Complete the task: Compare initials, expansion and spoken mention tradeoffs",
        "queryHypothesis": "pen name initials decision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare initials, expansion and spoken mention tradeoffs?",
        "When should pen name initials decision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare initials, expansion and spoken mention tradeoffs",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare initials, expansion and spoken mention tradeoffs. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Pen name designer. Initial display is a candidate presentation option.",
        "deskReview": {
          "candidate": "pen-name-initials-decision",
          "parent": "pen-name-designer",
          "action": "merge-proposed",
          "reason": "Initial display is a candidate presentation option.",
          "parentId": "nw-pen-name-designer",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-candidate-decision",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Compare initials, expansion and spoken mention tradeoffs. Task B: Compare a fixed shortlist using published heuristic criteria. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-pronunciation",
          "title": 0.25,
          "task": 0.1,
          "score": 0.1525,
          "sharedProfile": true,
          "difference": "Task A: Compare initials, expansion and spoken mention tradeoffs. Task B: Produce an author approved spoken introduction and ambiguity notes. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-audio-introduction",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Task A: Compare initials, expansion and spoken mention tradeoffs. Task B: Test host introductions and spoken acknowledgments. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare initials, expansion and spoken mention tradeoffs",
        "outline": [
          "Explain the specific decision: Compare initials, expansion and spoken mention tradeoffs",
          "Define the applicable contract and limits for Pen name initials decision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare initials, expansion and spoken mention tradeoffs; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare initials, expansion and spoken mention tradeoffs",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Initial display is a candidate presentation option."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:224",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-designer",
        "reason": "Initial display is a candidate presentation option.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-mononym-author-credit",
      "slug": "mononym-author-credit",
      "name": "Mononym author credit",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/mononym-author-credit/",
        "ja": "/ja/tools/mononym-author-credit/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Evaluate attribution clarity when a creator uses a single name",
      "task": "Evaluate attribution clarity when a creator uses a single name",
      "searchIntent": {
        "primary": "Complete the task: Evaluate attribution clarity when a creator uses a single name",
        "queryHypothesis": "mononym author credit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to evaluate attribution clarity when a creator uses a single name?",
        "When should mononym author credit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Evaluate attribution clarity when a creator uses a single name",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Evaluate attribution clarity when a creator uses a single name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Pen name designer. A one-part author name changes structure and review questions, but the main byline decision remains the same.",
        "deskReview": {
          "candidate": "mononym-author-credit",
          "parent": "pen-name-designer",
          "action": "merge-proposed",
          "reason": "A one-part author name changes structure and review questions, but the main byline decision remains the same.",
          "parentId": "nw-pen-name-designer",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-mononym-character-design",
          "title": 0.25,
          "task": 0.09090909090909091,
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Task A: Evaluate attribution clarity when a creator uses a single name. Task B: Maintain referential clarity for a character with one public name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-comic-cover-character-credit",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Evaluate attribution clarity when a creator uses a single name. Task B: Separate character names from creator and actor credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-collective-author-credit-governance",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Evaluate attribution clarity when a creator uses a single name. Task B: Record how members join, leave and retain past credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Evaluate attribution clarity when a creator uses a single name",
        "outline": [
          "Explain the specific decision: Evaluate attribution clarity when a creator uses a single name",
          "Define the applicable contract and limits for Mononym author credit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Evaluate attribution clarity when a creator uses a single name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Evaluate attribution clarity when a creator uses a single name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: A one-part author name changes structure and review questions, but the main byline decision remains the same."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:225",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-designer",
        "reason": "A one-part author name changes structure and review questions, but the main byline decision remains the same.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-typography-comparison",
      "slug": "pen-name-typography-comparison",
      "name": "Pen name typography comparison",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-typography-comparison/",
        "ja": "/ja/tools/pen-name-typography-comparison/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare type treatment without inferring trademark clearance",
      "task": "Compare type treatment without inferring trademark clearance",
      "searchIntent": {
        "primary": "Complete the task: Compare type treatment without inferring trademark clearance",
        "queryHypothesis": "pen name typography comparison",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare type treatment without inferring trademark clearance?",
        "When should pen name typography comparison be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare type treatment without inferring trademark clearance",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare type treatment without inferring trademark clearance. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Author byline preview. Typeface selection and size belong in one byline proof surface.",
        "deskReview": {
          "candidate": "pen-name-typography-comparison",
          "parent": "author-byline-preview",
          "action": "merge-proposed",
          "reason": "Typeface selection and size belong in one byline proof surface.",
          "parentId": "nw-author-byline-preview",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-accessibility-comparison",
          "title": 0.25,
          "task": 0.09090909090909091,
          "score": 0.1465909090909091,
          "sharedProfile": false,
          "difference": "Task A: Compare type treatment without inferring trademark clearance. Task B: Record participant specific difficulties without generalizing to a diagnosis. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Compare type treatment without inferring trademark clearance. Task B: Record the scope of external checks without clearance claims. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-genre-positioning",
          "title": 0.2,
          "task": 0.08333333333333333,
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Task A: Compare type treatment without inferring trademark clearance. Task B: Compare intended shelf signals without guaranteeing audience response. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare type treatment without inferring trademark clearance",
        "outline": [
          "Explain the specific decision: Compare type treatment without inferring trademark clearance",
          "Define the applicable contract and limits for Pen name typography comparison",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare type treatment without inferring trademark clearance; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare type treatment without inferring trademark clearance",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Typeface selection and size belong in one byline proof surface."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:237",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-designer",
        "reason": "Typeface selection and size belong in one byline proof surface.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published",
        "parentHistory": [
          "nw-author-byline-preview"
        ]
      }
    },
    {
      "id": "nw-pen-name-domain-checklist",
      "slug": "pen-name-domain-checklist",
      "name": "Pen name domain checklist",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-domain-checklist/",
        "ja": "/ja/tools/pen-name-domain-checklist/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Record domain checks with time and scope rather than promise availability",
      "task": "Record domain checks with time and scope rather than promise availability",
      "searchIntent": {
        "primary": "Complete the task: Record domain checks with time and scope rather than promise availability",
        "queryHypothesis": "pen name domain checklist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record domain checks with time and scope rather than promise availability?",
        "When should pen name domain checklist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record domain checks with time and scope rather than promise availability",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record domain checks with time and scope rather than promise availability. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Pen name search collision log. Domain checking is one external check category and cannot establish global clearance.",
        "deskReview": {
          "candidate": "pen-name-domain-checklist",
          "parent": "pen-name-search-collision-log",
          "action": "merge-proposed",
          "reason": "Domain checking is one external check category and cannot establish global clearance.",
          "parentId": "nw-pen-name-search-collision-log",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-personal-safety-checklist",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Record domain checks with time and scope rather than promise availability. Task B: Minimize volunteered identifying details without promising anonymity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-negative-association-review",
          "title": 0.16666666666666666,
          "task": 0.08333333333333333,
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Task A: Record domain checks with time and scope rather than promise availability. Task B: Structure human checks for unintended associations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-name-trademark-check-log",
          "title": 0,
          "task": 0.16666666666666666,
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Task A: Record domain checks with time and scope rather than promise availability. Task B: Record the scope of external checks without clearance claims. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record domain checks with time and scope rather than promise availability",
        "outline": [
          "Explain the specific decision: Record domain checks with time and scope rather than promise availability",
          "Define the applicable contract and limits for Pen name domain checklist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record domain checks with time and scope rather than promise availability; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record domain checks with time and scope rather than promise availability",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Domain checking is one external check category and cannot establish global clearance."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:229",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-search-collision-log",
        "reason": "Domain checking is one external check category and cannot establish global clearance.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-punctuation-fallback",
      "slug": "pen-name-punctuation-fallback",
      "name": "Pen name punctuation fallback",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-punctuation-fallback/",
        "ja": "/ja/tools/pen-name-punctuation-fallback/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Preserve attribution when a platform strips punctuation",
      "task": "Preserve attribution when a platform strips punctuation",
      "searchIntent": {
        "primary": "Complete the task: Preserve attribution when a platform strips punctuation",
        "queryHypothesis": "pen name punctuation fallback",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve attribution when a platform strips punctuation?",
        "When should pen name punctuation fallback be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve attribution when a platform strips punctuation",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve attribution when a platform strips punctuation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Pen name designer. A platform fallback is a shared presentation constraint with a scope note.",
        "deskReview": {
          "candidate": "pen-name-punctuation-fallback",
          "parent": "pen-name-designer",
          "action": "merge-proposed",
          "reason": "A platform fallback is a shared presentation constraint with a scope note.",
          "parentId": "nw-pen-name-designer",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-diacritic-fallback",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Preserve attribution when a platform strips punctuation. Task B: Explain the cost of a fallback spelling in credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-social-handle-mapping",
          "title": 0.16666666666666666,
          "task": 0.125,
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Task A: Preserve attribution when a platform strips punctuation. Task B: Keep display name and platform identifier decisions separate. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-mononym-author-credit",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": true,
          "difference": "Task A: Preserve attribution when a platform strips punctuation. Task B: Evaluate attribution clarity when a creator uses a single name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve attribution when a platform strips punctuation",
        "outline": [
          "Explain the specific decision: Preserve attribution when a platform strips punctuation",
          "Define the applicable contract and limits for Pen name punctuation fallback",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve attribution when a platform strips punctuation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve attribution when a platform strips punctuation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: A platform fallback is a shared presentation constraint with a scope note."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:235",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-designer",
        "reason": "A platform fallback is a shared presentation constraint with a scope note.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-diacritic-fallback",
      "slug": "pen-name-diacritic-fallback",
      "name": "Pen name diacritic fallback",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-diacritic-fallback/",
        "ja": "/ja/tools/pen-name-diacritic-fallback/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Explain the cost of a fallback spelling in credits",
      "task": "Explain the cost of a fallback spelling in credits",
      "searchIntent": {
        "primary": "Complete the task: Explain the cost of a fallback spelling in credits",
        "queryHypothesis": "pen name diacritic fallback",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain the cost of a fallback spelling in credits?",
        "When should pen name diacritic fallback be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain the cost of a fallback spelling in credits",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain the cost of a fallback spelling in credits. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Pen name designer. Diacritic fallback belongs alongside original display and platform-specific alternatives.",
        "deskReview": {
          "candidate": "pen-name-diacritic-fallback",
          "parent": "pen-name-designer",
          "action": "merge-proposed",
          "reason": "Diacritic fallback belongs alongside original display and platform-specific alternatives.",
          "parentId": "nw-pen-name-designer",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-punctuation-fallback",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Explain the cost of a fallback spelling in credits. Task B: Preserve attribution when a platform strips punctuation. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-uncommon-character-fallback",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Explain the cost of a fallback spelling in credits. Task B: Keep original glyph, fallback and explanation distinct. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Task A: Explain the cost of a fallback spelling in credits. Task B: Store approved kana and romanized credits alongside the name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain the cost of a fallback spelling in credits",
        "outline": [
          "Explain the specific decision: Explain the cost of a fallback spelling in credits",
          "Define the applicable contract and limits for Pen name diacritic fallback",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain the cost of a fallback spelling in credits; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain the cost of a fallback spelling in credits",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Diacritic fallback belongs alongside original display and platform-specific alternatives."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:234",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged",
        "parentId": "nw-pen-name-designer",
        "reason": "Diacritic fallback belongs alongside original display and platform-specific alternatives.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-small-kana-audit",
      "slug": "japanese-name-small-kana-audit",
      "name": "Japanese name small kana audit",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-small-kana-audit/",
        "ja": "/ja/tools/japanese-name-small-kana-audit/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Preserve contracted sounds in approved reading data",
      "task": "Preserve contracted sounds in approved reading data",
      "searchIntent": {
        "primary": "Complete the task: Preserve contracted sounds in approved reading data",
        "queryHypothesis": "japanese name small kana audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve contracted sounds in approved reading data?",
        "When should japanese name small kana audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve contracted sounds in approved reading data",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve contracted sounds in approved reading data. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Japanese character name record. Preserving small kana is a validation rule for approved reading records.",
        "deskReview": {
          "candidate": "japanese-name-small-kana-audit",
          "parent": "japanese-character-name-record",
          "action": "merge-proposed",
          "reason": "Preserving small kana is a validation rule for approved reading records.",
          "parentId": "nw-japanese-character-name-record",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-invented-reading-disclosure",
          "title": 0.14285714285714285,
          "task": 0.14285714285714285,
          "score": 0.14285714285714285,
          "sharedProfile": true,
          "difference": "Task A: Preserve contracted sounds in approved reading data. Task B: Label an author invented reading as fictional. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-difficult-name-introduction",
          "title": 0.16666666666666666,
          "task": 0.125,
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Task A: Preserve contracted sounds in approved reading data. Task B: Compare staged reading support against renaming. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-vertical-setting",
          "title": 0.16666666666666666,
          "task": 0.125,
          "score": 0.13958333333333334,
          "sharedProfile": true,
          "difference": "Task A: Preserve contracted sounds in approved reading data. Task B: Test name and reading in vertical text layouts. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve contracted sounds in approved reading data",
        "outline": [
          "Explain the specific decision: Preserve contracted sounds in approved reading data",
          "Define the applicable contract and limits for Japanese name small kana audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve contracted sounds in approved reading data; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve contracted sounds in approved reading data",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Preserving small kana is a validation rule for approved reading records."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:287",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged",
        "parentId": "nw-japanese-character-name-record",
        "reason": "Preserving small kana is a validation rule for approved reading records.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-fact-versus-association",
      "slug": "japanese-name-fact-versus-association",
      "name": "Japanese name fact versus association",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-fact-versus-association/",
        "ja": "/ja/tools/japanese-name-fact-versus-association/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Annotate each explanation as sourced fact or creative interpretation",
      "task": "Annotate each explanation as sourced fact or creative interpretation",
      "searchIntent": {
        "primary": "Complete the task: Annotate each explanation as sourced fact or creative interpretation",
        "queryHypothesis": "japanese name fact versus association",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to annotate each explanation as sourced fact or creative interpretation?",
        "When should japanese name fact versus association be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Annotate each explanation as sourced fact or creative interpretation",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Annotate each explanation as sourced fact or creative interpretation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Japanese character name record. Fact and creative interpretation labels are mandatory evidence fields, not standalone naming tasks.",
        "deskReview": {
          "candidate": "japanese-name-fact-versus-association",
          "parent": "japanese-character-name-record",
          "action": "merge-proposed",
          "reason": "Fact and creative interpretation labels are mandatory evidence fields, not standalone naming tasks.",
          "parentId": "nw-japanese-character-name-record",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-character-name-kanji-evidence",
          "title": 0.16666666666666666,
          "task": 0.09090909090909091,
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Task A: Annotate each explanation as sourced fact or creative interpretation. Task B: Track dictionary evidence separately from creative symbolism. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-fictional-legal-name-note",
          "title": 0.16666666666666666,
          "task": 0.09090909090909091,
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Task A: Annotate each explanation as sourced fact or creative interpretation. Task B: Separate creative choices from real name registration advice. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-uncommon-character-fallback",
          "title": 0.16666666666666666,
          "task": 0.09090909090909091,
          "score": 0.11742424242424243,
          "sharedProfile": true,
          "difference": "Task A: Annotate each explanation as sourced fact or creative interpretation. Task B: Keep original glyph, fallback and explanation distinct. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Annotate each explanation as sourced fact or creative interpretation",
        "outline": [
          "Explain the specific decision: Annotate each explanation as sourced fact or creative interpretation",
          "Define the applicable contract and limits for Japanese name fact versus association",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Annotate each explanation as sourced fact or creative interpretation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Annotate each explanation as sourced fact or creative interpretation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Fact and creative interpretation labels are mandatory evidence fields, not standalone naming tasks."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:296",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged",
        "parentId": "nw-japanese-character-name-record",
        "reason": "Fact and creative interpretation labels are mandatory evidence fields, not standalone naming tasks.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-invented-reading-disclosure",
      "slug": "japanese-invented-reading-disclosure",
      "name": "Japanese invented reading disclosure",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-invented-reading-disclosure/",
        "ja": "/ja/tools/japanese-invented-reading-disclosure/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Label an author invented reading as fictional",
      "task": "Label an author invented reading as fictional",
      "searchIntent": {
        "primary": "Complete the task: Label an author invented reading as fictional",
        "queryHypothesis": "japanese invented reading disclosure",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to label an author invented reading as fictional?",
        "When should japanese invented reading disclosure be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Label an author invented reading as fictional",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Label an author invented reading as fictional. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Japanese character name record. Disclosure of invention must be a default rule, not an optional separate tool.",
        "deskReview": {
          "candidate": "japanese-invented-reading-disclosure",
          "parent": "japanese-character-name-record",
          "action": "merge-proposed",
          "reason": "Disclosure of invention must be a default rule, not an optional separate tool.",
          "parentId": "nw-japanese-character-name-record",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-given-name-reading-choice",
          "title": 0.3333333333333333,
          "task": 0.125,
          "score": 0.19791666666666666,
          "sharedProfile": true,
          "difference": "Task A: Label an author invented reading as fictional. Task B: Attach evidence to each candidate reading. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-screen-reader-brief",
          "title": 0.14285714285714285,
          "task": 0.2222222222222222,
          "score": 0.19444444444444442,
          "sharedProfile": true,
          "difference": "Task A: Label an author invented reading as fictional. Task B: Provide author approved reading without relying on glyph guessing. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-cast-reading-collision",
          "title": 0.3333333333333333,
          "task": 0.1111111111111111,
          "score": 0.18888888888888888,
          "sharedProfile": true,
          "difference": "Task A: Label an author invented reading as fictional. Task B: Detect different written names with the same confirmed reading. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Label an author invented reading as fictional",
        "outline": [
          "Explain the specific decision: Label an author invented reading as fictional",
          "Define the applicable contract and limits for Japanese invented reading disclosure",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Label an author invented reading as fictional; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Label an author invented reading as fictional",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Disclosure of invention must be a default rule, not an optional separate tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:261",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged",
        "parentId": "nw-japanese-character-name-record",
        "reason": "Disclosure of invention must be a default rule, not an optional separate tool.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-plain-text-export",
      "slug": "japanese-name-plain-text-export",
      "name": "Japanese name plain text export",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-plain-text-export/",
        "ja": "/ja/tools/japanese-name-plain-text-export/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Preserve readings when ruby markup is unavailable",
      "task": "Preserve readings when ruby markup is unavailable",
      "searchIntent": {
        "primary": "Complete the task: Preserve readings when ruby markup is unavailable",
        "queryHypothesis": "japanese name plain text export",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve readings when ruby markup is unavailable?",
        "When should japanese name plain text export be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve readings when ruby markup is unavailable",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve readings when ruby markup is unavailable. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Japanese character name record. Plain-text output is an export format from the same approved record.",
        "deskReview": {
          "candidate": "japanese-name-plain-text-export",
          "parent": "japanese-character-name-record",
          "action": "merge-proposed",
          "reason": "Plain-text output is an export format from the same approved record.",
          "parentId": "nw-japanese-character-name-record",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-comic-off-panel-name-reference",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Preserve readings when ruby markup is unavailable. Task B: Maintain clarity when a speaker or listener is unseen. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-locale-fallback-names",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Preserve readings when ruby markup is unavailable. Task B: Define a reviewed fallback when a locale is incomplete. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-same-writing-different-reading",
          "title": 0.125,
          "task": 0.1111111111111111,
          "score": 0.11597222222222221,
          "sharedProfile": true,
          "difference": "Task A: Preserve readings when ruby markup is unavailable. Task B: Require explicit readings and ambiguity disclosures. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve readings when ruby markup is unavailable",
        "outline": [
          "Explain the specific decision: Preserve readings when ruby markup is unavailable",
          "Define the applicable contract and limits for Japanese name plain text export",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve readings when ruby markup is unavailable; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve readings when ruby markup is unavailable",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Plain-text output is an export format from the same approved record."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:292",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged",
        "parentId": "nw-japanese-character-name-record",
        "reason": "Plain-text output is an export format from the same approved record.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-uncommon-character-fallback",
      "slug": "japanese-name-uncommon-character-fallback",
      "name": "Japanese name uncommon character fallback",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-uncommon-character-fallback/",
        "ja": "/ja/tools/japanese-name-uncommon-character-fallback/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Keep original glyph, fallback and explanation distinct",
      "task": "Keep original glyph, fallback and explanation distinct",
      "searchIntent": {
        "primary": "Complete the task: Keep original glyph, fallback and explanation distinct",
        "queryHypothesis": "japanese name uncommon character fallback",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to keep original glyph, fallback and explanation distinct?",
        "When should japanese name uncommon character fallback be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Keep original glyph, fallback and explanation distinct",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Keep original glyph, fallback and explanation distinct. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "redesign-proposed: Japanese name glyph variant continuity. Uncommon glyph handling and historical variants may overlap. Redesign one evidence-backed glyph continuity workflow before considering independent pages.",
        "deskReview": {
          "candidate": "japanese-name-uncommon-character-fallback",
          "parent": "japanese-name-glyph-variant-continuity",
          "action": "redesign-proposed",
          "reason": "Uncommon glyph handling and historical variants may overlap. Redesign one evidence-backed glyph continuity workflow before considering independent pages.",
          "parentId": "nw-japanese-name-glyph-variant-continuity",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-historical-obsolete-glyph-handling",
          "title": 0,
          "task": 0.2857142857142857,
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Task A: Keep original glyph, fallback and explanation distinct. Task B: Preserve original and readable fallback separately. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-diacritic-fallback",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Keep original glyph, fallback and explanation distinct. Task B: Explain the cost of a fallback spelling in credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-locale-fallback-names",
          "title": 0.2,
          "task": 0.09090909090909091,
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Task A: Keep original glyph, fallback and explanation distinct. Task B: Define a reviewed fallback when a locale is incomplete. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Keep original glyph, fallback and explanation distinct",
        "outline": [
          "Explain the specific decision: Keep original glyph, fallback and explanation distinct",
          "Define the applicable contract and limits for Japanese name uncommon character fallback",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Keep original glyph, fallback and explanation distinct; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Keep original glyph, fallback and explanation distinct",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "redesign-proposed: Uncommon glyph handling and historical variants may overlap. Redesign one evidence-backed glyph continuity workflow before considering independent pages."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:289",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged-into-redesigned-parent",
        "parentId": "nw-japanese-name-glyph-variant-continuity",
        "reason": "Uncommon glyph handling and historical variants may overlap. Redesign one evidence-backed glyph continuity workflow before considering independent pages.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-localized-name-credits-reconciliation",
      "slug": "localized-name-credits-reconciliation",
      "name": "Localized name credits reconciliation",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-credits-reconciliation/",
        "ja": "/ja/tools/localized-name-credits-reconciliation/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Match creators and character credits across editions",
      "task": "Match creators and character credits across editions",
      "searchIntent": {
        "primary": "Complete the task: Match creators and character credits across editions",
        "queryHypothesis": "localized name credits reconciliation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to match creators and character credits across editions?",
        "When should localized name credits reconciliation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Match creators and character credits across editions",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Match creators and character credits across editions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Character localization name map. Credits are a target surface that already consumes the bilingual identity map.",
        "deskReview": {
          "candidate": "localized-name-credits-reconciliation",
          "parent": "character-localization-name-map",
          "action": "merge-proposed",
          "reason": "Credits are a target surface that already consumes the bilingual identity map.",
          "parentId": "nw-character-localization-name-map",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-localized-signature-consistency",
          "title": 0.2,
          "task": 0.2222222222222222,
          "score": 0.21444444444444444,
          "sharedProfile": true,
          "difference": "Task A: Match creators and character credits across editions. Task B: Keep a drawn signature recognizable across localized editions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-alias-reveal-parity",
          "title": 0.16666666666666666,
          "task": 0.2222222222222222,
          "score": 0.20277777777777775,
          "sharedProfile": true,
          "difference": "Task A: Match creators and character credits across editions. Task B: Keep clue timing comparable across language editions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-order-policy",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Match creators and character credits across editions. Task B: Keep display order consistent across narration and credits. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Match creators and character credits across editions",
        "outline": [
          "Explain the specific decision: Match creators and character credits across editions",
          "Define the applicable contract and limits for Localized name credits reconciliation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Match creators and character credits across editions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Match creators and character credits across editions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Credits are a target surface that already consumes the bilingual identity map."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:338",
      "profileSource": "data/profiles.json#localization",
      "disposition": {
        "action": "merged",
        "parentId": "nw-character-localization-name-map",
        "reason": "Credits are a target surface that already consumes the bilingual identity map.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-localized-name-typography-proof",
      "slug": "localized-name-typography-proof",
      "name": "Localized name typography proof",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-typography-proof/",
        "ja": "/ja/tools/localized-name-typography-proof/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Compare target fonts and actual grapheme rendering",
      "task": "Compare target fonts and actual grapheme rendering",
      "searchIntent": {
        "primary": "Complete the task: Compare target fonts and actual grapheme rendering",
        "queryHypothesis": "localized name typography proof",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare target fonts and actual grapheme rendering?",
        "When should localized name typography proof be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare target fonts and actual grapheme rendering",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare target fonts and actual grapheme rendering. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Character localization name map. Typography is an evaluation surface; do not detach it solely to add a page.",
        "deskReview": {
          "candidate": "localized-name-typography-proof",
          "parent": "character-localization-name-map",
          "action": "merge-proposed",
          "reason": "Typography is an evaluation surface; do not detach it solely to add a page.",
          "parentId": "nw-character-localization-name-map",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-localized-gender-assumption-audit",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Task A: Compare target fonts and actual grapheme rendering. Task B: Flag unintended target language signals for human review. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-acrostic-name-clue",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Compare target fonts and actual grapheme rendering. Task B: Reconcile translated names with an acrostic used in the plot. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-anagram-clue",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Compare target fonts and actual grapheme rendering. Task B: Rebuild a name puzzle with solvability evidence in each language. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare target fonts and actual grapheme rendering",
        "outline": [
          "Explain the specific decision: Compare target fonts and actual grapheme rendering",
          "Define the applicable contract and limits for Localized name typography proof",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare target fonts and actual grapheme rendering; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare target fonts and actual grapheme rendering",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Typography is an evaluation surface; do not detach it solely to add a page."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:322",
      "profileSource": "data/profiles.json#localization",
      "disposition": {
        "action": "merged",
        "parentId": "nw-character-localization-name-map",
        "reason": "Typography is an evaluation surface; do not detach it solely to add a page.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-localized-name-version-migration",
      "slug": "localized-name-version-migration",
      "name": "Localized name version migration",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-name-version-migration/",
        "ja": "/ja/tools/localized-name-version-migration/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Preserve old spellings in a controlled editorial ledger",
      "task": "Preserve old spellings in a controlled editorial ledger",
      "searchIntent": {
        "primary": "Complete the task: Preserve old spellings in a controlled editorial ledger",
        "queryHypothesis": "localized name version migration",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve old spellings in a controlled editorial ledger?",
        "When should localized name version migration be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve old spellings in a controlled editorial ledger",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve old spellings in a controlled editorial ledger. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Character localization name map. Versioned spelling migration is a maintenance capability of the identity mapping tool.",
        "deskReview": {
          "candidate": "localized-name-version-migration",
          "parent": "character-localization-name-map",
          "action": "merge-proposed",
          "reason": "Versioned spelling migration is a maintenance capability of the identity mapping tool.",
          "parentId": "nw-character-localization-name-map",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-invented-spelling-reform",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Preserve old spellings in a controlled editorial ledger. Task B: Map old and new spellings while retaining character identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-save-migration-renamed-npc",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Task A: Preserve old spellings in a controlled editorial ledger. Task B: Preserve old save IDs while changing approved display names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-serial-author-handle-migration",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": false,
          "difference": "Task A: Preserve old spellings in a controlled editorial ledger. Task B: Reconcile old community handles with a book byline. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve old spellings in a controlled editorial ledger",
        "outline": [
          "Explain the specific decision: Preserve old spellings in a controlled editorial ledger",
          "Define the applicable contract and limits for Localized name version migration",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve old spellings in a controlled editorial ledger; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve old spellings in a controlled editorial ledger",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review.",
        "merge-proposed: Versioned spelling migration is a maintenance capability of the identity mapping tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:336",
      "profileSource": "data/profiles.json#localization",
      "disposition": {
        "action": "merged",
        "parentId": "nw-character-localization-name-map",
        "reason": "Versioned spelling migration is a maintenance capability of the identity mapping tool.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-comic-mobile-name-legibility",
      "slug": "comic-mobile-name-legibility",
      "name": "Comic mobile name legibility",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-mobile-name-legibility/",
        "ja": "/ja/tools/comic-mobile-name-legibility/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Test supplied text at realistic narrow viewports",
      "task": "Test supplied text at realistic narrow viewports",
      "searchIntent": {
        "primary": "Complete the task: Test supplied text at realistic narrow viewports",
        "queryHypothesis": "comic mobile name legibility",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test supplied text at realistic narrow viewports?",
        "When should comic mobile name legibility be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test supplied text at realistic narrow viewports",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test supplied text at realistic narrow viewports. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Manga cast lettering proof. Mobile viewport is a proof parameter, not an independent naming task.",
        "deskReview": {
          "candidate": "comic-mobile-name-legibility",
          "parent": "manga-cast-lettering-proof",
          "action": "merge-proposed",
          "reason": "Mobile viewport is a proof parameter, not an independent naming task.",
          "parentId": "nw-manga-cast-lettering-proof",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-vertical-setting",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Test supplied text at realistic narrow viewports. Task B: Test name and reading in vertical text layouts. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-signature-legibility",
          "title": 0.2,
          "task": 0.125,
          "score": 0.15125,
          "sharedProfile": false,
          "difference": "Task A: Test supplied text at realistic narrow viewports. Task B: Compare supplied signatures at realistic display sizes. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-comic-name-reveal-splash",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Task A: Test supplied text at realistic narrow viewports. Task B: Compare reveal text hierarchy with prior identity clues. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test supplied text at realistic narrow viewports",
        "outline": [
          "Explain the specific decision: Test supplied text at realistic narrow viewports",
          "Define the applicable contract and limits for Comic mobile name legibility",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test supplied text at realistic narrow viewports; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test supplied text at realistic narrow viewports",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Mobile viewport is a proof parameter, not an independent naming task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:370",
      "profileSource": "data/profiles.json#manga-production",
      "disposition": {
        "action": "merged",
        "parentId": "nw-manga-cast-lettering-proof",
        "reason": "Mobile viewport is a proof parameter, not an independent naming task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-speech-balloon-name-wrapping",
      "slug": "speech-balloon-name-wrapping",
      "name": "Speech balloon name wrapping",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/speech-balloon-name-wrapping/",
        "ja": "/ja/tools/speech-balloon-name-wrapping/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Compare line breaks at supplied balloon dimensions",
      "task": "Compare line breaks at supplied balloon dimensions",
      "searchIntent": {
        "primary": "Complete the task: Compare line breaks at supplied balloon dimensions",
        "queryHypothesis": "speech balloon name wrapping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare line breaks at supplied balloon dimensions?",
        "When should speech balloon name wrapping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare line breaks at supplied balloon dimensions",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare line breaks at supplied balloon dimensions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Manga cast lettering proof. Balloon wrapping is a core proof operation and needs the same inputs and output context.",
        "deskReview": {
          "candidate": "speech-balloon-name-wrapping",
          "parent": "manga-cast-lettering-proof",
          "action": "merge-proposed",
          "reason": "Balloon wrapping is a core proof operation and needs the same inputs and output context.",
          "parentId": "nw-manga-cast-lettering-proof",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-name-dialogue-balloon",
          "title": 0.2,
          "task": 0.2222222222222222,
          "score": 0.21444444444444444,
          "sharedProfile": false,
          "difference": "Task A: Compare line breaks at supplied balloon dimensions. Task B: Preview line breaks and reading support in constrained balloons. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-name-hud-budget",
          "title": 0,
          "task": 0.14285714285714285,
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Task A: Compare line breaks at supplied balloon dimensions. Task B: Fit approved names to actual rendered HUD dimensions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-name-length-budget",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Compare line breaks at supplied balloon dimensions. Task B: Fit approved forms to actual UI or balloon constraints. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare line breaks at supplied balloon dimensions",
        "outline": [
          "Explain the specific decision: Compare line breaks at supplied balloon dimensions",
          "Define the applicable contract and limits for Speech balloon name wrapping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare line breaks at supplied balloon dimensions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare line breaks at supplied balloon dimensions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Balloon wrapping is a core proof operation and needs the same inputs and output context."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:346",
      "profileSource": "data/profiles.json#manga-production",
      "disposition": {
        "action": "merged",
        "parentId": "nw-manga-cast-lettering-proof",
        "reason": "Balloon wrapping is a core proof operation and needs the same inputs and output context.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-comic-printable-cast-reference",
      "slug": "comic-printable-cast-reference",
      "name": "Comic printable cast reference",
      "category": "manga-production",
      "urls": {
        "en": "/en/tools/comic-printable-cast-reference/",
        "ja": "/ja/tools/comic-printable-cast-reference/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "manga writers, artists and letterers",
      "scenario": "Export an editor usable reference with version identifiers",
      "task": "Export an editor usable reference with version identifiers",
      "searchIntent": {
        "primary": "Complete the task: Export an editor usable reference with version identifiers",
        "queryHypothesis": "comic printable cast reference",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export an editor usable reference with version identifiers?",
        "When should comic printable cast reference be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "page and panel references: locate identity appearance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "balloon or card dimensions: bound layout",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved script and readings: keep text consistent",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "measure rendered text using the selected font",
        "separate production labels from reader visible names"
      ],
      "requiredData": [
        {
          "description": "authored panel manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "approved cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "font and layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export an editor usable reference with version identifiers",
        "measure rendered text using the selected font",
        "separate production labels from reader visible names",
        "Proposed category workflow: cast bible → panel mapping → lettering proof → editorial signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "name layout proofs",
        "panel linked change list",
        "spoiler and continuity warnings"
      ],
      "capabilities": [
        "trace a rename into visible props as well as dialogue",
        "preview short name and reading layouts at mobile dimensions"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export an editor usable reference with version identifiers. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Manga character name card. Printability is an export surface, while a creator-facing cast card is the main artifact.",
        "deskReview": {
          "candidate": "comic-printable-cast-reference",
          "parent": "manga-character-name-card",
          "action": "merge-proposed",
          "reason": "Printability is an export surface, while a creator-facing cast card is the main artifact.",
          "parentId": "nw-manga-character-name-card",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-editor-handoff",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Export an editor usable reference with version identifiers. Task B: Export approved names and open questions for an editor. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-institution-fictional-name-charter",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Export an editor usable reference with version identifiers. Task B: Export membership, naming authority and exceptions as a usable guide. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-comic-letterer-handoff-names",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Task A: Export an editor usable reference with version identifiers. Task B: Export approved spellings, pronunciations and forbidden variants. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export an editor usable reference with version identifiers",
        "outline": [
          "Explain the specific decision: Export an editor usable reference with version identifiers",
          "Define the applicable contract and limits for Comic printable cast reference",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export an editor usable reference with version identifiers; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export an editor usable reference with version identifiers",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Printability is an export surface, while a creator-facing cast card is the main artifact."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:378",
      "profileSource": "data/profiles.json#manga-production",
      "disposition": {
        "action": "merged",
        "parentId": "nw-manga-character-name-card",
        "reason": "Printability is an export surface, while a creator-facing cast card is the main artifact.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-mora-timing",
      "slug": "japanese-name-mora-timing",
      "name": "Japanese name mora timing",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/japanese-name-mora-timing/",
        "ja": "/ja/tools/japanese-name-mora-timing/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Estimate timing from confirmed kana and label estimates honestly",
      "task": "Estimate timing from confirmed kana and label estimates honestly",
      "searchIntent": {
        "primary": "Complete the task: Estimate timing from confirmed kana and label estimates honestly",
        "queryHypothesis": "japanese name mora timing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to estimate timing from confirmed kana and label estimates honestly?",
        "When should japanese name mora timing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Estimate timing from confirmed kana and label estimates honestly",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Estimate timing from confirmed kana and label estimates honestly. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Motion comic spoken cast separation. Mora-based estimates are an explicitly limited timing method in the audio workflow, not a promised intelligibility measurement.",
        "deskReview": {
          "candidate": "japanese-name-mora-timing",
          "parent": "motion-comic-spoken-cast-separation",
          "action": "merge-proposed",
          "reason": "Mora-based estimates are an explicitly limited timing method in the audio workflow, not a promised intelligibility measurement.",
          "parentId": "nw-motion-comic-spoken-cast-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-japanese-full-name-rhythm",
          "title": 0.2,
          "task": 0.18181818181818182,
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Task A: Estimate timing from confirmed kana and label estimates honestly. Task B: Compare mora patterns using author confirmed kana. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-character-name-record",
          "title": 0.3333333333333333,
          "task": 0.1,
          "score": 0.18166666666666664,
          "sharedProfile": false,
          "difference": "Task A: Estimate timing from confirmed kana and label estimates honestly. Task B: Keep kanji, kana and approved pronunciation as separate fields. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "title": 0.2,
          "task": 0.09090909090909091,
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Task A: Estimate timing from confirmed kana and label estimates honestly. Task B: Store approved kana and romanized credits alongside the name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Estimate timing from confirmed kana and label estimates honestly",
        "outline": [
          "Explain the specific decision: Estimate timing from confirmed kana and label estimates honestly",
          "Define the applicable contract and limits for Japanese name mora timing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Estimate timing from confirmed kana and label estimates honestly; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Estimate timing from confirmed kana and label estimates honestly",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Mora-based estimates are an explicitly limited timing method in the audio workflow, not a promised intelligibility measurement."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:390",
      "profileSource": "data/profiles.json#audio-drama",
      "disposition": {
        "action": "merged",
        "parentId": "nw-motion-comic-spoken-cast-separation",
        "reason": "Mora-based estimates are an explicitly limited timing method in the audio workflow, not a promised intelligibility measurement.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-english-name-stress-brief",
      "slug": "english-name-stress-brief",
      "name": "English name stress brief",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/english-name-stress-brief/",
        "ja": "/ja/tools/english-name-stress-brief/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Record approved stress patterns and alternative interpretations",
      "task": "Record approved stress patterns and alternative interpretations",
      "searchIntent": {
        "primary": "Complete the task: Record approved stress patterns and alternative interpretations",
        "queryHypothesis": "english name stress brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record approved stress patterns and alternative interpretations?",
        "When should english name stress brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record approved stress patterns and alternative interpretations",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record approved stress patterns and alternative interpretations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Voice cast name pronunciation sheet. Approved stress is pronunciation metadata for the same performer handoff.",
        "deskReview": {
          "candidate": "english-name-stress-brief",
          "parent": "voice-cast-name-pronunciation-sheet",
          "action": "merge-proposed",
          "reason": "Approved stress is pronunciation metadata for the same performer handoff.",
          "parentId": "nw-voice-cast-name-pronunciation-sheet",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-character-naming-brief",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Record approved stress patterns and alternative interpretations. Task B: Convert a role, setting and narrative distance into a testable name brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-that-cannot-be-spoken",
          "title": 0,
          "task": 0.14285714285714285,
          "score": 0.09285714285714286,
          "sharedProfile": false,
          "difference": "Task A: Record approved stress patterns and alternative interpretations. Task B: Provide alternative references with explicit fictional consequences. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-name-pronunciation-brief",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Record approved stress patterns and alternative interpretations. Task B: Supply author approved pronunciations without invented etymology. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record approved stress patterns and alternative interpretations",
        "outline": [
          "Explain the specific decision: Record approved stress patterns and alternative interpretations",
          "Define the applicable contract and limits for English name stress brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record approved stress patterns and alternative interpretations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record approved stress patterns and alternative interpretations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Approved stress is pronunciation metadata for the same performer handoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:391",
      "profileSource": "data/profiles.json#audio-drama",
      "disposition": {
        "action": "merged",
        "parentId": "nw-voice-cast-name-pronunciation-sheet",
        "reason": "Approved stress is pronunciation metadata for the same performer handoff.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-whispered-name-scene",
      "slug": "whispered-name-scene",
      "name": "Whispered name scene",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/whispered-name-scene/",
        "ja": "/ja/tools/whispered-name-scene/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Compare intelligibility using actual recordings supplied for review",
      "task": "Compare intelligibility using actual recordings supplied for review",
      "searchIntent": {
        "primary": "Complete the task: Compare intelligibility using actual recordings supplied for review",
        "queryHypothesis": "whispered name scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare intelligibility using actual recordings supplied for review?",
        "When should whispered name scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare intelligibility using actual recordings supplied for review",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare intelligibility using actual recordings supplied for review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Motion comic spoken cast separation. Whisper delivery is a rehearsal condition, not a distinct name generation task.",
        "deskReview": {
          "candidate": "whispered-name-scene",
          "parent": "motion-comic-spoken-cast-separation",
          "action": "merge-proposed",
          "reason": "Whisper delivery is a rehearsal condition, not a distinct name generation task.",
          "parentId": "nw-motion-comic-spoken-cast-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-in-confession-scene",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Compare intelligibility using actual recordings supplied for review. Task B: Control who is identified by an emotionally loaded address. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-scene-laboratory",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Compare intelligibility using actual recordings supplied for review. Task B: Compare one scene written with three explicitly different naming decisions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-unspoken-name-scene",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Compare intelligibility using actual recordings supplied for review. Task B: Keep a name off the page while preserving referential clarity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare intelligibility using actual recordings supplied for review",
        "outline": [
          "Explain the specific decision: Compare intelligibility using actual recordings supplied for review",
          "Define the applicable contract and limits for Whispered name scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare intelligibility using actual recordings supplied for review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare intelligibility using actual recordings supplied for review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Whisper delivery is a rehearsal condition, not a distinct name generation task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:397",
      "profileSource": "data/profiles.json#audio-drama",
      "disposition": {
        "action": "merged",
        "parentId": "nw-motion-comic-spoken-cast-separation",
        "reason": "Whisper delivery is a rehearsal condition, not a distinct name generation task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-shouted-name-action-scene",
      "slug": "shouted-name-action-scene",
      "name": "Shouted name action scene",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/shouted-name-action-scene/",
        "ja": "/ja/tools/shouted-name-action-scene/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Test author recorded alternatives against scene pacing",
      "task": "Test author recorded alternatives against scene pacing",
      "searchIntent": {
        "primary": "Complete the task: Test author recorded alternatives against scene pacing",
        "queryHypothesis": "shouted name action scene",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test author recorded alternatives against scene pacing?",
        "When should shouted name action scene be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test author recorded alternatives against scene pacing",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test author recorded alternatives against scene pacing. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Motion comic spoken cast separation. Shouted delivery is another measured rehearsal condition under the same audio decision.",
        "deskReview": {
          "candidate": "shouted-name-action-scene",
          "parent": "motion-comic-spoken-cast-separation",
          "action": "merge-proposed",
          "reason": "Shouted delivery is another measured rehearsal condition under the same audio decision.",
          "parentId": "nw-motion-comic-spoken-cast-separation",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-crowd-shouted-name-clarity",
          "title": 0.2,
          "task": 0.3333333333333333,
          "score": 0.2866666666666667,
          "sharedProfile": false,
          "difference": "Task A: Test author recorded alternatives against scene pacing. Task B: Test distinguishability against other names in the scene. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-dialogue-vocative-pacing",
          "title": 0,
          "task": 0.2727272727272727,
          "score": 0.17727272727272728,
          "sharedProfile": true,
          "difference": "Task A: Test author recorded alternatives against scene pacing. Task B: Measure recorded name duration against a scene timing budget. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-scene-laboratory",
          "title": 0.25,
          "task": 0.07692307692307693,
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Task A: Test author recorded alternatives against scene pacing. Task B: Compare one scene written with three explicitly different naming decisions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test author recorded alternatives against scene pacing",
        "outline": [
          "Explain the specific decision: Test author recorded alternatives against scene pacing",
          "Define the applicable contract and limits for Shouted name action scene",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test author recorded alternatives against scene pacing; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test author recorded alternatives against scene pacing",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Shouted delivery is another measured rehearsal condition under the same audio decision."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:398",
      "profileSource": "data/profiles.json#audio-drama",
      "disposition": {
        "action": "merged",
        "parentId": "nw-motion-comic-spoken-cast-separation",
        "reason": "Shouted delivery is another measured rehearsal condition under the same audio decision.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-npc-name-seed-reproducibility",
      "slug": "npc-name-seed-reproducibility",
      "name": "NPC name seed reproducibility",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-name-seed-reproducibility/",
        "ja": "/ja/tools/npc-name-seed-reproducibility/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Produce the same approved identity from saved generation state",
      "task": "Produce the same approved identity from saved generation state",
      "searchIntent": {
        "primary": "Complete the task: Produce the same approved identity from saved generation state",
        "queryHypothesis": "npc name seed reproducibility",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to produce the same approved identity from saved generation state?",
        "When should npc name seed reproducibility be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Produce the same approved identity from saved generation state",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Produce the same approved identity from saved generation state. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Procedural NPC naming. Reproducibility is a required engine capability and cannot be removed into a different page.",
        "deskReview": {
          "candidate": "npc-name-seed-reproducibility",
          "parent": "procedural-npc-naming",
          "action": "merge-proposed",
          "reason": "Reproducibility is a required engine capability and cannot be removed into a different page.",
          "parentId": "nw-procedural-npc-naming",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-character-ending-signature",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Produce the same approved identity from saved generation state. Task B: Compare the final signature with the opening identity state. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-game-npc-name-registry",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Task A: Produce the same approved identity from saved generation state. Task B: Assign stable identity keys and separate display names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-occupation-name-separation",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Task A: Produce the same approved identity from saved generation state. Task B: Keep role titles from replacing individual identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Produce the same approved identity from saved generation state",
        "outline": [
          "Explain the specific decision: Produce the same approved identity from saved generation state",
          "Define the applicable contract and limits for NPC name seed reproducibility",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Produce the same approved identity from saved generation state; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Produce the same approved identity from saved generation state",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Reproducibility is a required engine capability and cannot be removed into a different page."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:439",
      "profileSource": "data/profiles.json#game-characters",
      "disposition": {
        "action": "merged",
        "parentId": "nw-procedural-npc-naming",
        "reason": "Reproducibility is a required engine capability and cannot be removed into a different page.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-npc-unique-name-exhaustion",
      "slug": "npc-unique-name-exhaustion",
      "name": "NPC unique name exhaustion",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-unique-name-exhaustion/",
        "ja": "/ja/tools/npc-unique-name-exhaustion/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Explain exhausted pools rather than silently duplicate names",
      "task": "Explain exhausted pools rather than silently duplicate names",
      "searchIntent": {
        "primary": "Complete the task: Explain exhausted pools rather than silently duplicate names",
        "queryHypothesis": "npc unique name exhaustion",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to explain exhausted pools rather than silently duplicate names?",
        "When should npc unique name exhaustion be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Explain exhausted pools rather than silently duplicate names",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Explain exhausted pools rather than silently duplicate names. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Procedural NPC naming. Pool exhaustion is required failure handling in the same generation task.",
        "deskReview": {
          "candidate": "npc-unique-name-exhaustion",
          "parent": "procedural-npc-naming",
          "action": "merge-proposed",
          "reason": "Pool exhaustion is required failure handling in the same generation task.",
          "parentId": "nw-procedural-npc-naming",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-family-records-mismatch",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Explain exhausted pools rather than silently duplicate names. Task B: Explain alternate spellings without silently merging characters. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-game-name-generation-error-ui",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Explain exhausted pools rather than silently duplicate names. Task B: Explain exhausted constraints and offer targeted relaxations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-alternate-history-name-divergence",
          "title": 0,
          "task": 0.16666666666666666,
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Task A: Explain exhausted pools rather than silently duplicate names. Task B: Trace the authored divergence rather than invent historical certainty. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Explain exhausted pools rather than silently duplicate names",
        "outline": [
          "Explain the specific decision: Explain exhausted pools rather than silently duplicate names",
          "Define the applicable contract and limits for NPC unique name exhaustion",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Explain exhausted pools rather than silently duplicate names; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Explain exhausted pools rather than silently duplicate names",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Pool exhaustion is required failure handling in the same generation task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:441",
      "profileSource": "data/profiles.json#game-characters",
      "disposition": {
        "action": "merged",
        "parentId": "nw-procedural-npc-naming",
        "reason": "Pool exhaustion is required failure handling in the same generation task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-npc-name-generation-coverage",
      "slug": "npc-name-generation-coverage",
      "name": "NPC name generation coverage",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-name-generation-coverage/",
        "ja": "/ja/tools/npc-name-generation-coverage/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Audit which declared cultures and households lack data",
      "task": "Audit which declared cultures and households lack data",
      "searchIntent": {
        "primary": "Complete the task: Audit which declared cultures and households lack data",
        "queryHypothesis": "npc name generation coverage",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to audit which declared cultures and households lack data?",
        "When should npc name generation coverage be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Audit which declared cultures and households lack data",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Audit which declared cultures and households lack data. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Procedural NPC naming. Coverage reporting belongs to corpus readiness and cannot count as a generated naming task.",
        "deskReview": {
          "candidate": "npc-name-generation-coverage",
          "parent": "procedural-npc-naming",
          "action": "merge-proposed",
          "reason": "Coverage reporting belongs to corpus readiness and cannot count as a generated naming task.",
          "parentId": "nw-procedural-npc-naming",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-npc-family-generation",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Audit which declared cultures and households lack data. Task B: Propagate household rules through a generated settlement graph. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-social-memory-names",
          "title": 0.2,
          "task": 0.07142857142857142,
          "score": 0.11642857142857142,
          "sharedProfile": true,
          "difference": "Task A: Audit which declared cultures and households lack data. Task B: Decide which observers remember an earlier identity after a quest. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-data-generation-audit-trail",
          "title": 0.16666666666666666,
          "task": 0.08333333333333333,
          "score": 0.11249999999999999,
          "sharedProfile": false,
          "difference": "Task A: Audit which declared cultures and households lack data. Task B: Export which entries and rules produced a candidate. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Audit which declared cultures and households lack data",
        "outline": [
          "Explain the specific decision: Audit which declared cultures and households lack data",
          "Define the applicable contract and limits for NPC name generation coverage",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Audit which declared cultures and households lack data; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Audit which declared cultures and households lack data",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Coverage reporting belongs to corpus readiness and cannot count as a generated naming task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:452",
      "profileSource": "data/profiles.json#game-characters",
      "disposition": {
        "action": "merged",
        "parentId": "nw-procedural-npc-naming",
        "reason": "Coverage reporting belongs to corpus readiness and cannot count as a generated naming task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-npc-forbidden-token-rules",
      "slug": "npc-forbidden-token-rules",
      "name": "NPC forbidden token rules",
      "category": "game-characters",
      "urls": {
        "en": "/en/tools/npc-forbidden-token-rules/",
        "ja": "/ja/tools/npc-forbidden-token-rules/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "narrative designers and game writers",
      "scenario": "Apply project supplied exclusion data and report empty pools",
      "task": "Apply project supplied exclusion data and report empty pools",
      "searchIntent": {
        "primary": "Complete the task: Apply project supplied exclusion data and report empty pools",
        "queryHypothesis": "npc forbidden token rules",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to apply project supplied exclusion data and report empty pools?",
        "When should npc forbidden token rules be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "persistent character IDs: preserve saves",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "world state: resolve current identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "generation seed and corpus version: reproduce output",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates"
      ],
      "requiredData": [
        {
          "description": "versioned fictional corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "quest flags and relationship graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "save migration fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Apply project supplied exclusion data and report empty pools",
        "display name changes must not change save identity",
        "satisfy hard constraints before ranking candidates",
        "Proposed category workflow: state contract → deterministic generation → event simulation → save regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "identity keyed candidates",
        "state dependent display forms",
        "generation provenance and failure reasons"
      ],
      "capabilities": [
        "replay name output from a pinned state",
        "test an identity before and after a quest event"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Apply project supplied exclusion data and report empty pools. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: Procedural NPC naming. Exclusion rules are shared controls with explicit matching semantics.",
        "deskReview": {
          "candidate": "npc-forbidden-token-rules",
          "parent": "procedural-npc-naming",
          "action": "merge-proposed",
          "reason": "Exclusion rules are shared controls with explicit matching semantics.",
          "parentId": "nw-procedural-npc-naming",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-npc-adoption-event-names",
          "title": 0.16666666666666666,
          "task": 0.08333333333333333,
          "score": 0.11249999999999999,
          "sharedProfile": true,
          "difference": "Task A: Apply project supplied exclusion data and report empty pools. Task B: Apply household rules with author approved identity retention. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-inheritance-event-names",
          "title": 0.16666666666666666,
          "task": 0.07692307692307693,
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Task A: Apply project supplied exclusion data and report empty pools. Task B: Apply surname and title rules after a succession event. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-name-generation-coverage",
          "title": 0.16666666666666666,
          "task": 0.07692307692307693,
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Task A: Apply project supplied exclusion data and report empty pools. Task B: Audit which declared cultures and households lack data. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Apply project supplied exclusion data and report empty pools",
        "outline": [
          "Explain the specific decision: Apply project supplied exclusion data and report empty pools",
          "Define the applicable contract and limits for NPC forbidden token rules",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Apply project supplied exclusion data and report empty pools; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Apply project supplied exclusion data and report empty pools",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Exclusion rules are shared controls with explicit matching semantics."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:440",
      "profileSource": "data/profiles.json#game-characters",
      "disposition": {
        "action": "merged",
        "parentId": "nw-procedural-npc-naming",
        "reason": "Exclusion rules are shared controls with explicit matching semantics.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-game-name-randomizer-lock",
      "slug": "game-name-randomizer-lock",
      "name": "Game name randomizer lock",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-randomizer-lock/",
        "ja": "/ja/tools/game-name-randomizer-lock/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Preserve locked components during character creation rerolls",
      "task": "Preserve locked components during character creation rerolls",
      "searchIntent": {
        "primary": "Complete the task: Preserve locked components during character creation rerolls",
        "queryHypothesis": "game name randomizer lock",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve locked components during character creation rerolls?",
        "When should game name randomizer lock be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve locked components during character creation rerolls",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve locked components during character creation rerolls. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Procedural NPC naming. Component locks are a shared interaction rather than an independent page.",
        "deskReview": {
          "candidate": "game-name-randomizer-lock",
          "parent": "procedural-npc-naming",
          "action": "merge-proposed",
          "reason": "Component locks are a shared interaction rather than an independent page.",
          "parentId": "nw-procedural-npc-naming",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-game-name-maximum-expansion",
          "title": 0.2,
          "task": 0.08333333333333333,
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Task A: Preserve locked components during character creation rerolls. Task B: Test worst case localized names across declared UI components. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-game-engine-name-key-migration",
          "title": 0.16666666666666666,
          "task": 0.1,
          "score": 0.12333333333333332,
          "sharedProfile": true,
          "difference": "Task A: Preserve locked components during character creation rerolls. Task B: Keep resource keys stable during display name revisions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-legal-name-layers",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Preserve locked components during character creation rerolls. Task B: Separate citizenship, household and personal chosen components. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve locked components during character creation rerolls",
        "outline": [
          "Explain the specific decision: Preserve locked components during character creation rerolls",
          "Define the applicable contract and limits for Game name randomizer lock",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve locked components during character creation rerolls; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve locked components during character creation rerolls",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Component locks are a shared interaction rather than an independent page."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:487",
      "profileSource": "data/profiles.json#game-ui",
      "disposition": {
        "action": "merged",
        "parentId": "nw-procedural-npc-naming",
        "reason": "Component locks are a shared interaction rather than an independent page.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-game-name-markup-escaping",
      "slug": "game-name-markup-escaping",
      "name": "Game name markup escaping",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-markup-escaping/",
        "ja": "/ja/tools/game-name-markup-escaping/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Validate safe insertion into a selected rich text format",
      "task": "Validate safe insertion into a selected rich text format",
      "searchIntent": {
        "primary": "Complete the task: Validate safe insertion into a selected rich text format",
        "queryHypothesis": "game name markup escaping",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to validate safe insertion into a selected rich text format?",
        "When should game name markup escaping be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Validate safe insertion into a selected rich text format",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Validate safe insertion into a selected rich text format. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Game NPC name registry. Escaping is mandatory engineering hygiene; it is not public creator-facing naming value.",
        "deskReview": {
          "candidate": "game-name-markup-escaping",
          "parent": "game-npc-name-registry",
          "action": "merge-proposed",
          "reason": "Escaping is mandatory engineering hygiene; it is not public creator-facing naming value.",
          "parentId": "nw-game-npc-name-registry",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-game-text-width-name-audit",
          "title": 0.16666666666666666,
          "task": 0.07692307692307693,
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Task A: Validate safe insertion into a selected rich text format. Task B: Measure actual text instead of using character count as width. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-convention-game-pregenerated-names",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Task A: Validate safe insertion into a selected rich text format. Task B: Design pronounceable player selectable characters with neutral role cues. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-game-codex-spoiler-names",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": false,
          "difference": "Task A: Validate safe insertion into a selected rich text format. Task B: Gate names by discovery flags with explicit fallback labels. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Validate safe insertion into a selected rich text format",
        "outline": [
          "Explain the specific decision: Validate safe insertion into a selected rich text format",
          "Define the applicable contract and limits for Game name markup escaping",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Validate safe insertion into a selected rich text format; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Validate safe insertion into a selected rich text format",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Escaping is mandatory engineering hygiene; it is not public creator-facing naming value."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:474",
      "profileSource": "data/profiles.json#game-ui",
      "disposition": {
        "action": "merged",
        "parentId": "nw-game-npc-name-registry",
        "reason": "Escaping is mandatory engineering hygiene; it is not public creator-facing naming value.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-game-name-multiline-ordering",
      "slug": "game-name-multiline-ordering",
      "name": "Game name multiline ordering",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-multiline-ordering/",
        "ja": "/ja/tools/game-name-multiline-ordering/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Preserve logical reading order in stacked nameplates",
      "task": "Preserve logical reading order in stacked nameplates",
      "searchIntent": {
        "primary": "Complete the task: Preserve logical reading order in stacked nameplates",
        "queryHypothesis": "game name multiline ordering",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve logical reading order in stacked nameplates?",
        "When should game name multiline ordering be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve logical reading order in stacked nameplates",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve logical reading order in stacked nameplates. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Dialogue nameplate overflow. Logical line ordering belongs in one nameplate layout proof rather than a separate tiny validator.",
        "deskReview": {
          "candidate": "game-name-multiline-ordering",
          "parent": "dialogue-nameplate-overflow",
          "action": "merge-proposed",
          "reason": "Logical line ordering belongs in one nameplate layout proof rather than a separate tiny validator.",
          "parentId": "nw-dialogue-nameplate-overflow",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-comic-name-gloss-placement",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Preserve logical reading order in stacked nameplates. Task B: Choose reading notes that preserve panel reading order. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-invented-reading-disclosure",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Preserve logical reading order in stacked nameplates. Task B: Label an author invented reading as fictional. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-small-kana-audit",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Preserve logical reading order in stacked nameplates. Task B: Preserve contracted sounds in approved reading data. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve logical reading order in stacked nameplates",
        "outline": [
          "Explain the specific decision: Preserve logical reading order in stacked nameplates",
          "Define the applicable contract and limits for Game name multiline ordering",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve logical reading order in stacked nameplates; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve logical reading order in stacked nameplates",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Logical line ordering belongs in one nameplate layout proof rather than a separate tiny validator."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:492",
      "profileSource": "data/profiles.json#game-ui",
      "disposition": {
        "action": "merged",
        "parentId": "nw-dialogue-nameplate-overflow",
        "reason": "Logical line ordering belongs in one nameplate layout proof rather than a separate tiny validator.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-invented-matronymic-grammar",
      "slug": "invented-matronymic-grammar",
      "name": "Invented matronymic grammar",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-matronymic-grammar/",
        "ja": "/ja/tools/invented-matronymic-grammar/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Derive names from maternal records with declared exceptions",
      "task": "Derive names from maternal records with declared exceptions",
      "searchIntent": {
        "primary": "Complete the task: Derive names from maternal records with declared exceptions",
        "queryHypothesis": "invented matronymic grammar",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive names from maternal records with declared exceptions?",
        "When should invented matronymic grammar be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive names from maternal records with declared exceptions",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive names from maternal records with declared exceptions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: World naming grammar builder. Maternal derivation is a grammar operation. A different inheritance branch alone is an option.",
        "deskReview": {
          "candidate": "invented-matronymic-grammar",
          "parent": "world-naming-grammar-builder",
          "action": "merge-proposed",
          "reason": "Maternal derivation is a grammar operation. A different inheritance branch alone is an option.",
          "parentId": "nw-world-naming-grammar-builder",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-invented-patronymic-grammar",
          "title": 0.5,
          "task": 0.42857142857142855,
          "score": 0.45357142857142857,
          "sharedProfile": true,
          "difference": "Task A: Derive names from maternal records with declared exceptions. Task B: Derive names from parent records with declared transformations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-matrilineal-fictional-inheritance",
          "title": 0,
          "task": 0.375,
          "score": 0.24375000000000002,
          "sharedProfile": false,
          "difference": "Task A: Derive names from maternal records with declared exceptions. Task B: Derive surnames through a declared maternal rule. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-name-grammar-exception",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Derive names from maternal records with declared exceptions. Task B: Record exceptional forms and their story justification. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive names from maternal records with declared exceptions",
        "outline": [
          "Explain the specific decision: Derive names from maternal records with declared exceptions",
          "Define the applicable contract and limits for Invented matronymic grammar",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive names from maternal records with declared exceptions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive names from maternal records with declared exceptions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Maternal derivation is a grammar operation. A different inheritance branch alone is an option."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:531",
      "profileSource": "data/profiles.json#world-grammar",
      "disposition": {
        "action": "merged",
        "parentId": "nw-world-naming-grammar-builder",
        "reason": "Maternal derivation is a grammar operation. A different inheritance branch alone is an option.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-invented-patronymic-grammar",
      "slug": "invented-patronymic-grammar",
      "name": "Invented patronymic grammar",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-patronymic-grammar/",
        "ja": "/ja/tools/invented-patronymic-grammar/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Derive names from parent records with declared transformations",
      "task": "Derive names from parent records with declared transformations",
      "searchIntent": {
        "primary": "Complete the task: Derive names from parent records with declared transformations",
        "queryHypothesis": "invented patronymic grammar",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to derive names from parent records with declared transformations?",
        "When should invented patronymic grammar be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Derive names from parent records with declared transformations",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Derive names from parent records with declared transformations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: World naming grammar builder. Paternal derivation is another grammar operation in the same rule authoring workflow.",
        "deskReview": {
          "candidate": "invented-patronymic-grammar",
          "parent": "world-naming-grammar-builder",
          "action": "merge-proposed",
          "reason": "Paternal derivation is another grammar operation in the same rule authoring workflow.",
          "parentId": "nw-world-naming-grammar-builder",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-invented-matronymic-grammar",
          "title": 0.5,
          "task": 0.42857142857142855,
          "score": 0.45357142857142857,
          "sharedProfile": true,
          "difference": "Task A: Derive names from parent records with declared transformations. Task B: Derive names from maternal records with declared exceptions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-name-grammar-exception",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Derive names from parent records with declared transformations. Task B: Record exceptional forms and their story justification. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-numerical-name-grammar",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Derive names from parent records with declared transformations. Task B: Explain how sequence and individuality coexist in names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Derive names from parent records with declared transformations",
        "outline": [
          "Explain the specific decision: Derive names from parent records with declared transformations",
          "Define the applicable contract and limits for Invented patronymic grammar",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Derive names from parent records with declared transformations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Derive names from parent records with declared transformations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Paternal derivation is another grammar operation in the same rule authoring workflow."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:530",
      "profileSource": "data/profiles.json#world-grammar",
      "disposition": {
        "action": "merged",
        "parentId": "nw-world-naming-grammar-builder",
        "reason": "Paternal derivation is another grammar operation in the same rule authoring workflow.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-invented-name-grammar-exception",
      "slug": "invented-name-grammar-exception",
      "name": "Invented name grammar exception",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-name-grammar-exception/",
        "ja": "/ja/tools/invented-name-grammar-exception/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Record exceptional forms and their story justification",
      "task": "Record exceptional forms and their story justification",
      "searchIntent": {
        "primary": "Complete the task: Record exceptional forms and their story justification",
        "queryHypothesis": "invented name grammar exception",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to record exceptional forms and their story justification?",
        "When should invented name grammar exception be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Record exceptional forms and their story justification",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Record exceptional forms and their story justification. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: World naming grammar builder. Exception management is a required part of grammar design.",
        "deskReview": {
          "candidate": "invented-name-grammar-exception",
          "parent": "world-naming-grammar-builder",
          "action": "merge-proposed",
          "reason": "Exception management is a required part of grammar design.",
          "parentId": "nw-world-naming-grammar-builder",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-invented-matronymic-grammar",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Record exceptional forms and their story justification. Task B: Derive names from maternal records with declared exceptions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-numerical-name-grammar",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Record exceptional forms and their story justification. Task B: Explain how sequence and individuality coexist in names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-patronymic-grammar",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Record exceptional forms and their story justification. Task B: Derive names from parent records with declared transformations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Record exceptional forms and their story justification",
        "outline": [
          "Explain the specific decision: Record exceptional forms and their story justification",
          "Define the applicable contract and limits for Invented name grammar exception",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Record exceptional forms and their story justification; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Record exceptional forms and their story justification",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: Exception management is a required part of grammar design."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:569",
      "profileSource": "data/profiles.json#world-grammar",
      "disposition": {
        "action": "merged",
        "parentId": "nw-world-naming-grammar-builder",
        "reason": "Exception management is a required part of grammar design.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-invented-culture-name-style-guide",
      "slug": "invented-culture-name-style-guide",
      "name": "Invented culture name style guide",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-culture-name-style-guide/",
        "ja": "/ja/tools/invented-culture-name-style-guide/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Export rules, examples and unresolved decisions for collaborators",
      "task": "Export rules, examples and unresolved decisions for collaborators",
      "searchIntent": {
        "primary": "Complete the task: Export rules, examples and unresolved decisions for collaborators",
        "queryHypothesis": "invented culture name style guide",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to export rules, examples and unresolved decisions for collaborators?",
        "When should invented culture name style guide be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Export rules, examples and unresolved decisions for collaborators",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Export rules, examples and unresolved decisions for collaborators. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "merge-proposed: World naming grammar builder. A portable style guide is an output from the grammar work, not another independent tool.",
        "deskReview": {
          "candidate": "invented-culture-name-style-guide",
          "parent": "world-naming-grammar-builder",
          "action": "merge-proposed",
          "reason": "A portable style guide is an output from the grammar work, not another independent tool.",
          "parentId": "nw-world-naming-grammar-builder",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-family-naming-bible",
          "title": 0,
          "task": 0.3,
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Task A: Export rules, examples and unresolved decisions for collaborators. Task B: Export people, naming rules and exception decisions as one reference. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-translator-handoff",
          "title": 0,
          "task": 0.3,
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Task A: Export rules, examples and unresolved decisions for collaborators. Task B: Export stable IDs, evidence and unresolved localization decisions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-invented-border-culture-names",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Export rules, examples and unresolved decisions for collaborators. Task B: Model mixed conventions without treating them as random blends. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Export rules, examples and unresolved decisions for collaborators",
        "outline": [
          "Explain the specific decision: Export rules, examples and unresolved decisions for collaborators",
          "Define the applicable contract and limits for Invented culture name style guide",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Export rules, examples and unresolved decisions for collaborators; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Export rules, examples and unresolved decisions for collaborators",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "merge-proposed: A portable style guide is an output from the grammar work, not another independent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:570",
      "profileSource": "data/profiles.json#world-grammar",
      "disposition": {
        "action": "merged",
        "parentId": "nw-world-naming-grammar-builder",
        "reason": "A portable style guide is an output from the grammar work, not another independent tool.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-epithet-spoiler-audit",
      "slug": "epithet-spoiler-audit",
      "name": "Epithet spoiler audit",
      "category": "titles",
      "urls": {
        "en": "/en/tools/epithet-spoiler-audit/",
        "ja": "/ja/tools/epithet-spoiler-audit/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Prevent a title from revealing a future deed too early",
      "task": "Prevent a title from revealing a future deed too early",
      "searchIntent": {
        "primary": "Complete the task: Prevent a title from revealing a future deed too early",
        "queryHypothesis": "epithet spoiler audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to prevent a title from revealing a future deed too early?",
        "When should epithet spoiler audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Prevent a title from revealing a future deed too early",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Prevent a title from revealing a future deed too early. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "merge-proposed: Character epithet builder. Spoiler exposure is a required evaluation step for an earned epithet.",
        "deskReview": {
          "candidate": "epithet-spoiler-audit",
          "parent": "character-epithet-builder",
          "action": "merge-proposed",
          "reason": "Spoiler exposure is a required evaluation step for an earned epithet.",
          "parentId": "nw-character-epithet-builder",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-prophecy-title-spoiler",
          "title": 0.2,
          "task": 0.18181818181818182,
          "score": 0.18818181818181817,
          "sharedProfile": false,
          "difference": "Task A: Prevent a title from revealing a future deed too early. Task B: Avoid exposing the future role in early character labels. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-campaign-rumor-name-variants",
          "title": 0,
          "task": 0.23076923076923078,
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Task A: Prevent a title from revealing a future deed too early. Task B: Link inconsistent rumors without revealing the true person too early. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-epithet-builder",
          "title": 0.25,
          "task": 0.09090909090909091,
          "score": 0.1465909090909091,
          "sharedProfile": true,
          "difference": "Task A: Prevent a title from revealing a future deed too early. Task B: Connect an epithet to an authored deed and observer perspective. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Prevent a title from revealing a future deed too early",
        "outline": [
          "Explain the specific decision: Prevent a title from revealing a future deed too early",
          "Define the applicable contract and limits for Epithet spoiler audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Prevent a title from revealing a future deed too early; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Prevent a title from revealing a future deed too early",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "merge-proposed: Spoiler exposure is a required evaluation step for an earned epithet."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:608",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged",
        "parentId": "nw-character-epithet-builder",
        "reason": "Spoiler exposure is a required evaluation step for an earned epithet.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-title-overload-pruning",
      "slug": "title-overload-pruning",
      "name": "Title overload pruning",
      "category": "titles",
      "urls": {
        "en": "/en/tools/title-overload-pruning/",
        "ja": "/ja/tools/title-overload-pruning/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Reduce stacked titles while preserving scene relevant information",
      "task": "Reduce stacked titles while preserving scene relevant information",
      "searchIntent": {
        "primary": "Complete the task: Reduce stacked titles while preserving scene relevant information",
        "queryHypothesis": "title overload pruning",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reduce stacked titles while preserving scene relevant information?",
        "When should title overload pruning be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reduce stacked titles while preserving scene relevant information",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reduce stacked titles while preserving scene relevant information. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "redesign-proposed: Fictional ceremonial full style. Combine full-style construction and scene-appropriate shortening into one title resolution task with a timeline and speaker context.",
        "deskReview": {
          "candidate": "title-overload-pruning",
          "parent": "fictional-ceremonial-full-style",
          "action": "redesign-proposed",
          "reason": "Combine full-style construction and scene-appropriate shortening into one title resolution task with a timeline and speaker context.",
          "parentId": "nw-fictional-ceremonial-full-style",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-symbolism-restraint-exercise",
          "title": 0,
          "task": 0.23076923076923078,
          "score": 0.15000000000000002,
          "sharedProfile": false,
          "difference": "Task A: Reduce stacked titles while preserving scene relevant information. Task B: Remove overdetermined motifs while preserving relevant story function. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-earned-title-progression",
          "title": 0.2,
          "task": 0.08333333333333333,
          "score": 0.12416666666666666,
          "sharedProfile": true,
          "difference": "Task A: Reduce stacked titles while preserving scene relevant information. Task B: Sequence titles across actual narrative achievements. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-campaign-title-reward",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": false,
          "difference": "Task A: Reduce stacked titles while preserving scene relevant information. Task B: Create earned titles tied to actual in game actions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reduce stacked titles while preserving scene relevant information",
        "outline": [
          "Explain the specific decision: Reduce stacked titles while preserving scene relevant information",
          "Define the applicable contract and limits for Title overload pruning",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reduce stacked titles while preserving scene relevant information; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reduce stacked titles while preserving scene relevant information",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool.",
        "redesign-proposed: Combine full-style construction and scene-appropriate shortening into one title resolution task with a timeline and speaker context."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:609",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-into-redesigned-parent",
        "parentId": "nw-fictional-ceremonial-full-style",
        "reason": "Combine full-style construction and scene-appropriate shortening into one title resolution task with a timeline and speaker context.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-test-counterbalancing",
      "slug": "name-test-counterbalancing",
      "name": "Name test counterbalancing",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-counterbalancing/",
        "ja": "/ja/tools/name-test-counterbalancing/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Rotate candidate order to reduce a simple ordering bias",
      "task": "Rotate candidate order to reduce a simple ordering bias",
      "searchIntent": {
        "primary": "Complete the task: Rotate candidate order to reduce a simple ordering bias",
        "queryHypothesis": "name test counterbalancing",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to rotate candidate order to reduce a simple ordering bias?",
        "When should name test counterbalancing be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Rotate candidate order to reduce a simple ordering bias",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Rotate candidate order to reduce a simple ordering bias. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Name shortlist blind test. Order rotation is study methodology within the reader test, not a distinct creative naming outcome.",
        "deskReview": {
          "candidate": "name-test-counterbalancing",
          "parent": "name-shortlist-blind-test",
          "action": "merge-proposed",
          "reason": "Order rotation is study methodology within the reader test, not a distinct creative naming outcome.",
          "parentId": "nw-name-shortlist-blind-test",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-character-name-memorability-test",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Rotate candidate order to reduce a simple ordering bias. Task B: Build a recall exercise against a supplied cast. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-possession-naming-test",
          "title": 0.3333333333333333,
          "task": 0,
          "score": 0.11666666666666665,
          "sharedProfile": false,
          "difference": "Task A: Rotate candidate order to reduce a simple ordering bias. Task B: State what a name test can and cannot establish in the fictional rules. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-list-spoiler-test",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Rotate candidate order to reduce a simple ordering bias. Task B: Compare cast list entries against mystery disclosure timing. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Rotate candidate order to reduce a simple ordering bias",
        "outline": [
          "Explain the specific decision: Rotate candidate order to reduce a simple ordering bias",
          "Define the applicable contract and limits for Name test counterbalancing",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Rotate candidate order to reduce a simple ordering bias; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Rotate candidate order to reduce a simple ordering bias",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Order rotation is study methodology within the reader test, not a distinct creative naming outcome."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:930",
      "profileSource": "data/profiles.json#reader-tests",
      "disposition": {
        "action": "merged",
        "parentId": "nw-name-shortlist-blind-test",
        "reason": "Order rotation is study methodology within the reader test, not a distinct creative naming outcome.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-test-respondent-privacy",
      "slug": "name-test-respondent-privacy",
      "name": "Name test respondent privacy",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-test-respondent-privacy/",
        "ja": "/ja/tools/name-test-respondent-privacy/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Minimize collected identifiers in an author run local study",
      "task": "Minimize collected identifiers in an author run local study",
      "searchIntent": {
        "primary": "Complete the task: Minimize collected identifiers in an author run local study",
        "queryHypothesis": "name test respondent privacy",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to minimize collected identifiers in an author run local study?",
        "When should name test respondent privacy be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Minimize collected identifiers in an author run local study",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Minimize collected identifiers in an author run local study. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Name shortlist blind test. Privacy must be built into response collection rather than offered as a separate optional tool.",
        "deskReview": {
          "candidate": "name-test-respondent-privacy",
          "parent": "name-shortlist-blind-test",
          "action": "merge-proposed",
          "reason": "Privacy must be built into response collection rather than offered as a separate optional tool.",
          "parentId": "nw-name-shortlist-blind-test",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-shortlist-blind-test",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Task A: Minimize collected identifiers in an author run local study. Task B: Collect unaided impressions without showing author explanations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-byline-recall-test",
          "title": 0.16666666666666666,
          "task": 0.07692307692307693,
          "score": 0.10833333333333334,
          "sharedProfile": true,
          "difference": "Task A: Minimize collected identifiers in an author run local study. Task B: Compare remembered author forms after a mock cover exposure. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-name-memorability-test",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Minimize collected identifiers in an author run local study. Task B: Build a recall exercise against a supplied cast. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Minimize collected identifiers in an author run local study",
        "outline": [
          "Explain the specific decision: Minimize collected identifiers in an author run local study",
          "Define the applicable contract and limits for Name test respondent privacy",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Minimize collected identifiers in an author run local study; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Minimize collected identifiers in an author run local study",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Privacy must be built into response collection rather than offered as a separate optional tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:931",
      "profileSource": "data/profiles.json#reader-tests",
      "disposition": {
        "action": "merged",
        "parentId": "nw-name-shortlist-blind-test",
        "reason": "Privacy must be built into response collection rather than offered as a separate optional tool.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-scoring-sensitivity",
      "slug": "name-scoring-sensitivity",
      "name": "Name scoring sensitivity",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/name-scoring-sensitivity/",
        "ja": "/ja/tools/name-scoring-sensitivity/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Show how ranking changes when heuristic weights change",
      "task": "Show how ranking changes when heuristic weights change",
      "searchIntent": {
        "primary": "Complete the task: Show how ranking changes when heuristic weights change",
        "queryHypothesis": "name scoring sensitivity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to show how ranking changes when heuristic weights change?",
        "When should name scoring sensitivity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Show how ranking changes when heuristic weights change",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Show how ranking changes when heuristic weights change. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Name heuristic score explainer. Changing weights and explaining score components are one interpretable evaluation flow.",
        "deskReview": {
          "candidate": "name-scoring-sensitivity",
          "parent": "name-heuristic-score-explainer",
          "action": "merge-proposed",
          "reason": "Changing weights and explaining score components are one interpretable evaluation flow.",
          "parentId": "nw-name-heuristic-score-explainer",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-swarm-character-continuity",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Show how ranking changes when heuristic weights change. Task B: Preserve identity when constituent members change. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-erasure-story-continuity",
          "title": 0,
          "task": 0.15384615384615385,
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Task A: Show how ranking changes when heuristic weights change. Task B: Define how records and memories change after erasure. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-memory-scene-exercise",
          "title": 0,
          "task": 0.15384615384615385,
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Task A: Show how ranking changes when heuristic weights change. Task B: Show how a remembered form reveals relationship history. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Show how ranking changes when heuristic weights change",
        "outline": [
          "Explain the specific decision: Show how ranking changes when heuristic weights change",
          "Define the applicable contract and limits for Name scoring sensitivity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Show how ranking changes when heuristic weights change; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Show how ranking changes when heuristic weights change",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Changing weights and explaining score components are one interpretable evaluation flow."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:937",
      "profileSource": "data/profiles.json#reader-tests",
      "disposition": {
        "action": "merged",
        "parentId": "nw-name-heuristic-score-explainer",
        "reason": "Changing weights and explaining score components are one interpretable evaluation flow.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-naming-project-exclusion-list",
      "slug": "naming-project-exclusion-list",
      "name": "Naming project exclusion list",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-exclusion-list/",
        "ja": "/ja/tools/naming-project-exclusion-list/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Separate whole name exclusions from token and substring exclusions",
      "task": "Separate whole name exclusions from token and substring exclusions",
      "searchIntent": {
        "primary": "Complete the task: Separate whole name exclusions from token and substring exclusions",
        "queryHypothesis": "naming project exclusion list",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate whole name exclusions from token and substring exclusions?",
        "When should naming project exclusion list be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate whole name exclusions from token and substring exclusions",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate whole name exclusions from token and substring exclusions. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Naming project brief. The exclusion list is project configuration and a reusable input component.",
        "deskReview": {
          "candidate": "naming-project-exclusion-list",
          "parent": "naming-project-brief",
          "action": "merge-proposed",
          "reason": "The exclusion list is project configuration and a reusable input component.",
          "parentId": "nw-naming-project-brief",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-data-exclusion-governance",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Task A: Separate whole name exclusions from token and substring exclusions. Task B: Record who excluded a token and why without universalizing taste. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-brief",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Separate whole name exclusions from token and substring exclusions. Task B: Capture cast, language, world and publishing constraints in one editable brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-decision-record",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Separate whole name exclusions from token and substring exclusions. Task B: Save chosen names with reasons and rejected alternatives. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate whole name exclusions from token and substring exclusions",
        "outline": [
          "Explain the specific decision: Separate whole name exclusions from token and substring exclusions",
          "Define the applicable contract and limits for Naming project exclusion list",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate whole name exclusions from token and substring exclusions; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate whole name exclusions from token and substring exclusions",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: The exclusion list is project configuration and a reusable input component."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1002",
      "profileSource": "data/profiles.json#project-workflows",
      "disposition": {
        "action": "merged",
        "parentId": "nw-naming-project-brief",
        "reason": "The exclusion list is project configuration and a reusable input component.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-naming-project-favorites-deduplication",
      "slug": "naming-project-favorites-deduplication",
      "name": "Naming project favorites deduplication",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-favorites-deduplication/",
        "ja": "/ja/tools/naming-project-favorites-deduplication/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Compare saved names using declared normalization scopes",
      "task": "Compare saved names using declared normalization scopes",
      "searchIntent": {
        "primary": "Complete the task: Compare saved names using declared normalization scopes",
        "queryHypothesis": "naming project favorites deduplication",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare saved names using declared normalization scopes?",
        "When should naming project favorites deduplication be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare saved names using declared normalization scopes",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare saved names using declared normalization scopes. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Naming project candidate comparison. Favorite-scope deduplication is a shared library operation, not a new naming task.",
        "deskReview": {
          "candidate": "naming-project-favorites-deduplication",
          "parent": "naming-project-candidate-comparison",
          "action": "merge-proposed",
          "reason": "Favorite-scope deduplication is a shared library operation, not a new naming task.",
          "parentId": "nw-naming-project-candidate-comparison",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-positioning-exercise",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Compare saved names using declared normalization scopes. Task B: Compare byline presentations using a declared audience brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-brief",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Compare saved names using declared normalization scopes. Task B: Capture cast, language, world and publishing constraints in one editable brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-decision-record",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Compare saved names using declared normalization scopes. Task B: Save chosen names with reasons and rejected alternatives. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare saved names using declared normalization scopes",
        "outline": [
          "Explain the specific decision: Compare saved names using declared normalization scopes",
          "Define the applicable contract and limits for Naming project favorites deduplication",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare saved names using declared normalization scopes; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare saved names using declared normalization scopes",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Favorite-scope deduplication is a shared library operation, not a new naming task."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1003",
      "profileSource": "data/profiles.json#project-workflows",
      "disposition": {
        "action": "merged",
        "parentId": "nw-naming-project-candidate-comparison",
        "reason": "Favorite-scope deduplication is a shared library operation, not a new naming task.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-data-attestation-levels",
      "slug": "name-data-attestation-levels",
      "name": "Name data attestation levels",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-attestation-levels/",
        "ja": "/ja/tools/name-data-attestation-levels/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Distinguish attested form, inferred combination and invented form",
      "task": "Distinguish attested form, inferred combination and invented form",
      "searchIntent": {
        "primary": "Complete the task: Distinguish attested form, inferred combination and invented form",
        "queryHypothesis": "name data attestation levels",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to distinguish attested form, inferred combination and invented form?",
        "When should name data attestation levels be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Distinguish attested form, inferred combination and invented form",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Distinguish attested form, inferred combination and invented form. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Name claim evidence mapping. Attestation categories are a required part of evidence mapping.",
        "deskReview": {
          "candidate": "name-data-attestation-levels",
          "parent": "name-claim-evidence-mapping",
          "action": "merge-proposed",
          "reason": "Attestation categories are a required part of evidence mapping.",
          "parentId": "nw-name-claim-evidence-mapping",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-name-data-transliteration-provenance",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Task A: Distinguish attested form, inferred combination and invented form. Task B: Record the system and manual exceptions for each form. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-historical-pseudonym-evidence",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Distinguish attested form, inferred combination and invented form. Task B: Distinguish documented pseudonyms from author invented analogues. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-historical-fiction-composite-names",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Distinguish attested form, inferred combination and invented form. Task B: Document invented combinations and avoid presenting them as attested. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Distinguish attested form, inferred combination and invented form",
        "outline": [
          "Explain the specific decision: Distinguish attested form, inferred combination and invented form",
          "Define the applicable contract and limits for Name data attestation levels",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Distinguish attested form, inferred combination and invented form; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Distinguish attested form, inferred combination and invented form",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Attestation categories are a required part of evidence mapping."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:977",
      "profileSource": "data/profiles.json#data-methods",
      "disposition": {
        "action": "merged",
        "parentId": "nw-name-claim-evidence-mapping",
        "reason": "Attestation categories are a required part of evidence mapping.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-data-creative-interpretation",
      "slug": "name-data-creative-interpretation",
      "name": "Name data creative interpretation",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-creative-interpretation/",
        "ja": "/ja/tools/name-data-creative-interpretation/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Store author associations apart from dictionary facts",
      "task": "Store author associations apart from dictionary facts",
      "searchIntent": {
        "primary": "Complete the task: Store author associations apart from dictionary facts",
        "queryHypothesis": "name data creative interpretation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to store author associations apart from dictionary facts?",
        "When should name data creative interpretation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Store author associations apart from dictionary facts",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Store author associations apart from dictionary facts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Name claim evidence mapping. Creative interpretation separation belongs in every claim record.",
        "deskReview": {
          "candidate": "name-data-creative-interpretation",
          "parent": "name-claim-evidence-mapping",
          "action": "merge-proposed",
          "reason": "Creative interpretation separation belongs in every claim record.",
          "parentId": "nw-name-claim-evidence-mapping",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-character-name-evidence-ledger",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Store author associations apart from dictionary facts. Task B: Separate verified cultural claims from author associations. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-invented-reading-disclosure",
          "title": 0,
          "task": 0.1111111111111111,
          "score": 0.07222222222222222,
          "sharedProfile": false,
          "difference": "Task A: Store author associations apart from dictionary facts. Task B: Label an author invented reading as fictional. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-data-attestation-levels",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Store author associations apart from dictionary facts. Task B: Distinguish attested form, inferred combination and invented form. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Store author associations apart from dictionary facts",
        "outline": [
          "Explain the specific decision: Store author associations apart from dictionary facts",
          "Define the applicable contract and limits for Name data creative interpretation",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Store author associations apart from dictionary facts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Store author associations apart from dictionary facts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Creative interpretation separation belongs in every claim record."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:984",
      "profileSource": "data/profiles.json#data-methods",
      "disposition": {
        "action": "merged",
        "parentId": "nw-name-claim-evidence-mapping",
        "reason": "Creative interpretation separation belongs in every claim record.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-naming-method-transfer-exercise",
      "slug": "naming-method-transfer-exercise",
      "name": "Naming method transfer exercise",
      "category": "editorial-content",
      "urls": {
        "en": "/en/tools/naming-method-transfer-exercise/",
        "ja": "/ja/tools/naming-method-transfer-exercise/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "writers learning naming through practice",
      "scenario": "Translate a demonstrated technique into the user's own brief",
      "task": "Translate a demonstrated technique into the user's own brief",
      "searchIntent": {
        "primary": "Complete the task: Translate a demonstrated technique into the user's own brief",
        "queryHypothesis": "naming method transfer exercise",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to translate a demonstrated technique into the user's own brief?",
        "When should naming method transfer exercise be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "authored scene: anchor the exercise",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "two naming decisions: define a controlled comparison",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "story stakes: explain the consequence",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior"
      ],
      "requiredData": [
        {
          "description": "original author supplied passage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "explicit decision alternatives",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "story function rubric",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Translate a demonstrated technique into the user's own brief",
        "all generated stories must be labeled fictional examples",
        "an exercise must change the scene's actual behavior",
        "Proposed category workflow: scene → controlled alternatives → consequence analysis → method transfer",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "scene revision plan",
        "before and after naming consequences",
        "transfer questions for the user's work"
      ],
      "capabilities": [
        "hold story facts fixed while varying one naming decision",
        "annotate the exact line where a naming choice affects interpretation"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Translate a demonstrated technique into the user's own brief. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "merge-proposed: Naming scene laboratory. Method transfer is an article's learning outcome and exercise, not a standalone public tool unless a real interactive decision is demonstrated.",
        "deskReview": {
          "candidate": "naming-method-transfer-exercise",
          "parent": "naming-scene-laboratory",
          "action": "merge-proposed",
          "reason": "Method transfer is an article's learning outcome and exercise, not a standalone public tool unless a real interactive decision is demonstrated.",
          "parentId": "nw-naming-scene-laboratory",
          "status": "proposal-not-human-signoff"
        }
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-positioning-exercise",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Task A: Translate a demonstrated technique into the user's own brief. Task B: Compare byline presentations using a declared audience brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-ocean-species-visual-names",
          "title": 0,
          "task": 0.16666666666666666,
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Task A: Translate a demonstrated technique into the user's own brief. Task B: Translate authored color patterns into reader usable names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-clan-adoption-naming",
          "title": 0,
          "task": 0.15384615384615385,
          "score": 0.1,
          "sharedProfile": false,
          "difference": "Task A: Translate a demonstrated technique into the user's own brief. Task B: Integrate an outsider into an invented clan's explicit rules. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Translate a demonstrated technique into the user's own brief",
        "outline": [
          "Explain the specific decision: Translate a demonstrated technique into the user's own brief",
          "Define the applicable contract and limits for Naming method transfer exercise",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Translate a demonstrated technique into the user's own brief; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Translate a demonstrated technique into the user's own brief",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development.",
        "merge-proposed: Method transfer is an article's learning outcome and exercise, not a standalone public tool unless a real interactive decision is demonstrated."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:970",
      "profileSource": "data/profiles.json#editorial-content",
      "disposition": {
        "action": "merged",
        "parentId": "nw-naming-scene-laboratory",
        "reason": "Method transfer is an article's learning outcome and exercise, not a standalone public tool unless a real interactive decision is demonstrated.",
        "reopenIf": "Demonstrate a different main task and at least two behavioral differences before reconsidering.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-author-byline-preview",
      "slug": "author-byline-preview",
      "name": "Author byline preview",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/author-byline-preview/",
        "ja": "/ja/tools/author-byline-preview/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Compare supplied pen names across cover, spine and article bylines",
      "task": "Compare supplied pen names across cover, spine and article bylines",
      "searchIntent": {
        "primary": "Complete the task: Compare supplied pen names across cover, spine and article bylines",
        "queryHypothesis": "author byline preview",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare supplied pen names across cover, spine and article bylines?",
        "When should author byline preview be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "byline",
          "use": "Exact approved text and reading without requiring legal identity."
        },
        {
          "key": "surfaces",
          "use": "Cover, spine and contributor-list widths and font metrics."
        },
        {
          "key": "fallbackPolicy",
          "use": "Explicit approved initials or punctuation variants."
        }
      ],
      "rules": [
        "Preserve the original form in every comparison.",
        "Use measured glyph bounds where available; label estimates otherwise.",
        "Never shrink below the declared minimum readable size.",
        "A layout proof does not imply domain or trademark availability.",
        "Compare the same name across configured surfaces"
      ],
      "requiredData": [
        {
          "description": "Original surface fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Actual font measurements or labeled estimates",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Approved alternate forms",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Preserve the original form in every comparison.",
        "Use measured glyph bounds where available; label estimates otherwise.",
        "Never shrink below the declared minimum readable size.",
        "A layout proof does not imply domain or trademark availability."
      ],
      "outputs": [
        "Surface-by-surface proof",
        "Overflow and approximation status",
        "Scoped fallback choice",
        "Surface proof with overflow"
      ],
      "capabilities": [
        "Compare the same name across cover and spine constraints.",
        "Preview a fallback without silently changing public identity everywhere."
      ],
      "contractScope": "task-specific-design-not-implemented",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Provisional production task: proof a fixed approved author identity on real credit surfaces, separate from generating candidates; merge into pen-name design if the handoff does not justify a page.",
        "proposedDifferenceAxes": [
          "inputs",
          "outputs",
          "evaluation",
          "workflow"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "pen-name-designer",
          "difference": "Consumes an accepted name and returns a production proof plus overflow decisions, rather than ranking new identities."
        }
      },
      "nearestTools": [
        {
          "id": "nw-bilingual-author-byline",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Compare supplied pen names across cover, spine and article bylines. Task B: Coordinate English and Japanese forms without counting two tools. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-translation-brief",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": true,
          "difference": "Task A: Compare supplied pen names across cover, spine and article bylines. Task B: Preserve author intent across localized bylines. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-author-rebrand-timeline",
          "title": 0.2,
          "task": 0.09090909090909091,
          "score": 0.1290909090909091,
          "sharedProfile": true,
          "difference": "Task A: Compare supplied pen names across cover, spine and article bylines. Task B: Schedule name changes across a backlist and active series. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "A byline needs a production proof after the naming decision, not an unsupported assurance of readability.",
        "outline": [
          "Freeze the identity before testing layout",
          "Measure the surface you will ship",
          "One byline on a cover and a narrow spine",
          "Approve fallbacks by surface"
        ],
        "story": "Fictional example: a collective author's long name fits a cover but not its spine. The production team approves an initialed spine form while preserving the full credit on the title page.",
        "storyAnalysis": "A scoped layout choice avoids an unnecessary author rebrand. Prototype evidence must decide whether this merits a separate page.",
        "evidence": "Original layout dimensions; real-font measurements and editor review still required.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Reducing width can change fit while text stays fixed.",
        "Unknown font metrics remain estimated.",
        "A minimum size is enforced.",
        "Original punctuation remains in the source record.",
        "Narrower width flags the same long name"
      ],
      "status": "merged",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:211",
      "profileSource": "data/profiles.json#pen-names",
      "absorbedModules": [
        {
          "sourceId": "nw-pen-name-typography-comparison",
          "input": "fontAndWidth",
          "rule": "Compare the same name across configured surfaces",
          "output": "Surface proof with overflow",
          "acceptance": "Narrower width flags the same long name",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "specBatch": "batch-01",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-pen-name-designer",
        "reason": "The implemented pen-name workbench now accepts an approved shortlist, measures cover/spine surfaces, preserves originals and scoped variants, and exports the credit sheet. A separate byline page adds no different primary task or two substantive behavioral differences.",
        "reopenIf": "A later production workflow demonstrates a different main task and at least two verified differences; a font or width option alone is insufficient.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-historical-birth-cohort-shortlist",
      "slug": "historical-birth-cohort-shortlist",
      "name": "Historical birth cohort shortlist",
      "category": "historical-research",
      "urls": {
        "en": "/en/tools/historical-birth-cohort-shortlist/",
        "ja": "/ja/tools/historical-birth-cohort-shortlist/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "historically situated fiction creators",
      "scenario": "Compare candidates only against dated source coverage",
      "task": "Compare candidates only against dated source coverage",
      "searchIntent": {
        "primary": "Complete the task: Compare candidates only against dated source coverage",
        "queryHypothesis": "historical birth cohort shortlist",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare candidates only against dated source coverage?",
        "When should historical birth cohort shortlist be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "period and locality: bound claims",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "primary source references: support attestation",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "transcription uncertainty: preserve alternatives",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations"
      ],
      "requiredData": [
        {
          "description": "user supplied archival references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "license and provenance ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "specialist review notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare candidates only against dated source coverage",
        "do not extrapolate a source sample to an entire culture",
        "mark invented composites and unsupported pronunciations",
        "Proposed category workflow: research scope → source evaluation → candidate evidence → specialist review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "evidence bounded candidate notes",
        "attestation inference invention labels",
        "unresolved research questions"
      ],
      "capabilities": [
        "compare contradictory sources without silent resolution",
        "export precise questions for a qualified historical reviewer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare candidates only against dated source coverage. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-game-font-glyph-audit",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Compare candidates only against dated source coverage. Task B: Verify approved name characters against actual font coverage. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-historical-parish-record-naming",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": true,
          "difference": "Task A: Compare candidates only against dated source coverage. Task B: Distinguish transcription uncertainty from source attestation. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-protagonist-name-shortlist",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Task A: Compare candidates only against dated source coverage. Task B: Compare a central character against the existing story vocabulary. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare candidates only against dated source coverage",
        "outline": [
          "Explain the specific decision: Compare candidates only against dated source coverage",
          "Define the applicable contract and limits for Historical birth cohort shortlist",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare candidates only against dated source coverage; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare candidates only against dated source coverage",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:839",
      "profileSource": "data/profiles.json#historical-research",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-age-cohort-naming",
        "reason": "Both tasks compare a candidate spelling with dated source coverage. The implemented age-to-birth-window and annual evidence workflow includes the same historical shortlist task; a separate page has no different primary decision.",
        "reopenIf": "Demonstrate a different main task and two substantive behavioral differences beyond another period or a source selector.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-sibling-name-differentiation",
      "slug": "sibling-name-differentiation",
      "name": "Sibling name differentiation",
      "category": "kinship",
      "urls": {
        "en": "/en/tools/sibling-name-differentiation/",
        "ja": "/ja/tools/sibling-name-differentiation/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "family saga authors and comics writers",
      "scenario": "Preserve family resemblance while preventing sibling confusion",
      "task": "Preserve family resemblance while preventing sibling confusion",
      "searchIntent": {
        "primary": "Complete the task: Preserve family resemblance while preventing sibling confusion",
        "queryHypothesis": "sibling name differentiation",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve family resemblance while preventing sibling confusion?",
        "When should sibling name differentiation be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "siblings",
          "use": "Stable IDs and confirmed relationship links."
        },
        {
          "key": "sharedMarker",
          "use": "Explicit fictional family marker, not an inferred cultural custom."
        },
        {
          "key": "readings",
          "use": "Approved short forms for all sibling pairs."
        }
      ],
      "rules": [
        "Shared markers never waive distinguishability checks.",
        "Evaluate every sibling pair, including twin and triplet groups.",
        "Keep birth-order assumptions separate from actual relationships.",
        "Lock existing identities before suggesting minimal edits.",
        "Shared marker does not exempt a pair from collision review",
        "Evaluate all three pairs in a three-person introduction"
      ],
      "requiredData": [
        {
          "description": "Authored sibling graph",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Confirmed readings and shared marker rule",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Shared markers never waive distinguishability checks.",
        "Evaluate every sibling pair, including twin and triplet groups.",
        "Keep birth-order assumptions separate from actual relationships.",
        "Lock existing identities before suggesting minimal edits."
      ],
      "outputs": [
        "Pairwise resemblance and confusion table",
        "Marker compliance",
        "Minimal unlocked alternatives",
        "Pair link and separate short forms",
        "Three pairwise findings"
      ],
      "capabilities": [
        "Compare resemblance with and without a shared marker.",
        "Identify which member of an introduction group causes the most pair collisions."
      ],
      "contractScope": "task-specific-design-not-implemented",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Provisional distinction: jointly satisfy a household's shared naming markers and scene-level distinguishability. It may instead be a family-planner mode plus ensemble review.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "evaluation"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "family-name-planner",
          "difference": "Family planning propagates inheritance; this proposes tuning given-name resemblance. If no distinct workflow emerges, merge rather than publish."
        }
      },
      "nearestTools": [
        {
          "id": "nw-clone-identity-differentiation",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": false,
          "difference": "Task A: Preserve family resemblance while preventing sibling confusion. Task B: Assign legal, personal and laboratory identities to cloned characters. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-estranged-sibling-name-clues",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Preserve family resemblance while preventing sibling confusion. Task B: Control how much shared structure reveals relatedness. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-family-branch-differentiation",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Preserve family resemblance while preventing sibling confusion. Task B: Mark branches without treating all cousins as interchangeable. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Family resemblance should help establish relationships without making relatives interchangeable.",
        "outline": [
          "Choose what should be shared",
          "Compare actual dialogue forms",
          "Three siblings at a roll call",
          "When this belongs in the parent family tool"
        ],
        "story": "Fictional example: three siblings preserve a shared family component but use distinct short forms during a workshop roll call. A twin-pair preset initially hid a sound collision and is corrected.",
        "storyAnalysis": "The rule that creates belonging cannot double as an exemption from reader clarity. The page's own independence remains a testable question.",
        "evidence": "Original pair fixtures; independent-page decision held pending prototype.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Triplets produce three pair evaluations.",
        "A locked name is not edited.",
        "Different spellings with identical approved readings are flagged.",
        "Removing a shared marker changes compliance without altering kinship.",
        "Two same-reading twins remain flagged despite an intentional link",
        "Three names produce exactly three comparisons"
      ],
      "status": "merged",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:40",
      "profileSource": "data/profiles.json#kinship",
      "absorbedModules": [
        {
          "sourceId": "nw-twin-character-names",
          "input": "intentionalPairLinks",
          "rule": "Shared marker does not exempt a pair from collision review",
          "output": "Pair link and separate short forms",
          "acceptance": "Two same-reading twins remain flagged despite an intentional link",
          "status": "implemented-under-acceptance-review"
        },
        {
          "sourceId": "nw-triplet-introduction-names",
          "input": "introductionGroups",
          "rule": "Evaluate all three pairs in a three-person introduction",
          "output": "Three pairwise findings",
          "acceptance": "Three names produce exactly three comparisons",
          "status": "implemented-under-acceptance-review"
        }
      ],
      "specBatch": "batch-01",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-family-name-planner",
        "reason": "The family workbench now evaluates all pairs in an authored introduction group, checks required shared markers separately, preserves locks, and reports confirmed-reading collisions. Sibling or triplet selection is a scoped group within the same joint naming task.",
        "reopenIf": "Show a different primary task and two meaningful differences beyond kinship/group-size presets.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-character-introduction-naming",
      "slug": "character-introduction-naming",
      "name": "Character introduction naming",
      "category": "character-foundations",
      "urls": {
        "en": "/en/tools/character-introduction-naming/",
        "ja": "/ja/tools/character-introduction-naming/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "novelists and character designers",
      "scenario": "Stage first reference, full introduction and later short forms",
      "task": "Stage first reference, full introduction and later short forms",
      "searchIntent": {
        "primary": "Complete the task: Stage first reference, full introduction and later short forms",
        "queryHypothesis": "character introduction naming",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to stage first reference, full introduction and later short forms?",
        "When should character introduction naming be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "forms",
          "use": "List full, short, title and concealed forms with stable identity ID."
        },
        {
          "key": "sceneOrder",
          "use": "Locate first use and when the reader can connect two forms."
        },
        {
          "key": "viewpoint",
          "use": "Restrict what narrator and reader can know."
        }
      ],
      "rules": [
        "Every short reference needs a disclosed identity connection or an intentional ambiguity marker.",
        "Do not reveal a hidden form in a recap before its scene.",
        "Distinguish character knowledge from reader knowledge.",
        "Keep an unnamed introduction available as an intentional choice."
      ],
      "requiredData": [
        {
          "description": "Authored scene sequence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "Identity forms and reveal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Every short reference needs a disclosed identity connection or an intentional ambiguity marker.",
        "Do not reveal a hidden form in a recap before its scene.",
        "Distinguish character knowledge from reader knowledge.",
        "Keep an unnamed introduction available as an intentional choice."
      ],
      "outputs": [
        "First-use timeline",
        "Unconnected short-form warnings",
        "Alternative disclosure order"
      ],
      "capabilities": [
        "Compare immediate naming with staged disclosure in the same scene.",
        "Trace a later nickname back to the scene that teaches its referent."
      ],
      "contractScope": "task-specific-design-not-implemented",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Design the order in which readers learn identity forms across a scene sequence; output is a disclosure plan, not a fresh name.",
        "proposedDifferenceAxes": [
          "inputs",
          "rules",
          "outputs"
        ],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences.",
        "designComparison": {
          "nearest": "large-cast-introduction-pacing",
          "difference": "Possible parent-child overlap: this focuses one identity's reference chain; cast pacing coordinates introductions among many people. Prototype must justify the split."
        }
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-nickname-introduction",
          "title": 0.3333333333333333,
          "task": 0.23076923076923078,
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Stage first reference, full introduction and later short forms. Task B: Find short forms with no reader facing connection to a full name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-introduction-rewrite",
          "title": 0.5,
          "task": 0.07692307692307693,
          "score": 0.22499999999999998,
          "sharedProfile": false,
          "difference": "Task A: Stage first reference, full introduction and later short forms. Task B: Revise a supplied introduction to make identity clear sooner. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-furigana-introduction-plan",
          "title": 0.25,
          "task": 0.16666666666666666,
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Task A: Stage first reference, full introduction and later short forms. Task B: Schedule reading support at first and later appearances. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Introduce the reference readers will actually need, at the moment they can use it.",
        "outline": [
          "Name presence and identity clarity differ",
          "Connect short forms explicitly",
          "A station platform with two introductions",
          "Check the recap after changing the opening"
        ],
        "story": "Fictional example: a conductor first calls a traveler by ticket number and later hears a companion use a nickname. One linking exchange lets readers understand both references without revealing a concealed surname.",
        "storyAnalysis": "Replacing all forms with the full name improves recognition but destroys the deliberate knowledge boundary.",
        "evidence": "Original scene and identity linkage fixtures; reader study pending.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "A nickname preceding its connection is flagged.",
        "Intentionally unnamed identity is not auto-filled.",
        "A viewpoint change does not grant hidden knowledge.",
        "Moving an introduction updates dependent short-form warnings."
      ],
      "status": "merged",
      "specMaturity": "detailed-design",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Detailed contract is a design artifact, not executed behavior or independent-value approval."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:14",
      "profileSource": "data/profiles.json#character-foundations",
      "specBatch": "batch-01",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-true-name-alias-bridge",
        "reason": "Implemented first-use forms, explicit connection events, intentional unnamed/ambiguous introductions and recap checks use the same single-identity observer/chapter knowledge state as alias disclosure. The primary decision remains which identity reference this observer can understand now; a separate page is not justified by adding a connection timeline.",
        "reopenIf": "Demonstrate a different primary user task and two substantive behavioral differences beyond a timeline view or scene-order preset. Multi-character pacing remains a separate candidate requiring review.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-spelling-recall",
      "slug": "pen-name-spelling-recall",
      "name": "Pen name spelling recall",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-spelling-recall/",
        "ja": "/ja/tools/pen-name-spelling-recall/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Design a reader recall test for supplied candidates",
      "task": "Design a reader recall test for supplied candidates",
      "searchIntent": {
        "primary": "Complete the task: Design a reader recall test for supplied candidates",
        "queryHypothesis": "pen name spelling recall",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to design a reader recall test for supplied candidates?",
        "When should pen name spelling recall be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Design a reader recall test for supplied candidates",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Design a reader recall test for supplied candidates. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-naming-system-reader-load",
          "title": 0,
          "task": 0.3333333333333333,
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Task A: Design a reader recall test for supplied candidates. Task B: Test grammar complexity against reader recall exercises. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-localized-name-memory-test",
          "title": 0,
          "task": 0.3333333333333333,
          "score": 0.21666666666666667,
          "sharedProfile": false,
          "difference": "Task A: Design a reader recall test for supplied candidates. Task B: Compare reader recall using language specific test prompts. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-cast-delayed-recall-test",
          "title": 0.16666666666666666,
          "task": 0.2,
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Task A: Design a reader recall test for supplied candidates. Task B: Test recall after a defined reading passage and delay. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Design a reader recall test for supplied candidates",
        "outline": [
          "Explain the specific decision: Design a reader recall test for supplied candidates",
          "Define the applicable contract and limits for Pen name spelling recall",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Design a reader recall test for supplied candidates; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Design a reader recall test for supplied candidates",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:213",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-name-memorability-test",
        "reason": "The implemented recall ledger already prepares exposure/blank response sheets for supplied target spellings, records condition-specific anonymous answers and actual denominators, and preserves raw strings. Changing the targets from character names to author credits or labeling an external exposure a mock cover does not create a different primary task. Visual byline proof remains in the pen-name workbench; this merger makes no automatic reader-administration or cover-rendering claim.",
        "reopenIf": "Demonstrate a different primary task and two substantive behavioral differences beyond an author/character preset or a different externally prepared exposure. A genuinely administered experiment would need its own tested workflow, not a new title.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-byline-recall-test",
      "slug": "pen-name-byline-recall-test",
      "name": "Pen name byline recall test",
      "category": "reader-tests",
      "urls": {
        "en": "/en/tools/pen-name-byline-recall-test/",
        "ja": "/ja/tools/pen-name-byline-recall-test/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and editorial teams",
      "scenario": "Compare remembered author forms after a mock cover exposure",
      "task": "Compare remembered author forms after a mock cover exposure",
      "searchIntent": {
        "primary": "Complete the task: Compare remembered author forms after a mock cover exposure",
        "queryHypothesis": "pen name byline recall test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare remembered author forms after a mock cover exposure?",
        "When should pen name byline recall test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "test hypothesis: state intended effect",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stimulus and exposure conditions: make results interpretable",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "raw responses: preserve disagreements",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses"
      ],
      "requiredData": [
        {
          "description": "author test materials",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "consented minimized responses",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "order and timing log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare remembered author forms after a mock cover exposure",
        "do not convert a small convenience sample into objective authority",
        "keep heuristic ranking separate from measured responses",
        "Proposed category workflow: hypothesis → stimulus → response capture → bounded interpretation",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "raw and summarized responses",
        "method and limitations",
        "revision options tied to observations"
      ],
      "capabilities": [
        "counterbalance supplied candidate order",
        "show rank changes under explicit heuristic weights"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare remembered author forms after a mock cover exposure. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-cast-delayed-recall-test",
          "title": 0.3333333333333333,
          "task": 0.07692307692307693,
          "score": 0.16666666666666666,
          "sharedProfile": true,
          "difference": "Task A: Compare remembered author forms after a mock cover exposure. Task B: Test recall after a defined reading passage and delay. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-consistency-audit",
          "title": 0.16666666666666666,
          "task": 0.16666666666666666,
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Compare remembered author forms after a mock cover exposure. Task B: Find mismatched author forms across a supplied publication list. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-spelling-recall",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Task A: Compare remembered author forms after a mock cover exposure. Task B: Design a reader recall test for supplied candidates. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare remembered author forms after a mock cover exposure",
        "outline": [
          "Explain the specific decision: Compare remembered author forms after a mock cover exposure",
          "Define the applicable contract and limits for Pen name byline recall test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare remembered author forms after a mock cover exposure; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare remembered author forms after a mock cover exposure",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:923",
      "profileSource": "data/profiles.json#reader-tests",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-name-memorability-test",
        "reason": "The implemented recall ledger already prepares exposure/blank response sheets for supplied target spellings, records condition-specific anonymous answers and actual denominators, and preserves raw strings. Changing the targets from character names to author credits or labeling an external exposure a mock cover does not create a different primary task. Visual byline proof remains in the pen-name workbench; this merger makes no automatic reader-administration or cover-rendering claim.",
        "reopenIf": "Demonstrate a different primary task and two substantive behavioral differences beyond an author/character preset or a different externally prepared exposure. A genuinely administered experiment would need its own tested workflow, not a new title.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-battlefield-earned-epithet",
      "slug": "battlefield-earned-epithet",
      "name": "Battlefield earned epithet",
      "category": "titles",
      "urls": {
        "en": "/en/tools/battlefield-earned-epithet/",
        "ja": "/ja/tools/battlefield-earned-epithet/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Contrast the holder's view with allied and enemy interpretations",
      "task": "Contrast the holder's view with allied and enemy interpretations",
      "searchIntent": {
        "primary": "Complete the task: Contrast the holder's view with allied and enemy interpretations",
        "queryHypothesis": "battlefield earned epithet",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to contrast the holder's view with allied and enemy interpretations?",
        "When should battlefield earned epithet be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Contrast the holder's view with allied and enemy interpretations",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Contrast the holder's view with allied and enemy interpretations. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-construct-creator-assigned-name",
          "title": 0,
          "task": 0.16666666666666666,
          "score": 0.10833333333333334,
          "sharedProfile": false,
          "difference": "Task A: Contrast the holder's view with allied and enemy interpretations. Task B: Contrast creator labels with the construct's self identification. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-epithet-builder",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Contrast the holder's view with allied and enemy interpretations. Task B: Connect an epithet to an authored deed and observer perspective. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-defamatory-epithet-perspective",
          "title": 0.2,
          "task": 0,
          "score": 0.06999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Contrast the holder's view with allied and enemy interpretations. Task B: Label hostile naming as a viewpoint claim with consequences. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Contrast the holder's view with allied and enemy interpretations",
        "outline": [
          "Explain the specific decision: Contrast the holder's view with allied and enemy interpretations",
          "Define the applicable contract and limits for Battlefield earned epithet",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Contrast the holder's view with allied and enemy interpretations; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Contrast the holder's view with allied and enemy interpretations",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:585",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-epithet-builder",
        "reason": "Allied and enemy interpretations are audience IDs with praising/hostile adoption, while the holder’s own refusal is a separate stance. A battlefield setting does not create a new primary task.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior changes beyond event setting, subject lifetime, audience allegiance or praise/hostility presets. Legal evaluation or historical entitlement is not within this fictional model.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-hero-reputation-names",
      "slug": "hero-reputation-names",
      "name": "Hero reputation names",
      "category": "titles",
      "urls": {
        "en": "/en/tools/hero-reputation-names/",
        "ja": "/ja/tools/hero-reputation-names/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Compare local reputations across different communities",
      "task": "Compare local reputations across different communities",
      "searchIntent": {
        "primary": "Complete the task: Compare local reputations across different communities",
        "queryHypothesis": "hero reputation names",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare local reputations across different communities?",
        "When should hero reputation names be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare local reputations across different communities",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare local reputations across different communities. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-immortal-reputation-names",
          "title": 0.3333333333333333,
          "task": 0.3333333333333333,
          "score": 0.3333333333333333,
          "sharedProfile": false,
          "difference": "Task A: Compare local reputations across different communities. Task B: Track names across communities and centuries. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-changes-surname-after-exile",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Compare local reputations across different communities. Task B: Preserve continuity across home and adopted communities. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-border-town-name-register",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Compare local reputations across different communities. Task B: Map local and official forms across a fictional frontier. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare local reputations across different communities",
        "outline": [
          "Explain the specific decision: Compare local reputations across different communities",
          "Define the applicable contract and limits for Hero reputation names",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare local reputations across different communities; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare local reputations across different communities",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:591",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-epithet-builder",
        "reason": "Comparing local reputations across communities is the implemented audience matrix itself; the heroic framing is proposed wording and adoption data.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior changes beyond event setting, subject lifetime, audience allegiance or praise/hostility presets. Legal evaluation or historical entitlement is not within this fictional model.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-defamatory-epithet-perspective",
      "slug": "defamatory-epithet-perspective",
      "name": "Defamatory epithet perspective",
      "category": "titles",
      "urls": {
        "en": "/en/tools/defamatory-epithet-perspective/",
        "ja": "/ja/tools/defamatory-epithet-perspective/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Label hostile naming as a viewpoint claim with consequences",
      "task": "Label hostile naming as a viewpoint claim with consequences",
      "searchIntent": {
        "primary": "Complete the task: Label hostile naming as a viewpoint claim with consequences",
        "queryHypothesis": "defamatory epithet perspective",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to label hostile naming as a viewpoint claim with consequences?",
        "When should defamatory epithet perspective be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Label hostile naming as a viewpoint claim with consequences",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Label hostile naming as a viewpoint claim with consequences. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-historical-name-fact-annotation",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Label hostile naming as a viewpoint claim with consequences. Task B: Label attestation, inference and invention at claim level. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-epithet-builder",
          "title": 0.25,
          "task": 0,
          "score": 0.0875,
          "sharedProfile": true,
          "difference": "Task A: Label hostile naming as a viewpoint claim with consequences. Task B: Connect an epithet to an authored deed and observer perspective. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-rejects-family-name",
          "title": 0,
          "task": 0.125,
          "score": 0.08125,
          "sharedProfile": false,
          "difference": "Task A: Label hostile naming as a viewpoint claim with consequences. Task B: Track practical and relational consequences in authored scenes. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Label hostile naming as a viewpoint claim with consequences",
        "outline": [
          "Explain the specific decision: Label hostile naming as a viewpoint claim with consequences",
          "Define the applicable contract and limits for Defamatory epithet perspective",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Label hostile naming as a viewpoint claim with consequences; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Label hostile naming as a viewpoint claim with consequences",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:604",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-epithet-builder",
        "reason": "The implemented hostile-use branch keeps attribution, knowledge, deed prerequisites and personal refusal separate. A hostile preset adds no new primary task; no legal defamation assessment is promised.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior changes beyond event setting, subject lifetime, audience allegiance or praise/hostility presets. Legal evaluation or historical entitlement is not within this fictional model.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-posthumous-epithet-revision",
      "slug": "posthumous-epithet-revision",
      "name": "Posthumous epithet revision",
      "category": "titles",
      "urls": {
        "en": "/en/tools/posthumous-epithet-revision/",
        "ja": "/ja/tools/posthumous-epithet-revision/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Compare reputation changes after new evidence in the story",
      "task": "Compare reputation changes after new evidence in the story",
      "searchIntent": {
        "primary": "Complete the task: Compare reputation changes after new evidence in the story",
        "queryHypothesis": "posthumous epithet revision",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare reputation changes after new evidence in the story?",
        "When should posthumous epithet revision be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare reputation changes after new evidence in the story",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare reputation changes after new evidence in the story. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-name-test-revision-comparison",
          "title": 0.2,
          "task": 0.09090909090909091,
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Task A: Compare reputation changes after new evidence in the story. Task B: Compare before and after candidates with disclosed test conditions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-existing-pen-name-revision",
          "title": 0.2,
          "task": 0.08333333333333333,
          "score": 0.12416666666666666,
          "sharedProfile": false,
          "difference": "Task A: Compare reputation changes after new evidence in the story. Task B: Plan continuity notes and old to new credit mappings. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-live-roleplay-alias-reveal",
          "title": 0,
          "task": 0.18181818181818182,
          "score": 0.1181818181818182,
          "sharedProfile": false,
          "difference": "Task A: Compare reputation changes after new evidence in the story. Task B: Schedule badge or roster changes at an agreed story event. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare reputation changes after new evidence in the story",
        "outline": [
          "Explain the specific decision: Compare reputation changes after new evidence in the story",
          "Define the applicable contract and limits for Posthumous epithet revision",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare reputation changes after new evidence in the story; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare reputation changes after new evidence in the story",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:606",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-character-epithet-builder",
        "reason": "Reputation changes after new evidence use pinned deed revisions, audience transmission and scene comparison. A deceased subject has no forced current stance; death alone does not change this task.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior changes beyond event setting, subject lifetime, audience allegiance or praise/hostility presets. Legal evaluation or historical entitlement is not within this fictional model.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-artificial-person-chosen-identity",
      "slug": "artificial-person-chosen-identity",
      "name": "Artificial person chosen identity",
      "category": "identities",
      "urls": {
        "en": "/en/tools/artificial-person-chosen-identity/",
        "ja": "/ja/tools/artificial-person-chosen-identity/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "mystery, thriller and transformation writers",
      "scenario": "Separate serial designation from self chosen name",
      "task": "Separate serial designation from self chosen name",
      "searchIntent": {
        "primary": "Complete the task: Separate serial designation from self chosen name",
        "queryHypothesis": "artificial person chosen identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate serial designation from self chosen name?",
        "When should artificial person chosen identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "stable identity ID: link name layers",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "scene knowledge states: prevent premature disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "reveal timeline: gate public forms",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "render only identities available to the selected observer",
        "separate writer known truth from character belief"
      ],
      "requiredData": [
        {
          "description": "identity state machine",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and observer ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored clue dependencies",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate serial designation from self chosen name",
        "render only identities available to the selected observer",
        "separate writer known truth from character belief",
        "Proposed category workflow: identity layers → knowledge matrix → scene simulation → reveal audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "public and private identity layers",
        "knowledge violation warnings",
        "before and after reveal references"
      ],
      "capabilities": [
        "simulate one observer at one scene boundary",
        "audit earlier clues after a reveal revision"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate serial designation from self chosen name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-robot-production-batch-identity",
          "title": 0.14285714285714285,
          "task": 0.3333333333333333,
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Separate serial designation from self chosen name. Task B: Separate batch, serial and chosen personal identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-artificial-intelligence-instance-names",
          "title": 0.16666666666666666,
          "task": 0.2857142857142857,
          "score": 0.24404761904761904,
          "sharedProfile": false,
          "difference": "Task A: Separate serial designation from self chosen name. Task B: Distinguish model, instance and self chosen name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-ghost-former-living-name",
          "title": 0,
          "task": 0.2857142857142857,
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Task A: Separate serial designation from self chosen name. Task B: Separate remembered, forgotten and self chosen identities. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate serial designation from self chosen name",
        "outline": [
          "Explain the specific decision: Separate serial designation from self chosen name",
          "Define the applicable contract and limits for Artificial person chosen identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate serial designation from self chosen name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "ink",
        "renpy",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate serial designation from self chosen name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:148",
      "profileSource": "data/profiles.json#identities",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-robot-serial-to-personal-name",
        "reason": "Separating a technical designation from an authored self-choice is now the implemented registry’s primary task. Claim types, effective choice intervals, exact technical keys and personal displays are already distinct; changing the species label adds no new behavior.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior differences beyond a robot/artificial-person preset, another prefix grammar or a different batch label. Philosophical personhood and real consent certification remain outside this tool.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-robot-production-batch-identity",
      "slug": "robot-production-batch-identity",
      "name": "Robot production batch identity",
      "category": "institutions",
      "urls": {
        "en": "/en/tools/robot-production-batch-identity/",
        "ja": "/ja/tools/robot-production-batch-identity/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and ensemble creators",
      "scenario": "Separate batch, serial and chosen personal identity",
      "task": "Separate batch, serial and chosen personal identity",
      "searchIntent": {
        "primary": "Complete the task: Separate batch, serial and chosen personal identity",
        "queryHypothesis": "robot production batch identity",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate batch, serial and chosen personal identity?",
        "When should robot production batch identity be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "fictional membership rules: establish authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "join leave and rank events: change eligibility",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "personal preferences: expose coercion and refusal",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title"
      ],
      "requiredData": [
        {
          "description": "original institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "membership timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "name assignment and refusal events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate batch, serial and chosen personal identity",
        "membership labels and personal identities remain separately addressable",
        "track who has the authority to assign or revoke a title",
        "Proposed category workflow: charter → membership → assignment → authority and continuity audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "member identity layers",
        "eligibility and authority trace",
        "exception and agency notes"
      ],
      "capabilities": [
        "simulate entering and leaving an institution",
        "audit competing naming authorities"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate batch, serial and chosen personal identity. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-artificial-person-chosen-identity",
          "title": 0.14285714285714285,
          "task": 0.3333333333333333,
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Separate batch, serial and chosen personal identity. Task B: Separate serial designation from self chosen name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-robot-serial-to-personal-name",
          "title": 0.2,
          "task": 0.25,
          "score": 0.23249999999999998,
          "sharedProfile": false,
          "difference": "Task A: Separate batch, serial and chosen personal identity. Task B: Preserve manufacturer designation while allowing chosen identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-playable-character-preset-names",
          "title": 0,
          "task": 0.2857142857142857,
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Task A: Separate batch, serial and chosen personal identity. Task B: Keep defaults distinct from player chosen identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate batch, serial and chosen personal identity",
        "outline": [
          "Explain the specific decision: Separate batch, serial and chosen personal identity",
          "Define the applicable contract and limits for Robot production batch identity",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate batch, serial and chosen personal identity; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate batch, serial and chosen personal identity",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:828",
      "profileSource": "data/profiles.json#institutions",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-robot-serial-to-personal-name",
        "reason": "The implemented registry explicitly separates namespace/serial, batch membership and chosen personal identity, and shows a batch-only reference resolving to multiple individuals. This candidate is the same task, not another independent naming page.",
        "reopenIf": "Demonstrate a different primary creative task and two substantive behavior differences beyond a robot/artificial-person preset, another prefix grammar or a different batch label. Philosophical personhood and real consent certification remain outside this tool.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-collaborative-pen-name",
      "slug": "collaborative-pen-name",
      "name": "Collaborative pen name",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/collaborative-pen-name/",
        "ja": "/ja/tools/collaborative-pen-name/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "Allocate shared credit and member identity under a joint byline",
      "task": "Allocate shared credit and member identity under a joint byline",
      "searchIntent": {
        "primary": "Complete the task: Allocate shared credit and member identity under a joint byline",
        "queryHypothesis": "collaborative pen name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to allocate shared credit and member identity under a joint byline?",
        "When should collaborative pen name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Allocate shared credit and member identity under a joint byline",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Allocate shared credit and member identity under a joint byline. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-pen-name-ruby-credit",
          "title": 0.2,
          "task": 0.15384615384615385,
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Task A: Allocate shared credit and member identity under a joint byline. Task B: Pair byline and reading in publication sized credit previews. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-inherited-pen-name-fiction",
          "title": 0.25,
          "task": 0.08333333333333333,
          "score": 0.14166666666666666,
          "sharedProfile": true,
          "difference": "Task A: Allocate shared credit and member identity under a joint byline. Task B: Track multiple fictional holders of a famous author identity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-positioning-exercise",
          "title": 0.25,
          "task": 0.07692307692307693,
          "score": 0.1375,
          "sharedProfile": false,
          "difference": "Task A: Allocate shared credit and member identity under a joint byline. Task B: Compare byline presentations using a declared audience brief. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Allocate shared credit and member identity under a joint byline",
        "outline": [
          "Explain the specific decision: Allocate shared credit and member identity under a joint byline",
          "Define the applicable contract and limits for Collaborative pen name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Allocate shared credit and member identity under a joint byline; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Allocate shared credit and member identity under a joint byline",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:216",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-collective-author-credit-governance",
        "reason": "The working edition-credit tool already allocates shared public bylines, private member IDs and explicit per-edition credit displays. A collective preset does not create a different primary task. Generating and measuring a candidate remains the pen-name workbench’s connected task, not a second group-credit page.",
        "reopenIf": "Prove a different primary creative task and at least two substantive behavior differences beyond a collective preset, public/internal display option or another question-sheet export. General legal agreement and rights certification are outside this implemented scope.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-pen-name-contributor-agreement-brief",
      "slug": "pen-name-contributor-agreement-brief",
      "name": "Pen name contributor agreement brief",
      "category": "pen-names",
      "urls": {
        "en": "/en/tools/pen-name-contributor-agreement-brief/",
        "ja": "/ja/tools/pen-name-contributor-agreement-brief/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fiction writers and manga authors",
      "scenario": "List credit decisions for later professional review",
      "task": "List credit decisions for later professional review",
      "searchIntent": {
        "primary": "Complete the task: List credit decisions for later professional review",
        "queryHypothesis": "pen name contributor agreement brief",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to list credit decisions for later professional review?",
        "When should pen name contributor agreement brief be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author positioning brief: state intended work",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "public identity boundary: constrain disclosure",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "credit surfaces: test real presentation",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent"
      ],
      "requiredData": [
        {
          "description": "author candidate names",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "byline layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "timestamped external check notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: List credit decisions for later professional review",
        "never claim uniqueness or legal clearance",
        "compare reader supplied responses separately from author intent",
        "Proposed category workflow: brief → signature comparison → reader check → manual external verification",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "byline candidates and previews",
        "readability tradeoffs",
        "external verification checklist"
      ],
      "capabilities": [
        "preview the same candidate across cover and compact credit",
        "track dated collision checks without an availability guarantee"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: List credit decisions for later professional review. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-pen-name-translation-brief",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Task A: List credit decisions for later professional review. Task B: Preserve author intent across localized bylines. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-pen-name-social-handle-mapping",
          "title": 0.14285714285714285,
          "task": 0.1111111111111111,
          "score": 0.1222222222222222,
          "sharedProfile": true,
          "difference": "Task A: List credit decisions for later professional review. Task B: Keep display name and platform identifier decisions separate. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-collaborative-pen-name",
          "title": 0.2,
          "task": 0.07692307692307693,
          "score": 0.12,
          "sharedProfile": true,
          "difference": "Task A: List credit decisions for later professional review. Task B: Allocate shared credit and member identity under a joint byline. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "List credit decisions for later professional review",
        "outline": [
          "Explain the specific decision: List credit decisions for later professional review",
          "Define the applicable contract and limits for Pen name contributor agreement brief",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for List credit decisions for later professional review; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: List credit decisions for later professional review",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:248",
      "profileSource": "data/profiles.json#pen-names",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-collective-author-credit-governance",
        "reason": "Listing exact credit decisions and unresolved scope questions for later review is the implemented private credit-question handoff. Exporting that package does not establish a separate naming task, and the tool does not draft an agreement, interpret law or verify consent.",
        "reopenIf": "Prove a different primary creative task and at least two substantive behavior differences beyond a collective preset, public/internal display option or another question-sheet export. General legal agreement and rights certification are outside this implemented scope.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-game-name-unicode-normalization",
      "slug": "game-name-unicode-normalization",
      "name": "Game name Unicode normalization",
      "category": "game-ui",
      "urls": {
        "en": "/en/tools/game-name-unicode-normalization/",
        "ja": "/ja/tools/game-name-unicode-normalization/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "UI designers and technical narrative teams",
      "scenario": "Preserve original display and normalized comparison forms",
      "task": "Preserve original display and normalized comparison forms",
      "searchIntent": {
        "primary": "Complete the task: Preserve original display and normalized comparison forms",
        "queryHypothesis": "game name unicode normalization",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to preserve original display and normalized comparison forms?",
        "When should game name unicode normalization be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "identity data: separate keys and display",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "actual UI dimensions: measure usable space",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locale and font: test the shipped rendering",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "escape names at output boundaries",
        "do not substitute character count for rendered width"
      ],
      "requiredData": [
        {
          "description": "approved localized cast",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual fonts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "UI scene and save fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Preserve original display and normalized comparison forms",
        "escape names at output boundaries",
        "do not substitute character count for rendered width",
        "Proposed category workflow: UI fixtures → rendering proof → fallback choice → production regression",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "component specific name proofs",
        "overflow and fallback issues",
        "safe production mappings"
      ],
      "capabilities": [
        "compare worst case approved names across named components",
        "verify a rename without changing resource keys"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Preserve original display and normalized comparison forms. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-name-data-duplicate-normalization",
          "title": 0.2,
          "task": 0.5714285714285714,
          "score": 0.44142857142857145,
          "sharedProfile": false,
          "difference": "Task A: Preserve original display and normalized comparison forms. Task B: Compare normalized forms while retaining original display. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-name-in-records",
          "title": 0,
          "task": 0.2857142857142857,
          "score": 0.18571428571428572,
          "sharedProfile": false,
          "difference": "Task A: Preserve original display and normalized comparison forms. Task B: Keep official record forms separate from narrative display. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-game-npc-name-registry",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Preserve original display and normalized comparison forms. Task B: Assign stable identity keys and separate display names. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Preserve original display and normalized comparison forms",
        "outline": [
          "Explain the specific decision: Preserve original display and normalized comparison forms",
          "Define the applicable contract and limits for Game name Unicode normalization",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Preserve original display and normalized comparison forms; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Preserve original display and normalized comparison forms",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:475",
      "profileSource": "data/profiles.json#game-ui",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-player-chosen-name-review",
        "reason": "The candidate’s stated primary task is exact comparison of normalized forms while preserving raw displays. That behavior is exercised by the explicit normalization/key-stage pipeline, not a distinct tool. Inherited rendering, font and general data-ingestion category promises are not claimed as implemented.",
        "reopenIf": "Demonstrate a different main creator task and two substantial behavior axes, such as an independently justified corpus intake/provenance reconciliation workflow. A normalization-form switch, renamed dataset or extra export alone does not reopen the page.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-name-data-duplicate-normalization",
      "slug": "name-data-duplicate-normalization",
      "name": "Name data duplicate normalization",
      "category": "data-methods",
      "urls": {
        "en": "/en/tools/name-data-duplicate-normalization/",
        "ja": "/ja/tools/name-data-duplicate-normalization/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "creators building reusable naming resources",
      "scenario": "Compare normalized forms while retaining original display",
      "task": "Compare normalized forms while retaining original display",
      "searchIntent": {
        "primary": "Complete the task: Compare normalized forms while retaining original display",
        "queryHypothesis": "name data duplicate normalization",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare normalized forms while retaining original display?",
        "When should name data duplicate normalization be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "dataset manifest: identify provenance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "claim type: apply evidence rules",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "declared use: check reviewed license scope",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence"
      ],
      "requiredData": [
        {
          "description": "user supplied corpora",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "source and license ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "per entry evidence and reviewer notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare normalized forms while retaining original display",
        "unknown license means no redistribution",
        "normalization must not overwrite display or imply identity equivalence",
        "Proposed category workflow: manifest → evidence and license review → constrained intake → audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "intake and evidence report",
        "unresolved claim queue",
        "generation eligible subset with reasons"
      ],
      "capabilities": [
        "trace one output back to its data and rule versions",
        "compare corpora while preserving original forms"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare normalized forms while retaining original display. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-game-name-unicode-normalization",
          "title": 0.2,
          "task": 0.5714285714285714,
          "score": 0.44142857142857145,
          "sharedProfile": false,
          "difference": "Task A: Compare normalized forms while retaining original display. Task B: Preserve original display and normalized comparison forms. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-character-name-in-records",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": false,
          "difference": "Task A: Compare normalized forms while retaining original display. Task B: Keep official record forms separate from narrative display. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-npc-migration-between-towns",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Compare normalized forms while retaining original display. Task B: Preserve individual names while updating local forms of address. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare normalized forms while retaining original display",
        "outline": [
          "Explain the specific decision: Compare normalized forms while retaining original display",
          "Define the applicable contract and limits for Name data duplicate normalization",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare normalized forms while retaining original display; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare normalized forms while retaining original display",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:979",
      "profileSource": "data/profiles.json#data-methods",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-player-chosen-name-review",
        "reason": "The candidate’s stated primary task is exact comparison of normalized forms while preserving raw displays. That behavior is exercised by the explicit normalization/key-stage pipeline, not a distinct tool. Inherited rendering, font and general data-ingestion category promises are not claimed as implemented.",
        "reopenIf": "Demonstrate a different main creator task and two substantial behavior axes, such as an independently justified corpus intake/provenance reconciliation workflow. A normalization-form switch, renamed dataset or extra export alone does not reopen the page.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-audio-nickname-confusion-test",
      "slug": "audio-nickname-confusion-test",
      "name": "Audio nickname confusion test",
      "category": "audio-drama",
      "urls": {
        "en": "/en/tools/audio-nickname-confusion-test/",
        "ja": "/ja/tools/audio-nickname-confusion-test/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "motion comic writers and voice teams",
      "scenario": "Compare short forms in a supplied scene recording",
      "task": "Compare short forms in a supplied scene recording",
      "searchIntent": {
        "primary": "Complete the task: Compare short forms in a supplied scene recording",
        "queryHypothesis": "audio nickname confusion test",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to compare short forms in a supplied scene recording?",
        "When should audio nickname confusion test be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "approved pronunciation: avoid synthesized authority",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "recorded scene or timing: use real performance",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "listener knowledge: gate speaker identity",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context"
      ],
      "requiredData": [
        {
          "description": "creator supplied recordings and permissions",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "pronunciation bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cue and subtitle timeline",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Compare short forms in a supplied scene recording",
        "label timing estimates separately from measured recordings",
        "test spoken short forms in actual dialogue context",
        "Proposed category workflow: reading approval → rehearsal → listener check → recording handoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "pronunciation and cue sheet",
        "potential audio collisions",
        "retake or subtitle change notes"
      ],
      "capabilities": [
        "compare timed names with a selected scene budget",
        "separate performer cues from listener visible identity"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Compare short forms in a supplied scene recording. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-nickname-introduction",
          "title": 0.16666666666666666,
          "task": 0.2,
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Task A: Compare short forms in a supplied scene recording. Task B: Find short forms with no reader facing connection to a full name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-bilingual-voice-pronunciation-parity",
          "title": 0,
          "task": 0.25,
          "score": 0.1625,
          "sharedProfile": true,
          "difference": "Task A: Compare short forms in a supplied scene recording. Task B: Align creator approved forms across recording languages. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Compare short forms in a supplied scene recording",
        "outline": [
          "Explain the specific decision: Compare short forms in a supplied scene recording",
          "Define the applicable contract and limits for Audio nickname confusion test",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Compare short forms in a supplied scene recording; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "wcag22",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Compare short forms in a supplied scene recording",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:395",
      "profileSource": "data/profiles.json#audio-drama",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-audio-cast-recognition-test",
        "reason": "Testing short-form identity choices in a supplied scene recording is the implemented local listening-session task. Using nickname labels instead of full names does not create another main task. Inherited pronunciation/timing/retake category sketches are not claimed delivered by this merge.",
        "reopenIf": "Prove a different primary production task and at least two substantive behavior axes beyond nickname labels, another clip, condition or export. Performer preparation remains connected to motion-comic-spoken-cast-separation, not an automatically measured listening result.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-royal-regnal-name",
      "slug": "royal-regnal-name",
      "name": "Royal regnal name",
      "category": "titles",
      "urls": {
        "en": "/en/tools/royal-regnal-name/",
        "ja": "/ja/tools/royal-regnal-name/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "fantasy, historical fiction and game writers",
      "scenario": "Separate birth name, reign name and succession number",
      "task": "Separate birth name, reign name and succession number",
      "searchIntent": {
        "primary": "Complete the task: Separate birth name, reign name and succession number",
        "queryHypothesis": "royal regnal name",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate birth name, reign name and succession number?",
        "When should royal regnal name be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "office or deed ledger: justify titles",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "succession timeline: resolve holders",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "observer allegiance: distinguish recognition",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint"
      ],
      "requiredData": [
        {
          "description": "fictional institution charter",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "succession events",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "authored deeds and observer beliefs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate birth name, reign name and succession number",
        "an office and its holder are different entities",
        "reputation labels carry an attributed viewpoint",
        "Proposed category workflow: title rules → eligibility → holder timeline → address review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "personal and title forms",
        "holder timeline",
        "recognition and spoiler notes"
      ],
      "capabilities": [
        "transfer an office while retaining individual IDs",
        "compare claimed and recognized styles by observer"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate birth name, reign name and succession number. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "shared-task-risk",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-invented-royal-personal-grammar",
          "title": 0.25,
          "task": 0.16666666666666666,
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Task A: Separate birth name, reign name and succession number. Task B: Separate royal personal names from succession numbering. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-regnal-number-clue",
          "title": 0.25,
          "task": 0.125,
          "score": 0.16875,
          "sharedProfile": false,
          "difference": "Task A: Separate birth name, reign name and succession number. Task B: Base a deduction on a disclosed fictional succession system. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-secret-royal-identity",
          "title": 0.25,
          "task": 0.1111111111111111,
          "score": 0.1597222222222222,
          "sharedProfile": false,
          "difference": "Task A: Separate birth name, reign name and succession number. Task B: Manage birth title, assumed name and recognition triggers. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate birth name, reign name and succession number",
        "outline": [
          "Explain the specific decision: Separate birth name, reign name and succession number",
          "Define the applicable contract and limits for Royal regnal name",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate birth name, reign name and succession number; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate birth name, reign name and succession number",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "A different fictional situation may not change the main user task; compare with the nearest parent tool."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:576",
      "profileSource": "data/profiles.json#titles",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-regnal-numbering-consistency",
        "reason": "The stated task separates personal identity, reign display and succession numbering. The working numbering ledger preserves those fields, counts by explicit series/key and audits reaccession. A royal preset or another display format does not establish a different main task. Inherited phonotactic, title, audience and culture category sketches are not declared implemented.",
        "reopenIf": "Prove a different primary naming task and two substantive behavior axes beyond royal labels, personal/reign fields or numeral formatting. A genuine invented-language derivation belongs with the grammar tool unless it establishes another independently useful workflow.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-invented-royal-personal-grammar",
      "slug": "invented-royal-personal-grammar",
      "name": "Invented royal personal grammar",
      "category": "world-grammar",
      "urls": {
        "en": "/en/tools/invented-royal-personal-grammar/",
        "ja": "/ja/tools/invented-royal-personal-grammar/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "worldbuilders and speculative fiction writers",
      "scenario": "Separate royal personal names from succession numbering",
      "task": "Separate royal personal names from succession numbering",
      "searchIntent": {
        "primary": "Complete the task: Separate royal personal names from succession numbering",
        "queryHypothesis": "invented royal personal grammar",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to separate royal personal names from succession numbering?",
        "When should invented royal personal grammar be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "phonotactic inventory: constrain sounds",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "morphology and inheritance: derive components",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "exceptions: make deliberate departures visible",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts"
      ],
      "requiredData": [
        {
          "description": "original fictional morphemes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "transformation tables",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "positive and negative corpus examples",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Separate royal personal names from succession numbering",
        "apply authored transformations in a declared order",
        "never describe invented conventions as real cultural facts",
        "Proposed category workflow: grammar → corpus examples → constrained generation → consistency audit",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "derived names with derivation traces",
        "rule violations",
        "culture specific style guide"
      ],
      "capabilities": [
        "trace every component to an authored rule",
        "compare two fictional grammars using controlled corpus tests"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Separate royal personal names from succession numbering. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-royal-regnal-name",
          "title": 0.25,
          "task": 0.16666666666666666,
          "score": 0.19583333333333333,
          "sharedProfile": false,
          "difference": "Task A: Separate royal personal names from succession numbering. Task B: Separate birth name, reign name and succession number. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Separate royal personal names from succession numbering",
        "outline": [
          "Explain the specific decision: Separate royal personal names from succession numbering",
          "Define the applicable contract and limits for Invented royal personal grammar",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Separate royal personal names from succession numbering; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Separate royal personal names from succession numbering",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:552",
      "profileSource": "data/profiles.json#world-grammar",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-regnal-numbering-consistency",
        "reason": "The stated task separates personal identity, reign display and succession numbering. The working numbering ledger preserves those fields, counts by explicit series/key and audits reaccession. A royal preset or another display format does not establish a different main task. Inherited phonotactic, title, audience and culture category sketches are not declared implemented.",
        "reopenIf": "Prove a different primary naming task and two substantive behavior axes beyond royal labels, personal/reign fields or numeral formatting. A genuine invented-language derivation belongs with the grammar tool unless it establishes another independently useful workflow.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-localized-ensemble-introduction-order",
      "slug": "localized-ensemble-introduction-order",
      "name": "Localized ensemble introduction order",
      "category": "localization",
      "urls": {
        "en": "/en/tools/localized-ensemble-introduction-order/",
        "ja": "/ja/tools/localized-ensemble-introduction-order/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "translators and bilingual creators",
      "scenario": "Adjust exposition while preserving identity knowledge",
      "task": "Adjust exposition while preserving identity knowledge",
      "searchIntent": {
        "primary": "Complete the task: Adjust exposition while preserving identity knowledge",
        "queryHypothesis": "localized ensemble introduction order",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to adjust exposition while preserving identity knowledge?",
        "When should localized ensemble introduction order be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "source and target locale: select review context",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "stable character IDs: preserve identity",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "plot dependencies: protect clue function",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions"
      ],
      "requiredData": [
        {
          "description": "approved bilingual identity map",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "translator decision log",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "locale specific layout fixtures",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Adjust exposition while preserving identity knowledge",
        "do not infer equivalence solely from transliteration",
        "record retained and lost narrative functions",
        "Proposed category workflow: identity mapping → alternatives → clue and layout regression → translator signoff",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "source target mapping",
        "tradeoff notes",
        "production assets requiring revision"
      ],
      "capabilities": [
        "detect multiple source identities collapsed into one target form",
        "compare reveal knowledge before and after localization"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Adjust exposition while preserving identity knowledge. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-cold-open-unknown-speaker-names",
          "title": 0,
          "task": 0.3,
          "score": 0.195,
          "sharedProfile": false,
          "difference": "Task A: Adjust exposition while preserving identity knowledge. Task B: Hide reader identity while preserving production clarity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-identical-twin-scene-labels",
          "title": 0,
          "task": 0.2222222222222222,
          "score": 0.14444444444444443,
          "sharedProfile": false,
          "difference": "Task A: Adjust exposition while preserving identity knowledge. Task B: Track knowledge of identity across a mistaken identity scene. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-order-initiation-names",
          "title": 0.2,
          "task": 0.1,
          "score": 0.135,
          "sharedProfile": false,
          "difference": "Task A: Adjust exposition while preserving identity knowledge. Task B: Apply fictional ceremonial name rules with an identity timeline. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Adjust exposition while preserving identity knowledge",
        "outline": [
          "Explain the specific decision: Adjust exposition while preserving identity knowledge",
          "Define the applicable contract and limits for Localized ensemble introduction order",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Adjust exposition while preserving identity knowledge; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "renpy",
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Adjust exposition while preserving identity knowledge",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:326",
      "profileSource": "data/profiles.json#localization",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-large-cast-introduction-pacing",
        "reason": "Changing an edition or locale does not alone establish a separate scheduling task. The implemented scheduler audits one authored edition with explicit starting knowledge, scene windows, protected placements and prerequisites. Cross-edition identity mapping, clue regression and translator approval from the inherited category sketch remain unimplemented; this merge does not certify them.",
        "reopenIf": "Demonstrate a coordinated source/target-edition decision with a different primary task and at least two substantive axes beyond another locale, schedule or supplied baseline. Keep translation equivalence and spoiler knowledge review separate from schedule feasibility.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-manuscript-nickname-introduction",
      "slug": "manuscript-nickname-introduction",
      "name": "Manuscript nickname introduction",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-nickname-introduction/",
        "ja": "/ja/tools/manuscript-nickname-introduction/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Find short forms with no reader facing connection to a full name",
      "task": "Find short forms with no reader facing connection to a full name",
      "searchIntent": {
        "primary": "Complete the task: Find short forms with no reader facing connection to a full name",
        "queryHypothesis": "manuscript nickname introduction",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to find short forms with no reader facing connection to a full name?",
        "When should manuscript nickname introduction be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Find short forms with no reader facing connection to a full name",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Find short forms with no reader facing connection to a full name. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-character-introduction-naming",
          "title": 0.3333333333333333,
          "task": 0.23076923076923078,
          "score": 0.26666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Find short forms with no reader facing connection to a full name. Task B: Stage first reference, full introduction and later short forms. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-audio-nickname-confusion-test",
          "title": 0.16666666666666666,
          "task": 0.2,
          "score": 0.18833333333333332,
          "sharedProfile": false,
          "difference": "Task A: Find short forms with no reader facing connection to a full name. Task B: Compare short forms in a supplied scene recording. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-name-introduction-audit",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Find short forms with no reader facing connection to a full name. Task B: Detect references that precede the intended introduction. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Find short forms with no reader facing connection to a full name",
        "outline": [
          "Explain the specific decision: Find short forms with no reader facing connection to a full name",
          "Define the applicable contract and limits for Manuscript nickname introduction",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Find short forms with no reader facing connection to a full name; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Find short forms with no reader facing connection to a full name",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:877",
      "profileSource": "data/profiles.json#manuscript-audit",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-true-name-alias-bridge",
        "reason": "The core task is checking whether a confirmed name form is introduced or connected before use for a specified observer. The existing identity bridge implements that ordered first-use ledger. Nickname wording or manuscript context alone adds no different main task. Whole-manuscript parsing, automatic entity discovery and bulk replacement from category sketches are not implemented or implied.",
        "reopenIf": "Prove a different primary editorial task with two substantive behavior axes beyond entering another form, observer, chapter or batch size. A safe whole-manuscript import may be an integration; demonstrate independent value before another page.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-manuscript-name-introduction-audit",
      "slug": "manuscript-name-introduction-audit",
      "name": "Manuscript name introduction audit",
      "category": "manuscript-audit",
      "urls": {
        "en": "/en/tools/manuscript-name-introduction-audit/",
        "ja": "/ja/tools/manuscript-name-introduction-audit/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "novel editors and serial creators",
      "scenario": "Detect references that precede the intended introduction",
      "task": "Detect references that precede the intended introduction",
      "searchIntent": {
        "primary": "Complete the task: Detect references that precede the intended introduction",
        "queryHypothesis": "manuscript name introduction audit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to detect references that precede the intended introduction?",
        "When should manuscript name introduction audit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "author confirmed entity list: prevent automatic identity inference",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "passage references: localize issues",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "approved timeline and forms: define expected behavior",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation"
      ],
      "requiredData": [
        {
          "description": "user supplied manuscript excerpts",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "cast bible",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "scene and edit ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Detect references that precede the intended introduction",
        "suggest possible matches without automatically merging identities",
        "preview all replacements before mutation",
        "Proposed category workflow: confirmed entities → occurrence review → scoped preview → editor decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "occurrence linked issues",
        "proposed revisions and scope",
        "editor decisions with rationale"
      ],
      "capabilities": [
        "trace identity changes into exact passage references",
        "compare deliberate document errors with narrative spelling"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Detect references that precede the intended introduction. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-family-generational-confusion-audit",
          "title": 0.16666666666666666,
          "task": 0.2222222222222222,
          "score": 0.20277777777777775,
          "sharedProfile": false,
          "difference": "Task A: Detect references that precede the intended introduction. Task B: Detect repeated name references in dated scenes. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-name-variant-audit",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Detect references that precede the intended introduction. Task B: Find spelling variants for human identity confirmation. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-nickname-introduction",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Detect references that precede the intended introduction. Task B: Find short forms with no reader facing connection to a full name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Detect references that precede the intended introduction",
        "outline": [
          "Explain the specific decision: Detect references that precede the intended introduction",
          "Define the applicable contract and limits for Manuscript name introduction audit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Detect references that precede the intended introduction; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Detect references that precede the intended introduction",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:875",
      "profileSource": "data/profiles.json#manuscript-audit",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-true-name-alias-bridge",
        "reason": "The core task is checking whether a confirmed name form is introduced or connected before use for a specified observer. The existing identity bridge implements that ordered first-use ledger. Nickname wording or manuscript context alone adds no different main task. Whole-manuscript parsing, automatic entity discovery and bulk replacement from category sketches are not implemented or implied.",
        "reopenIf": "Prove a different primary editorial task with two substantive behavior axes beyond entering another form, observer, chapter or batch size. A safe whole-manuscript import may be an integration; demonstrate independent value before another page.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-name-vertical-setting",
      "slug": "japanese-name-vertical-setting",
      "name": "Japanese name vertical setting",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-name-vertical-setting/",
        "ja": "/ja/tools/japanese-name-vertical-setting/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Test name and reading in vertical text layouts",
      "task": "Test name and reading in vertical text layouts",
      "searchIntent": {
        "primary": "Complete the task: Test name and reading in vertical text layouts",
        "queryHypothesis": "japanese name vertical setting",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to test name and reading in vertical text layouts?",
        "When should japanese name vertical setting be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Test name and reading in vertical text layouts",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Test name and reading in vertical text layouts. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-japanese-difficult-name-introduction",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": true,
          "difference": "Task A: Test name and reading in vertical text layouts. Task B: Compare staged reading support against renaming. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Test name and reading in vertical text layouts",
        "outline": [
          "Explain the specific decision: Test name and reading in vertical text layouts",
          "Define the applicable contract and limits for Japanese name vertical setting",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Test name and reading in vertical text layouts; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Test name and reading in vertical text layouts",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:274",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-japanese-name-ruby-layout",
        "reason": "Vertical setting is an actual writing-mode option within the same annotation-contract and bounded proof task. Literal base/reading associations, exact rectangles and physical dimensions do not become a second main task when the writing axis changes.",
        "reopenIf": "Demonstrate a different primary task and at least two substantive behavioral axes beyond bearer type, writing mode, frame size or font choice. Adjacent-art obstacle geometry and complete publisher-specific composition remain outside this tool.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-japanese-pen-name-ruby-credit",
      "slug": "japanese-pen-name-ruby-credit",
      "name": "Japanese pen name ruby credit",
      "category": "japanese-writing",
      "urls": {
        "en": "/en/tools/japanese-pen-name-ruby-credit/",
        "ja": "/ja/tools/japanese-pen-name-ruby-credit/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "Japanese language fiction and manga creators",
      "scenario": "Pair byline and reading in publication sized credit previews",
      "task": "Pair byline and reading in publication sized credit previews",
      "searchIntent": {
        "primary": "Complete the task: Pair byline and reading in publication sized credit previews",
        "queryHypothesis": "japanese pen name ruby credit",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to pair byline and reading in publication sized credit previews?",
        "When should japanese pen name ruby credit be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "written form: preserve chosen script",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "confirmed kana: support reading analysis",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "claim sources: separate attestation and invention",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly"
      ],
      "requiredData": [
        {
          "description": "author approved written and kana pairs",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "licensed reviewed reading evidence",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "actual font glyph coverage",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Pair byline and reading in publication sized credit previews",
        "do not derive name readings solely from kanji meanings",
        "label invented readings and creative associations explicitly",
        "Proposed category workflow: forms → reading evidence → layout test → Japanese editorial review",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "written form and kana in separate fields",
        "reading ambiguity notes",
        "evidence and fictional interpretation labels"
      ],
      "capabilities": [
        "detect collisions between different spellings with equal confirmed readings",
        "retain original glyphs alongside reviewed fallbacks"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Pair byline and reading in publication sized credit previews. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-collaborative-pen-name",
          "title": 0.2,
          "task": 0.15384615384615385,
          "score": 0.16999999999999998,
          "sharedProfile": false,
          "difference": "Task A: Pair byline and reading in publication sized credit previews. Task B: Allocate shared credit and member identity under a joint byline. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-name-ruby-layout",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": true,
          "difference": "Task A: Pair byline and reading in publication sized credit previews. Task B: Preview supplied readings over name text without asserting cultural validity. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-japanese-pen-name-reading",
          "title": 0.4,
          "task": 0,
          "score": 0.13999999999999999,
          "sharedProfile": false,
          "difference": "Task A: Pair byline and reading in publication sized credit previews. Task B: Store approved kana and romanized credits alongside the name. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Pair byline and reading in publication sized credit previews",
        "outline": [
          "Explain the specific decision: Pair byline and reading in publication sized credit previews",
          "Define the applicable contract and limits for Japanese pen name ruby credit",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Pair byline and reading in publication sized credit previews; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "moj-reading",
        "edrdg",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Pair byline and reading in publication sized credit previews",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "Cultural and language-specific claims require evidence and qualified human review."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:273",
      "profileSource": "data/profiles.json#japanese-writing",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-japanese-name-ruby-layout",
        "reason": "A pen-name ruby credit is the same task of attaching a supplied whole/segmented annotation to a literal byline and checking a bounded production surface. Changing the bearer or label does not create a distinct tool; author identity design remains in the separate pen-name atelier.",
        "reopenIf": "Demonstrate a different primary task and at least two substantive behavioral axes beyond bearer type, writing mode, frame size or font choice. Adjacent-art obstacle geometry and complete publisher-specific composition remain outside this tool.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-naming-project-restore-conflict",
      "slug": "naming-project-restore-conflict",
      "name": "Naming project restore conflict",
      "category": "project-workflows",
      "urls": {
        "en": "/en/tools/naming-project-restore-conflict/",
        "ja": "/ja/tools/naming-project-restore-conflict/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "authors and production collaborators",
      "scenario": "Reconcile imported names with current locked identities explicitly",
      "task": "Reconcile imported names with current locked identities explicitly",
      "searchIntent": {
        "primary": "Complete the task: Reconcile imported names with current locked identities explicitly",
        "queryHypothesis": "naming project restore conflict",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to reconcile imported names with current locked identities explicitly?",
        "When should naming project restore conflict be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "project state: restore accepted decisions",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "hard constraints and preferences: define priorities",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "locked identities: protect committed work",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states"
      ],
      "requiredData": [
        {
          "description": "local project manifest",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "versioned rule and corpus references",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "editorial decision history",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Reconcile imported names with current locked identities explicitly",
        "do not silently relax hard constraints",
        "generated candidates and accepted identities have different states",
        "Proposed category workflow: brief → constraints → reversible comparison → accepted decision",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "task scoped decision package",
        "constraint conflict explanation",
        "reversible revision preview"
      ],
      "capabilities": [
        "find conflicting rules and suggest specific relaxations",
        "restore an earlier decision without overwriting unreviewed changes"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Reconcile imported names with current locked identities explicitly. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "scope-and-feature-risk",
        "alternative": "Integrate into a parent tool, project workspace or editorial guide; keep this record and reason in the rejected archive."
      },
      "nearestTools": [
        {
          "id": "nw-naming-project-conflict-explanation",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Reconcile imported names with current locked identities explicitly. Task B: Explain which rules make a request impossible and suggest bounded changes. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-naming-project-version-restore",
          "title": 0.5,
          "task": 0,
          "score": 0.175,
          "sharedProfile": true,
          "difference": "Task A: Reconcile imported names with current locked identities explicitly. Task B: Restore parameters and identity records from an explicit version. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-campaign-lore-naming-conflict",
          "title": 0.2,
          "task": 0.1111111111111111,
          "score": 0.1422222222222222,
          "sharedProfile": false,
          "difference": "Task A: Reconcile imported names with current locked identities explicitly. Task B: Reconcile two contributor supplied naming conventions. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Reconcile imported names with current locked identities explicitly",
        "outline": [
          "Explain the specific decision: Reconcile imported names with current locked identities explicitly",
          "Define the applicable contract and limits for Naming project restore conflict",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Reconcile imported names with current locked identities explicitly; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Reconcile imported names with current locked identities explicitly",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff.",
        "May be a shared feature, educational exercise or internal workflow outside the public naming-tool scope; merge or redesign before development."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:1020",
      "profileSource": "data/profiles.json#project-workflows",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-series-cast-change-diff",
        "reason": "Reconciling imported names with current locked identities is the same primary naming reconciliation task when current and base match. It needs the same record fields, locks, exact decision context and complete-export gate, not another route or an import-themed duplicate.",
        "reopenIf": "Demonstrate a different primary user decision and at least two substantive implemented differences beyond source-file origin or choosing current as the base. Arbitrary legacy-project migration and verified version ancestry are not provided by this tool.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    },
    {
      "id": "nw-campaign-archive-identity-merge",
      "slug": "campaign-archive-identity-merge",
      "name": "Campaign archive identity merge",
      "category": "tabletop",
      "urls": {
        "en": "/en/tools/campaign-archive-identity-merge/",
        "ja": "/ja/tools/campaign-archive-identity-merge/"
      },
      "urlState": "never-published-retired-path",
      "canonicalOrigin": null,
      "audience": "game masters and collaborative storytellers",
      "scenario": "Flag suspected duplicate records for human confirmation",
      "task": "Flag suspected duplicate records for human confirmation",
      "searchIntent": {
        "primary": "Complete the task: Flag suspected duplicate records for human confirmation",
        "queryHypothesis": "campaign archive identity merge",
        "validation": "unvalidated",
        "monthlyVolume": null,
        "evidenceIds": []
      },
      "relatedQuestions": [
        "What information is needed to flag suspected duplicate records for human confirmation?",
        "When should campaign archive identity merge be part of a broader naming workflow?"
      ],
      "inputs": [
        {
          "key": "draft-1",
          "use": "campaign registry: prevent accidental reuse",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-2",
          "use": "player knowledge: create safe handouts",
          "status": "inherited-category-draft"
        },
        {
          "key": "draft-3",
          "use": "session context: prioritize immediate usability",
          "status": "inherited-category-draft"
        }
      ],
      "rules": [
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity"
      ],
      "requiredData": [
        {
          "description": "author campaign notes",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "group approved readings",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        },
        {
          "description": "session and relationship ledger",
          "intakeStatus": "not-imported",
          "licenseReview": "required-before-redistribution"
        }
      ],
      "generationFlow": [
        "Clarify task-specific contract for: Flag suspected duplicate records for human confirmation",
        "save improvised names before rerolling",
        "separate GM truth from player accessible identity",
        "Proposed category workflow: encounter brief → name card → table use → continuity capture",
        "Do not implement or publish this sketch as a generic generator"
      ],
      "outputs": [
        "speakable name cards",
        "GM private identity notes",
        "player safe reference sheet"
      ],
      "capabilities": [
        "promote an improvised result into the campaign registry",
        "export a knowledge bounded handout"
      ],
      "contractScope": "category-proposal-not-demonstrated",
      "independence": {
        "question": "Why open this page rather than select an option in an existing tool?",
        "answer": "Hypothesis: Flag suspected duplicate records for human confirmation. This scenario alone does not prove a separate main task.",
        "proposedDifferenceAxes": [],
        "verifiedDifferenceAxes": [],
        "reviewStatus": "not-approved",
        "risk": "independence-unverified",
        "alternative": "Merge with the closest parent unless a prototype demonstrates a distinct main task and at least two meaningful differences."
      },
      "nearestTools": [
        {
          "id": "nw-manuscript-character-merge-review",
          "title": 0.16666666666666666,
          "task": 0.16666666666666666,
          "score": 0.16666666666666666,
          "sharedProfile": false,
          "difference": "Task A: Flag suspected duplicate records for human confirmation. Task B: Identify possible duplicate records without automatically merging them. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-manuscript-name-variant-audit",
          "title": 0,
          "task": 0.2,
          "score": 0.13,
          "sharedProfile": false,
          "difference": "Task A: Flag suspected duplicate records for human confirmation. Task B: Find spelling variants for human identity confirmation. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        },
        {
          "id": "nw-name-erased-archive",
          "title": 0.2,
          "task": 0.09090909090909091,
          "score": 0.1290909090909091,
          "sharedProfile": false,
          "difference": "Task A: Flag suspected duplicate records for human confirmation. Task B: Determine which records survive a fictional erasure event. This is a textual comparison; meaningful behavioral differences require human review.",
          "resolution": "open: merge, redesign or justify with prototype"
        }
      ],
      "contentPlan": {
        "status": "brief-only",
        "theme": "Flag suspected duplicate records for human confirmation",
        "outline": [
          "Explain the specific decision: Flag suspected duplicate records for human confirmation",
          "Define the applicable contract and limits for Campaign archive identity merge",
          "Build a complete original worked example for this task",
          "Show failed input, correction and downstream story consequences"
        ],
        "story": null,
        "storyAnalysis": null,
        "evidence": "Planned evidence: task-specific original fixtures for Flag suspected duplicate records for human confirmation; category references do not substantiate individual cultural claims.",
        "evidenceStatus": "planned-not-written-or-reviewed",
        "budgets": {
          "en": {
            "words": [
              1800,
              2600
            ],
            "status": "pilot-budget-not-a-publication-rule"
          },
          "ja": {
            "characters": [
              4500,
              7500
            ],
            "status": "needs-Japanese-editor-calibration"
          }
        },
        "faqs": [],
        "bodyPath": null,
        "storyPath": null
      },
      "dataSources": [
        "w3c-names",
        "scrivener"
      ],
      "difficulty": "unestimated-until-task-design",
      "acceptance": [
        "Provide input/output fixtures that demonstrate: Flag suspected duplicate records for human confirmation",
        "Vary a meaningful task input while holding seed and corpus fixed; explain the changed result.",
        "Demonstrate two task-specific capabilities beyond the category defaults.",
        "Compare with nearest candidates and disposition same-task overlaps before implementation."
      ],
      "status": "merged",
      "specMaturity": "scenario-sketch",
      "stageTwoPilot": false,
      "approvals": {
        "independence": false,
        "demand": false,
        "function": false,
        "content": false,
        "sources": false,
        "culturalReview": false,
        "accessibility": false,
        "seo": false,
        "humanRelease": false
      },
      "localeStatus": {
        "en": "not-authored",
        "ja": "not-authored"
      },
      "owner": {
        "author": null,
        "editor": null,
        "culturalReviewer": null
      },
      "unresolvedIssues": [
        "No independent demand or search-volume evidence; research hypothesis only.",
        "Inputs, rules and capabilities inherit a category draft; task-specific algorithm, data and fixtures still need design.",
        "No completed original long-form article, story edit, or named human editorial signoff."
      ],
      "created": "2026-10-31",
      "updated": "2026-10-31",
      "briefSource": "data/briefs.txt:524",
      "profileSource": "data/profiles.json#tabletop",
      "disposition": {
        "action": "merged-after-implementation-evidence",
        "parentId": "nw-manuscript-character-merge-review",
        "reason": "Campaign session labels and game-master notes do not change the main task of reviewing whether distinct source records denote the same fictional person. Lexical screening, authored relationships, contradiction witnesses and representative choices are the same behavior.",
        "reopenIf": "Show a different primary task and at least two substantive implemented axes beyond changing scene labels to session labels. Verified session history and automatic manuscript/database consolidation are not implemented.",
        "decidedBy": "AI-assisted product review under user-authorized autonomy",
        "date": "2026-11-01",
        "releaseApproval": false,
        "redirect": "none: source URL never published"
      }
    }
  ],
  "accounting": {
    "original": 967,
    "active": 885,
    "merged": 82,
    "unfilledTargetSlots": 82,
    "acceptedIndependentTools": 0,
    "targetIndependentTools": 200,
    "acceptedToolShortfall": 200,
    "addedReplacements": 0,
    "remainingTargetImplementations": 156
  }
}