{"id":47510,"plugin_id":"plugins_6abdca92a1908191b989544ed495ca16","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:33:35.448Z","digest":"ca550eee2bcfde184011b1a02662e6f6873c382cdfdea5ad53de80e3ba6efcd9","against":null,"payload":{"description":"AI developmental editing framework for fiction, narrative nonfiction, and argument-shaped nonfiction; owns the Nonfiction Argument Engine. Use when the user asks to \"run a development edit,\" \"analyze my manuscript,\" \"diagnose structural issues,\" \"start a new project,\" \"generate a contract,\" \"run the passes,\" \"do a revision round,\" or any request involving manuscript analysis, structural diagnosis, or editorial feedback. Also triggers on \"APODICTIC,\" \"APDE,\" or \"development editor.\"\n","included_files":[{"relative_path":"references/adversarial-stress-test.md","size_in_bytes":7157},{"relative_path":"references/annotated-manuscript.md","size_in_bytes":7813},{"relative_path":"references/argument-audits-propagation.md","size_in_bytes":6129},{"relative_path":"references/argument-audits-routing.md","size_in_bytes":6431},{"relative_path":"references/audit-routing-table.md","size_in_bytes":5551},{"relative_path":"references/author-voice-fingerprint.md","size_in_bytes":5059},{"relative_path":"references/character-architecture.md","size_in_bytes":4548},{"relative_path":"references/continuity-bible.md","size_in_bytes":8590},{"relative_path":"references/contract-template.md","size_in_bytes":2782},{"relative_path":"references/craft/approval-workflow.md","size_in_bytes":6732},{"relative_path":"references/diagnostic-state-meta-template.json","size_in_bytes":5839},{"relative_path":"references/diagnostic-state-template.md","size_in_bytes":3735},{"relative_path":"references/diagnostic-vocabulary.md","size_in_bytes":4316},{"relative_path":"references/editor-scaffolding.md","size_in_bytes":9886},{"relative_path":"references/example-annotated-manuscript/Example_Annotated_Manuscript_2026-01-01.md","size_in_bytes":1471},{"relative_path":"references/example-annotated-manuscript/Example_Annotation_Manifest_2026-01-01.md","size_in_bytes":2428},{"relative_path":"references/example-annotated-manuscript/Example_Crosslinked_Letter_2026-01-01.md","size_in_bytes":1590},{"relative_path":"references/example-annotated-manuscript/Example_Editorial_Letter_2026-01-01.md","size_in_bytes":1297},{"relative_path":"references/example-annotated-manuscript/Example_Findings_Ledger_2026-01-01.md","size_in_bytes":2937},{"relative_path":"references/example-annotated-manuscript/Example_Manuscript_Snapshot_2026-01-01.md","size_in_bytes":371},{"relative_path":"references/example-annotated-manuscript/Example_Timeline_2026-01-01.md","size_in_bytes":312},{"relative_path":"references/example-annotated-manuscript/html/Example_Annotated_Manuscript_2026-01-01.html","size_in_bytes":3104},{"relative_path":"references/example-annotated-manuscript/obsidian/Example_Annotated_Manuscript_2026-01-01.md","size_in_bytes":2022},{"relative_path":"references/example-annotated-manuscript/obsidian/Example_Crosslinked_Letter_2026-01-01.md","size_in_bytes":1644},{"relative_path":"references/example-argument-aif-export.json","size_in_bytes":4971},{"relative_path":"references/example-argument-aif-state.md","size_in_bytes":1793},{"relative_path":"references/example-argument-state-generative.md","size_in_bytes":2416},{"relative_path":"references/example-argument-state-genre-academic.md","size_in_bytes":5513},{"relative_path":"references/example-argument-state-genre-grant.md","size_in_bytes":5830},{"relative_path":"references/example-argument-state-genre-pitch.md","size_in_bytes":5601},{"relative_path":"references/example-argument-state-predraft.md","size_in_bytes":6554},{"relative_path":"references/example-author-style-explanation.md","size_in_bytes":5564},{"relative_path":"references/example-author-voice-profile.md","size_in_bytes":3513},{"relative_path":"references/example-beta-reader-instrument.md","size_in_bytes":2423},{"relative_path":"references/example-blindspot-ranked/Tide_Editorial_Letter_2026-07-04_opus48.md","size_in_bytes":2356},{"relative_path":"references/example-blindspot-ranked/Tide_Findings_Ledger_2026-07-04_opus48.md","size_in_bytes":1797},{"relative_path":"references/example-coaching-history/Diagnostic_State.md","size_in_bytes":668},{"relative_path":"references/example-coaching-history/Diagnostic_State.meta.json","size_in_bytes":1648},{"relative_path":"references/example-coaching-history/Example_Coaching_History_2026-03-01_opus48.md","size_in_bytes":2479},{"relative_path":"references/example-content-advisory.md","size_in_bytes":3028},{"relative_path":"references/example-continuity-bible.md","size_in_bytes":6792},{"relative_path":"references/example-cost-floor-contract.md","size_in_bytes":2900},{"relative_path":"references/example-cost-floor-preflight.md","size_in_bytes":1384},{"relative_path":"references/example-decision-audit-letter.md","size_in_bytes":2689},{"relative_path":"references/example-editorial-letter-dual-author.md","size_in_bytes":4803},{"relative_path":"references/example-editorial-letter-scaffolded.md","size_in_bytes":6188},{"relative_path":"references/example-editorial-letter.md","size_in_bytes":3060},{"relative_path":"references/example-feedback-triage.md","size_in_bytes":4109},{"relative_path":"references/example-findings-ledger.md","size_in_bytes":1503},{"relative_path":"references/example-intake-interview-ledger.md","size_in_bytes":1616},{"relative_path":"references/example-intake-interview.md","size_in_bytes":3378},{"relative_path":"references/example-legal-risk-register.md","size_in_bytes":4678},{"relative_path":"references/example-pass-artifact-header.md","size_in_bytes":1213},{"relative_path":"references/example-pass-scaffolded.md","size_in_bytes":4258},{"relative_path":"references/example-persona-divergence-ledger.md","size_in_bytes":1060},{"relative_path":"references/example-persona-divergence-map.md","size_in_bytes":2913},{"relative_path":"references/example-promise-contract.md","size_in_bytes":5660},{"relative_path":"references/example-quality-risk-contract.md","size_in_bytes":7550},{"relative_path":"references/example-reader-contract-outline/ExampleNF_Contract_2026-01-01.md","size_in_bytes":1060},{"relative_path":"references/example-reader-contract-outline/ExampleNF_Contract_Map_2026-01-01.md","size_in_bytes":1778},{"relative_path":"references/example-reader-contract-outline/ExampleNF_Findings_Ledger_2026-01-01.md","size_in_bytes":1441},{"relative_path":"references/example-reader-contract-outline/ExampleNF_Pass0_Reverse_Outline_2026-01-01.md","size_in_bytes":1054},{"relative_path":"references/example-reader-contract-outline/ExampleNF_Reader_Contract_Outline_2026-01-01.md","size_in_bytes":2748},{"relative_path":"references/example-reader-contract-outline/Example_Contract_2026-01-01.md","size_in_bytes":1452},{"relative_path":"references/example-reader-contract-outline/Example_Contract_Map_2026-01-01.md","size_in_bytes":1990},{"relative_path":"references/example-reader-contract-outline/Example_Findings_Ledger_2026-01-01.md","size_in_bytes":1517},{"relative_path":"references/example-reader-contract-outline/Example_Pass0_Reverse_Outline_2026-01-01.md","size_in_bytes":2180},{"relative_path":"references/example-reader-contract-outline/Example_Reader_Contract_Outline_2026-01-01.md","size_in_bytes":3018},{"relative_path":"references/example-reanchor-revised.md","size_in_bytes":528},{"relative_path":"references/example-regrounded-ledger.md","size_in_bytes":1323},{"relative_path":"references/example-regrounded-letter.md","size_in_bytes":1157},{"relative_path":"references/example-results-guide/Diagnostic_State.md","size_in_bytes":194},{"relative_path":"references/example-results-guide/Example_Findings_Ledger_run.md","size_in_bytes":362},{"relative_path":"references/example-results-guide/Example_Interiority_Audit_run.md","size_in_bytes":145},{"relative_path":"references/example-results-guide/Example_Pass2_Structural_Mapping_run.md","size_in_bytes":337},{"relative_path":"references/example-results-guide/Example_Pass5_Character_Audit_run.md","size_in_bytes":344},{"relative_path":"references/example-results-guide/Example_Results_Guide_run.md","size_in_bytes":851},{"relative_path":"references/example-retcon-plan.md","size_in_bytes":7314},{"relative_path":"references/example-revision-arc.md","size_in_bytes":6913},{"relative_path":"references/example-roundtrip-disposition.md","size_in_bytes":2953},{"relative_path":"references/example-roundtrip-revision-report.md","size_in_bytes":1163},{"relative_path":"references/example-run-folder-coverage-degraded/Diagnostic_State.meta.json","size_in_bytes":1299},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Audit_Invocation_Log_2026-01-01_opus46.md","size_in_bytes":278},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Contract_2026-01-01_opus46.md","size_in_bytes":191},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Core_DE_Synthesis_2026-01-01_opus46.md","size_in_bytes":2640},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Findings_Ledger_2026-01-01_opus46.md","size_in_bytes":847},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Pass1_Reader_Experience_2026-01-01_opus46.md","size_in_bytes":193},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Pass5_Character_Audit_2026-01-01_opus46.md","size_in_bytes":201},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Pass8_Reveal_Economy_2026-01-01_opus46.md","size_in_bytes":117},{"relative_path":"references/example-run-folder-coverage-degraded/Example_Synthesis_Read_Manifest_2026-01-01_opus46.md","size_in_bytes":1605},{"relative_path":"references/example-run-folder-coverage/Diagnostic_State.meta.json","size_in_bytes":1151},{"relative_path":"references/example-run-folder-coverage/Example_Audit_Invocation_Log_2026-01-01_opus46.md","size_in_bytes":278},{"relative_path":"references/example-run-folder-coverage/Example_Contract_2026-01-01_opus46.md","size_in_bytes":191},{"relative_path":"references/example-run-folder-coverage/Example_Core_DE_Synthesis_2026-01-01_opus46.md","size_in_bytes":2247},{"relative_path":"references/example-run-folder-coverage/Example_Findings_Ledger_2026-01-01_opus46.md","size_in_bytes":847},{"relative_path":"references/example-run-folder-coverage/Example_Pass1_Reader_Experience_2026-01-01_opus46.md","size_in_bytes":193},{"relative_path":"references/example-run-folder-coverage/Example_Pass5_Character_Audit_2026-01-01_opus46.md","size_in_bytes":201},{"relative_path":"references/example-run-folder-coverage/Example_Synthesis_Read_Manifest_2026-01-01_opus46.md","size_in_bytes":1465},{"relative_path":"references/example-run-folder-dispositions/Diagnostic_State.md","size_in_bytes":1531},{"relative_path":"references/example-run-folder-dispositions/Diagnostic_State.meta.json","size_in_bytes":2054},{"relative_path":"references/example-run-folder-dispositions/Example_Findings_Ledger_2026-03-01_opus46.md","size_in_bytes":2006},{"relative_path":"references/example-run-folder-dispositions/Submission_Readiness_Assessment_2026-03-01.md","size_in_bytes":910},{"relative_path":"references/example-run-folder-r1/Example_Findings_Ledger_2026-01-01_opus46.md","size_in_bytes":2352},{"relative_path":"references/example-run-folder-r1/Example_Revision_Report_2026-01-15_opus46.md","size_in_bytes":476},{"relative_path":"references/example-run-folder-r2/Example_Findings_Ledger_2026-02-01_opus46.md","size_in_bytes":2026},{"relative_path":"references/example-run-folder/Diagnostic_State.meta.json","size_in_bytes":2434},{"relative_path":"references/example-run-folder/Example_Audit_Invocation_Log_2026-01-01_opus46.md","size_in_bytes":82},{"relative_path":"references/example-run-folder/Example_Core_DE_Synthesis_2026-01-01_opus46.md","size_in_bytes":1243},{"relative_path":"references/example-run-folder/Example_Findings_Ledger_2026-01-01_opus46.md","size_in_bytes":1425},{"relative_path":"references/example-run-folder/Example_Manuscript_Snapshot_2026-01-01_opus46.md","size_in_bytes":664},{"relative_path":"references/example-run-folder/Example_Refutation_Record_2026-01-01_opus46.md","size_in_bytes":2660},{"relative_path":"references/example-scene-ethics-plan.md","size_in_bytes":2919},{"relative_path":"references/example-scene-function.md","size_in_bytes":3319},{"relative_path":"references/example-scene-roster.md","size_in_bytes":3422},{"relative_path":"references/example-setup-payoff-ledger.md","size_in_bytes":4895},{"relative_path":"references/example-state-card-round2.md","size_in_bytes":2004},{"relative_path":"references/example-state-card.md","size_in_bytes":2147},{"relative_path":"references/example-story-spine.md","size_in_bytes":4314},{"relative_path":"references/example-structure-map-manifest.md","size_in_bytes":8217},{"relative_path":"references/example-tension-points.md","size_in_bytes":3895},{"relative_path":"references/example-timeline.md","size_in_bytes":1905},{"relative_path":"references/example-uncertainty-ledger.md","size_in_bytes":1493},{"relative_path":"references/example-vocabulary-guide.md","size_in_bytes":2968},{"relative_path":"references/example-worldbuilding-bible.md","size_in_bytes":7960},{"relative_path":"references/execution-modes-reference.md","size_in_bytes":5160},{"relative_path":"references/findings-ledger-format.md","size_in_bytes":10571},{"relative_path":"references/firewall.md","size_in_bytes":2202},{"relative_path":"references/focused-audit-contract.md","size_in_bytes":2729},{"relative_path":"references/fragment-synthesis.md","size_in_bytes":9484},{"relative_path":"references/franklin-pathway.md","size_in_bytes":45289},{"relative_path":"references/genre-calibration-inline.md","size_in_bytes":10239},{"relative_path":"references/genre-horror.md","size_in_bytes":24618},{"relative_path":"references/genre-literary.md","size_in_bytes":44289},{"relative_path":"references/genre-mystery.md","size_in_bytes":20255},{"relative_path":"references/genre-romance.md","size_in_bytes":15949},{"relative_path":"references/genre-sff.md","size_in_bytes":46239},{"relative_path":"references/genre-template.md","size_in_bytes":4783},{"relative_path":"references/genre-thriller.md","size_in_bytes":21553},{"relative_path":"references/handoff-protocol.md","size_in_bytes":10120},{"relative_path":"references/hybrid-mode.md","size_in_bytes":30466},{"relative_path":"references/intake-interview.md","size_in_bytes":5608},{"relative_path":"references/intake-router-design.md","size_in_bytes":10698},{"relative_path":"references/intake-router-runtime.md","size_in_bytes":30189},{"relative_path":"references/interpretable-stylometric-explanation.md","size_in_bytes":4598},{"relative_path":"references/legal-risk-register.md","size_in_bytes":13175},{"relative_path":"references/manuscript-visualizations.md","size_in_bytes":6458},{"relative_path":"references/nonfiction-intake-routing.md","size_in_bytes":3810},{"relative_path":"references/output-policy.md","size_in_bytes":25053},{"relative_path":"references/output-structure.md","size_in_bytes":23080},{"relative_path":"references/partial-manuscript.md","size_in_bytes":14297},{"relative_path":"references/pass-10.md","size_in_bytes":17172},{"relative_path":"references/pass-11.md","size_in_bytes":23696},{"relative_path":"references/pass-dependencies.md","size_in_bytes":76824},{"relative_path":"references/promise-contract.md","size_in_bytes":9797},{"relative_path":"references/reader-contract-outline.md","size_in_bytes":4668},{"relative_path":"references/reference-index.md","size_in_bytes":3817},{"relative_path":"references/reverse-outline-template.md","size_in_bytes":1935},{"relative_path":"references/run-core.md","size_in_bytes":72441},{"relative_path":"references/run-full.md","size_in_bytes":57657},{"relative_path":"references/run-synthesis.md","size_in_bytes":100730},{"relative_path":"references/series-state-template.md","size_in_bytes":3024},{"relative_path":"references/setup-payoff-ledger.md","size_in_bytes":5040},{"relative_path":"references/state-lifecycle.md","size_in_bytes":24399},{"relative_path":"references/submission-readiness.md","size_in_bytes":19082},{"relative_path":"references/submission-triage.md","size_in_bytes":10508},{"relative_path":"references/synthesis-argument.md","size_in_bytes":4078},{"relative_path":"references/worldbuilding-bible.md","size_in_bytes":10965}],"name":"core-editor","skill_md_contents":"---\nname: core-editor\ndescription: >\n  AI developmental editing framework for fiction, narrative nonfiction, and\n  argument-shaped nonfiction; owns the Nonfiction Argument Engine.\n  Use when the user asks to \"run a development edit,\" \"analyze my manuscript,\"\n  \"diagnose structural issues,\" \"start a new project,\" \"generate a contract,\"\n  \"run the passes,\" \"do a revision round,\" or any request involving manuscript\n  analysis, structural diagnosis, or editorial feedback. Also triggers on\n  \"APODICTIC,\" \"APDE,\" or \"development editor.\"\nversion: 2.13.3\n---\n\n# APODICTIC Development Editor — Core Orchestrator\n\n---\n\n## Canonical Source\n\n`SKILL.md` is the thin orchestrator. It defines workflow, routing, and policy.\nExecution details live in reference files loaded on demand.\nDedicated reference files (genre modules, specialized audits, `references/pass-11.md`) win for module-specific rules.\n\n**Branding note:** Public-facing name is `APODICTIC Development Editor`. Tagline: *Developmental editing that listens before diagnosing.* The plugin author's identity must never be confused with the manuscript author's identity.\n\n**Model note:** This framework is designed for strong frontier models with reliable instruction-following and ample context. On weaker models, expect degraded severity honesty, weaker thematic interpretation, and lower fix quality.\n\n---\n\n## Author adjudication entry point\n\nFor `apodictic-adjudicate`, load `references/craft/approval-workflow.md` and follow that\nworkflow directly. It presents an existing reconstruction graph and records\nexplicit author decisions. Do not start Core DE passes or generic audit output\nrouting. Semantic exclusion screening remains unavailable; never override a\nblocked approval or represent this partial workflow as drafting acceptance.\n\n## Plugin Structure\n\nThis skill is the core of the APODICTIC plugin. Three companion workflows handle specialized functions:\n- **Plot coaching** — Spine diagnosis (50 spines), selection coaching, fantasy & series architecture\n- **Specialized audits** — Deep-dive audits, tag audits, and research modes (loaded on demand)\n- **Revision coaching** — Post-diagnostic revision coaching: session planning, stuck-point coaching, momentum tracking, deadline management (loaded via `apodictic-coach`)\n\n**Delegation principle:** Core runs the development edit workflow. Everything else delegates to companion workflows or reference files. Core does not carry audit catalogs, tag-audit internals, or genre deep-dives.\n\n---\n\n## The Firewall\n\n<!-- Firewall definition has been extracted to `references/firewall.md` (single canonical source).\n     Load `references/firewall.md` for the full no-content-invention firewall definition.\n     The `nonfiction-argument-engine` skill references the same file. -->\n\n*See `references/firewall.md` for the canonical Firewall definition. The no-content-invention rule applies in all modes — editorial, argument, coaching. Other surfaces (`revision-coach/SKILL.md §The Coaching Firewall`, `adversarial-stress-test.md §Firewall Compliance`, `run-full.md` §QA gate, `pass-11.md` §Forbidden) add only context-specific elaborations; the definition lives in `references/firewall.md` only.*\n\n---\n\n## Pass Resolution\n\nPass execution is concern-driven, not hardwired to a single fixed sequence.\n\n- Resolve the user's concern to a minimum pass set using `references/pass-dependencies.md`.\n- Pull required upstream dependencies automatically from the same file.\n- Execute by dependency tier (parallel where permitted), then synthesize.\n- If concern is unspecified or ambiguous, default to **General diagnostic floor**: Passes 0, 1, 2, 5, 8.\n- If findings indicate interconnected systemic issues, recommend expansion to the full pass set per auto-escalation rules.\n\n---\n\n## Workflow Contract\n\n### 1. Intake (always runs)\nDraft-then-validate contract from text analysis. Hypothesis-driven questions. Output: `[Project]_Contract_[runlabel].md`.\nIf router output is available (`artifact`, `goal`, `concern`, `constraints`, `operator`), treat those fields as pre-filled and skip redundant intake questions.\n\n### 2. Pass Resolution\nLoad `references/pass-dependencies.md`, resolve concern to minimum pass set, add dependencies, then run selected passes in dependency order.\n\n### 3. Synthesis\nLoad `references/run-synthesis.md`. Root cause analysis (max 5), triage (Must-Fix / Should-Fix / Could-Fix), adversarial self-check, adversarial reader stress test, editorial letter. After writing: mechanical section validation, then evidence spot-check (5 claims verified against manuscript).\n\n### 4. Expansion Recommendation\nApply auto-escalation rules from `references/pass-dependencies.md` §2b. Recommend expansion to full pass set when issue density/complexity exceeds the scoped run.\n\n### 5. Revision Round (when re-analyzing)\nLoad `references/state-lifecycle.md`. Delta scan, ripple check, resolution verification, new issue detection.\n\n### 6. Submission Readiness (when submitting)\nWhen the writer asks \"is this ready to submit?\", run the Submission Readiness Workflow: Core DE → Synthesis → Pass 11 → Compression Test → Unified Readiness Assessment. Entry point: `apodictic-ready` command or `full_draft + submit` route. Load `references/submission-readiness.md` for full specification. For deadline-constrained writers, route to Submission Triage instead (`references/submission-triage.md`).\n\n### 7. Scene-Level Handoff (when requested)\nWhen diagnosis is complete for a scoped scene and the writer wants execution help, follow `references/handoff-protocol.md` for mode switch, state persistence, and re-entry.\n\n**Execution details:** Load `references/run-core.md` for intake, pass execution, and Findings Ledger protocol. Load `references/run-synthesis.md` after passes complete for audit integration, synthesis, and deliverables. Load `references/state-lifecycle.md` for revision rounds and state gardening. Use `references/pass-dependencies.md` for pass resolution. For full expansion: load `references/run-full.md`.\n\n**Execution mode:** The system supports context-aware execution. **Single-agent** (default when ≥1M context tokens and manuscript fits): one subagent runs all passes sequentially in a single context, with the Findings Ledger persisted to disk after each pass. **Sequential** (default for standard-context or very large manuscripts): each pass runs as an independent subagent with the full manuscript. **Hybrid** (optional): Pass 0+1 produces a focus map; later passes run as independent subagents with targeted excerpts (~2–3x token cost). **Swarm** (optional): independent subagents with parallel execution (~5x token cost; architectural isolation for a final-round verification pass — reserve for submission prep, not everyday depth). Mode selection is automatic based on context window size and manuscript token load; the user can override at intake. See `references/run-core.md` §Execution Mode for protocol details; `references/hybrid-mode.md` for the focus map specification.\n\n---\n\n## Pass Architecture\n\nPass dependency and parallelization rules are canonical in `references/pass-dependencies.md`:\n\n- Tier 1 (read passes) can run in parallel.\n- Tier 2 (analysis passes) require resolved Tier 1 dependencies.\n- Tier 3 synthesis runs after selected Tier 2 passes complete.\n- Pass 11 runs only when submission readiness is in scope.\n\nNever synthesize before all selected passes and their dependencies are complete.\n\n---\n\n## Output Policy (Summary)\n\n- Maximum 5 root causes; 10 revision checklist items (Core DE), 15 (Full DE); 10 must-fix flags\n- Every flag requires 2-4 specific scene/page references\n- Quote budget: ≤25 words per excerpt, or paraphrase + pointer\n- Every proposed fix must list what it risks harming\n- All outputs are author-facing. Translate framework shorthand on first use. The author should never need to consult framework documentation.\n- Confidence markers: HIGH / MEDIUM / LOW / UNCERTAIN — never present LOW or UNCERTAIN as definitive\n- Severity honesty: do not soften Must-Fix to Should-Fix. Apply severity floor rules.\n\n### Pass-Detail Artifact Headers\n\nEvery pass-detail output artifact must begin with a one-line blockquote header that makes the file legible without framework knowledge:\n\n```\n> **Macro block:** [block name from §3 of pass-dependencies.md] · **Writer question:** [the §3 User Question for this block] · **Legacy pass id:** Pass [N]\n```\n\nThe three values are **read from `references/pass-dependencies.md §3` (Macro Block Definitions) — never authored.** §3 is the single source of truth for the 8 blocks, the pass→block map, and each block's User Question. `scripts/validate.sh pass-header` checks the header against §3 (see `references/run-core.md §What each pass subagent returns` and the canonical `references/example-pass-artifact-header.md`).\n\nMapping (**derived from §3 — reconcile here only by re-deriving from §3, do not hand-edit against it**):\n\n| Pass | Macro Block | Writer Question |\n|------|-------------|-----------------|\n| 0 | Structure Map | Is the structure working? |\n| 1 | Reader Dynamics | Does the pacing hold? |\n| 2 | Structure Map | Is the structure working? |\n| 3 | Reader Dynamics | Does the pacing hold? |\n| 4 | Emotional Dynamics | Are the emotional beats earning their weight? |\n| 5 | Character Architecture | Are my characters landing? |\n| 6 | Scene Delivery | Are the scenes doing their jobs? |\n| 7 | Character Architecture | Are my characters landing? |\n| 8 | Reveal Economy | Is the information flow right? |\n| 9 | Theme & Continuity | Does it cohere? |\n| 10 | Theme & Continuity | Does it cohere? |\n| 11 | Submission Readiness | Is this ready? |\n\n### Results Guide Artifact\n\nAfter synthesis, produce `[Project]_Results_Guide_[runlabel].md` — a map from writer questions to the relevant artifacts from the run. This is the first file after the editorial letter and helps the writer navigate their results without framework knowledge.\n\nInclude only blocks and artifacts from passes that actually ran. Format:\n\n```markdown\n# Results Guide — [Project Name]\n_Run: [runlabel]_\n\n## How to use this guide\nStart with the **Editorial Letter** for the diagnosis and priority repairs.\nUse this guide to find the detailed analysis behind each finding.\n\n---\n\n## Your results by question\n\n### [Writer question — e.g., \"Is the structure working?\"]\n- Editorial Letter § [Macro block name]\n- Detail: `[pass artifact filename]`\n- Detail: `[pass artifact filename]`\n\n[... repeat for each macro block that ran ...]\n\n## Specialized audits run\n- [Audit Name]: `[artifact filename]`\n\n## State files\n- Diagnostic State: `Diagnostic_State.md`\n- Findings Ledger: `[Project]_Findings_Ledger_[runlabel].md`\n\n## What to do next\n- `apodictic-coach` — plan revision sessions from this diagnosis\n- `apodictic-audit [name]` — run a focused deep-dive on a specific concern\n```\n\nOmit the \"Specialized audits run\" section if no audits ran. Omit \"Argument State\" from state files unless the nonfiction engine was active.\n\n**Full output policy (tone, evidence burden, caps, anti-sycophancy, severity floors, pass-level output protocol):** Load `references/output-policy.md`.\n\n---\n\n## Project Integration\n\nWhen operating within a manuscript project, the **active project output context** is the project root folder that holds the manuscript's APODICTIC artifacts and rolling state. See `references/output-structure.md` §Folder Architecture for the canonical folder structure.\n\n**Key rules:**\n- Rolling state (`Diagnostic_State.md`, `SYNTHESIS.md`, `Session_Plan_{NN}.md`, `README.md`) lives at the **project root**\n- Run artifacts (pass outputs, contracts, findings ledgers, audit reports, results guides) live inside **`runs/YYYY-MM-DD_{model}_{type}/`**\n- The `Outputs/` sibling convention is deprecated. For existing projects with an `Outputs/` folder, treat it as the project root and create `runs/` inside it.\n- Never write project state inside the plugin repo, the installed plugin cache, or any other APODICTIC framework directory.\n\nWhen operating within a project:\n\n1. **CHECK** for existing contract artifact before running intake\n2. **REFERENCE** character portraits during Pass 5 for consistency\n3. **REFERENCE** story guides during Pass 9 for controlling idea alignment\n4. **CREATE** the run folder (`runs/YYYY-MM-DD_{model}_{type}/`) at the start of each run\n5. **OUTPUT** all run artifacts (pass reports, contract, findings ledger, results guide) into the run folder\n6. **INITIALIZE** `Diagnostic_State.md` at the project root from `references/diagnostic-state-template.md` if it does not exist\n7. **SET** the Mode section's `**Current:**` field to `diagnostic` unless an active handoff is explicitly in effect\n8. **APPEND** handoff entries to `Handoff History` (never overwrite prior cycles)\n9. **UPDATE** `Diagnostic_State.md` at the project root with cumulative findings across sessions, including author decisions and control questions when synthesis produces them\n10. **UPDATE** `SYNTHESIS.md` at the project root — if this is the first run, copy synthesis there; if prior runs exist, incorporate new findings with a methodology note listing contributing runs\n11. **APPEND** a row to `README.md` run archive table\n\nWhen no project context exists, proceed with intake from scratch.\n\n### Pass-10-Class Rolling Structured Artifacts\n\n*Canonical home for the Pass-10-Class artifact pattern. Other surfaces (`pass-dependencies.md §1 Tier 1 Pass 10 row`, `run-synthesis.md §Step 2 Pass-10-Class artifact integration`, `references/pass-10.md`) reference this section's definition and add only artifact-instance specifics (Timeline schema, Argument_State schema, etc.).*\n\nA recognized class of project-level rolling artifacts the framework uses to track manuscript state across runs. Pass-10-class artifacts share these properties:\n\n- **Project-level**, not run-folder-scoped (lives at the project root, persists across runs)\n- **Structured**, machine-readable or near-machine-readable (schema specified per artifact)\n- **Diffable** across runs (subsequent runs produce a diff section showing what changed)\n- **Validator-paired** (each instance has a mechanical validator that surfaces drift, conflicts, or schema violations)\n- **Synthesis-layer integrated** (the synthesis step consumes the artifact and may treat numeric drift as severity input)\n\nThis contrasts with run-folder-scoped pass artifacts (e.g., individual pass reports, audit findings files), which are run-specific and not designed for cross-run diff.\n\nRecognized instances:\n- `Diagnostic_State.md` — rolling diagnostic state at project root (already exists)\n- `SYNTHESIS.md` — master revision plan at project root (already exists)\n- `Argument_State.md` — argument-shaped nonfiction state at project root (already exists; see argument-state-schema)\n- `Series_State.md` — cross-volume continuity at series root (already exists)\n- `Timeline.md` — temporal architecture for fiction with Pass 10 (live; schema in `references/pass-10.md`; three mechanical validators in `scripts/validate.sh`: `timeline-diff`, `timeline-arithmetic`, `timeline-anchor-conflict`)\n- `Plot_Spine.md` — spine-driven fiction state (future; intersects Plot Architecture skill)\n\nWhen adding a new project-level rolling artifact, instantiate it against this class: define its schema, pair it with a validator, specify the synthesis-layer integration. `Timeline.md` (Phase 6 Wave 1) is the first live instance added under the named pattern; `Plot_Spine.md` is the next planned instance.\n\n---\n\n## Definition of a Scene\n\n**Scene** = a continuous unit of time/space with a POV holder, a local goal, and a detectable turn (change in value, knowledge, or strategy).\n\nIf there is no turn, it's a **beat**. Beats get grouped until a scene exists.\n\n### Units Terminology\n- **Lines** = manuscript line numbers (for scene/passage references)\n- **Words** = actual word count (for length and proportion analysis)\nNever conflate these.\n\n### Quantitative Verification (Required)\nBefore reporting any word counts or proportions:\n1. Measure, don't estimate. Run `wc -w [manuscript]` to get total word count.\n2. Measure parts separately. Extract each section and count individually.\n3. Verify before analysis. All proportional analysis must use measured values.\n4. State measurements explicitly.\n\n---\n\n## Delegation Rules\n\n### Pre-Writing\nWriter has idea but no manuscript → Start the pre-writing pathway.\n\n### Plot Structure\nSpine diagnosis (which of the 50 spines / 12 families governs the whole-work shape), selection coaching, structural triage on stuck drafts, hybrid design, fantasy/series architecture → Start plot coaching (`plot-architecture` skill).\n\nThis is distinct from **Pass 2: Structural Mapping** (Tier 2 pass within a development edit run), which maps on-page act/movement boundaries, beat presence, missing-beat lists, and structural causality. Pass 2 answers \"is the structure I have on the page working\"; Plot Architecture answers \"which spine is this and does that paradigm hold.\" See `plot-architecture/SKILL.md §Plot Architecture vs. Pass 2 (Structural Mapping) — Boundary` for cross-reference and sequencing.\n\n### Nonfiction Argument Engine\nWhen intake resolves `constraint=nonfiction` AND the declared form is in the persuasive-argument family (op-ed, policy brief, testimony, academic argument, open letter, white paper, advocacy argument, legal brief, regulatory comment, expert affidavit — per `references/intake-router-runtime.md §6 Table A`), delegate to the **`nonfiction-argument-engine` skill**. Pass the full run-shape (form, audience burden, stakes, high-stakes flag); receive the standard artifact set (editorial letter + Findings Ledger + `Argument_State.md` + marked-up manuscript). The fiction path and the argument path share the core editorial spine; this delegation makes the argument route explicit rather than implicit.\n\nDo NOT remove or bypass the existing specialized-audits dispatch (§4a/§4b routing) — the nonfiction-argument-engine itself calls specialized-audits for its argument-cluster audits (Dialectical Clarity, Red Team, Evidence, Field Recon, Citation Verifier). This delegation is additive, not a replacement.\n\n### Specialized Audits\nAny deep-dive audit, tag audit, or research mode → Run the audit. The specialized-audits workflow maintains its own routing table and trigger logic.\n\n### Scene-Level Handoff\nWhen the writer requests prose-level execution help for a diagnosed scene:\n- Load `references/handoff-protocol.md`\n- Offer handoff using the required confirmation template\n- Write context into `Diagnostic_State.md` in the active project output context and set mode to `execution`\n- Suspend core-editor constraints for execution mode\n- Re-enter diagnostic mode only via explicit phrase trigger or `apodictic-start` resume check\n\n### Pass 11: Critical Quality & Market Viability\nAuthor states publication/submission goal, requests honest assessment, or mentions query materials → Load `references/pass-11.md`.\n\n### Character Architecture (Deep)\nPsychology engine, arc types, agency quotient, genre tuning packs → Load `references/character-architecture.md`.\n\n---\n\n## Genre Module Routing\n\nDuring intake, identify the manuscript's genre and load the corresponding module. Genre modules modify pass behavior (recalibrate thresholds, add tracking, adjust false positive warnings).\n\n| Genre | Reference File | Key Modification |\n|-------|---------------|------------------|\n| Literary Fiction | `references/genre-literary.md` | Pass 9 priority; Literary Mode for genre-bending; Register Uncertainty diagnostic |\n| Horror (Psychological) | `references/genre-horror.md` | Certainty axis priority; dread escalation tracking; reality anchoring |\n| Science Fiction / Fantasy | `references/genre-sff.md` | Rule Ledger (Pass 10); Sanderson's Laws; integration tests |\n| Romance | `references/genre-romance.md` | Relationship engine; trust-rupture-repair cycle; 15 named flags |\n| Mystery | `references/genre-mystery.md` | Information pressure; clue economy; fair play tests |\n| Thriller | `references/genre-thriller.md` | Threat escalation; clock pressure; protagonist competence |\n\n**If manuscript includes erotic/intimate content:** Activate the **Erotic Content tag** via specialized-audits. Adds heat level, consent calculus, escalation vs. repetition audit, erotic-specific flags.\n\n**If Literary Fiction is primary with other genre modules active:** Activate **Literary Mode** (see `references/genre-literary.md`). Genre conventions become available tools, not requirements.\n\n---\n\n## Reference Files (Load on Demand)\n\nCompact routing map below. Full index — templates, deprecated files, and per-file descriptions — in `references/reference-index.md`.\n\n**Execution:** `run-core.md` (every run: intake, pass execution, ledger protocol) · `run-synthesis.md` (after passes: audit integration, synthesis, deliverables, evidence spot-check) · `pass-dependencies.md` (concern → scoped pass set + order) · `run-full.md` (advanced passes 3/4/6/7/9/10) · `output-policy.md` (before writing output) · `output-structure.md` (folders, naming, lifecycle, sidecar — at write time) · `adversarial-stress-test.md` (letter §7) · `state-lifecycle.md` (revision rounds, state gardening) · situational: `partial-manuscript.md`, `editor-scaffolding.md` (`operator:editor`), `diagnostic-vocabulary.md` (`operator:facilitator`), `fragment-synthesis.md`, `handoff-protocol.md`, `character-architecture.md`, `pass-11.md`.\n\n**Genre modules** (load by detected genre, primary or secondary): `genre-literary.md` · `genre-horror.md` · `genre-sff.md` · `genre-romance.md` · `genre-mystery.md` · `genre-thriller.md`.\n\n**Templates, other references, and deprecated files:** see `references/reference-index.md`.\n\n---\n\n## QA Guardrails\n\n1. Verify word counts before proportional claims.\n2. Apply severity floor rules (see `references/output-policy.md`).\n3. Log uncertainty explicitly — never force false clarity.\n4. Run adversarial self-check before writing editorial letter.\n5. Check every flag against stated author intent before finalizing.\n6. Run mechanical validation (plugin-bundled `scripts/validate.sh`, or inline fallback) at each checkpoint (see `references/run-core.md` §Mechanical Validation Protocol).\n7. Run evidence spot-check after synthesis — verify 5 claims against manuscript before delivering (see `references/run-synthesis.md` §Evidence Spot-Check).\n\n---\n\n*This skill provides developmental editing methodology. It diagnoses structure; the author invents content. The system surfaces patterns, asks questions, and proposes intervention classes. Creative authority remains entirely with the author.*\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}