Writing is a deliverable
Your design isn't done when the simulator stops. It's done when someone else can understand and reproduce your reasoning from text alone. That's the writeup. Skip it and your work disappears.
The five-section structure
Every CrystalSim summary should have these five sections, in order:
1. Design description — one paragraph: what you built, layer by layer. 2. Materials chosen and why — bullet list. Channel material → why this one. Gate material → why this one. Etc. 3. Test results with baseline comparison — table or bullets. Each metric: your value, baseline value, ratio. 4. ECCF calculation — show the inputs (d₃₃, E, Q, δ, f), the formula, and the result. 5. Simon's Law projection — pessimistic/moderate/optimistic with parameters and final multiplier.
Three paragraphs minimum, ten max. Anything longer and reviewers skim.
Exercise — generate, edit, export
1. Open the Copilot with your best design attached. 2. Ask: 'Write a 3-paragraph technical summary of this design using the five-section structure: design / materials / test results / ECCF / Simon's Law projection.' 3. Read every number it cites. Cross-check against the actual test panel. Fix any wrong numbers. 4. Open the Export menu and use the Report Generator to save a PDF. 5. Review the PDF — does the design diagram match the prose?
Tone & clarity rules
- Lead with the result, not the journey. 'Switching speed 12.4 GHz, 1.6× silicon baseline' before the explanation. - One claim, one sentence. Long sentences hide errors. - Numbers carry units. '12.4 GHz', not '12.4'. - Tradeoffs out loud. 'Wins on TOPS/W, loses on absolute TOPS at scale.' - No marketing words. 'Revolutionary', 'breakthrough', 'unprecedented' all weaken credibility.
- Structure a technical summary that reviewers actually read.
- Use the AI Copilot to draft, then edit for accuracy.
- Export with the Report Generator.
- AI-assisted writing is editing, not authoring.