Technical Whitepaper Narrative Validation Checklist

Role: Principal Developer Advocate and Enterprise Editorial Director

Context

• Target demographic: {{developer_audience_profile}}
• Core architectural domain: {{core_architecture_topic}}
• Distribution vehicle: {{target_publishing_channel}}
• Primary language/stack: {{code_sample_language}}
• Market differentiation context: {{competitor_positioning_angle}}
• Target rigor standard: {{technical_depth_score}}

Task

Construct an advanced editorial and technical validation checklist that systematically evaluates a technical whitepaper on {{core_architecture_topic}}, guaranteeing it balances deep engineering credibility for {{developer_audience_profile}} with persuasive positioning against {{competitor_positioning_angle}}.

Method

1. Review the conceptual architecture thesis against the expectations of {{developer_audience_profile}} to identify unsupported assertions.
2. Formulate verification criteria for technical diagrams, architecture schemas, and data flow models within {{core_architecture_topic}}.
3. Build validation steps to confirm all {{code_sample_language}} snippets follow modern conventions, production-grade safety, and idiomatic patterns.
4. Design narrative velocity checks to ensure the manuscript avoids superficial marketing hyperbole and maintains {{technical_depth_score}} rigor.
5. Establish claim-verification checkpoints for performance claims, throughput benchmarks, and comparative statements involving {{competitor_positioning_angle}}.
6. Audit the structural transitions between problem diagnosis, technical mechanics, and architectural resolution.
7. Develop compliance and source-attribution validation gates for third-party citations, RFCs, and academic references.
8. Generate a weighted scoring checklist categorized into Narrative Integrity, Code Integrity, and Competitive Defensibility.

Constraints

• Checklist points MUST mandate reproducible benchmarks for any empirical performance or cost-reduction claims.
• You MUST NOT allow purely subjective marketing adjectives (e.g., "effortless", "ultra-fast") to pass without technical qualification.
• Technical checks MUST enforce strict formatting, dependency declarations, and version pinnotes for all {{code_sample_language}} samples.
• The output MUST follow the prescribed section sequence without omitted tiers.

Output format

1. Architectural Rigor Audit Gate (6 binary checks targeting technical accuracy and {{code_sample_language}} validity)
2. Narrative & Argumentation Structure Gate (5 binary checks on claims and logic)
3. Developer Trust & Commercial Positioning Gate (5 binary checks focusing on {{competitor_positioning_angle}})
4. Remediation Action Priority Table (defect class, severity tier, required editorial rewrite)

Self-review

• Confirm that evaluation standards match the sophistication level expected by {{developer_audience_profile}}.
• Ensure each checklist criterion contains a concrete failure flag that triggers manuscript rejection.
• Verify all checks directly address {{core_architecture_topic}} technical accuracy.