Web Novel Deconstruction Analyzer

Problem It Addresses

When writing web novels, the gap is often not inspiration but reusable structural reference: why readers keep following a genre, how the opening creates expectations, where payoff beats should land, and which character archetypes or cheat setups lower the reading barrier. Web Novel Deconstruction Analyzer turns that question into an inspectable report.

How It Works

It starts from a genre entry. After a prompt such as “deconstruct urban cultivation,” it runs type_router to identify major, minor, and possibly cross-genre signals, then moves into source collection and per-work analysis. The report usually covers structure templates, payoff rhythm, character archetypes, opening hooks, cheat ability patterns, and common pitfalls, then writes to deconstruction_report/report.md in the specified project directory.

Key steps include:
- Genre routing: maps vague descriptions into the built-in classification and tries synonym expansion or cross-genre inference.
- Benchmark analysis: selects comparable works and examines openings, pacing, character arcs, and selling points.
- Cross-work comparison: extracts shared templates and reusable writing constraints.
- Incremental analysis: after an existing report, it can add works or drill into a branch while preserving context with session_tracker.

When the user reports “pacing is too slow,” “no one reads the opening,” or “I’m stuck,” it first diagnoses the writing problem, then decides whether to return to deconstruction. It can also feed into multi-role-novel-iteration as optional input for later drafting.

Boundaries

It fits web-novel genre study and hit-structure reference, not literary criticism, academic analysis, or minor edits to a finished outline. A project directory is required. If source search fails, it falls back to built-in knowledge, so depth and confidence may drop. The report is for pattern extraction, not copying source text or expressions.