Bonus Episode 1: The Diagnostic Toolkit: How I Analyse Manuscripts Like Code

Throughout this series, I have been referencing something called the Structural Diagnostic. You have heard me quote from diagnostic reports, analyses that identified drift zones, flagged repetition, measured motif saturation.Some of you have asked: what exactly is this? How does it work? Is it something you can use on your own manuscript?Today I open up the toolkit and show you what is inside.I wear multiple hats. Developer. Project manager. Musician. Writer. It was the developer hat that led to the diagnostics. In software, you do not just write code and hope it works. You test it. You run diagnostics. You have tools that analyse your codebase for bugs, inefficiencies, patterns that indicate problems.One day I thought: why do we not have this for manuscripts?So I built it.In this episode, I walk you through the five diagnostic components I use:→ Scene Purpose Mapping: tagging structural function (plant, payoff, escalation, revelation, turn)→ Word Distribution Analysis: catching act imbalances before they become crises→ Motif Frequency Tracking: measuring occurrence and distribution→ Repetition Detection: finding unconscious patterns in phrases and structures→ Pacing Analysis: matching prose rhythm to scene energyI show you a real diagnostic report from The Reader of the Empress, the one that confirmed I was lost at Chapter Forty Seven, with Act Two bloated to eighty four percent of the manuscript.The diagnostic did not fix the problem. But it confirmed it. It gave me specific targets. And it made the path to recovery clear.—Resources:Custom GPT and Companion Workbook —Questions? Reach out at rondanini.com