{ "baseline": 967, "records": [ { "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" } } ] }