Deductive Reasoning Pipeline and Complex Analytic Argument Audit
Deconstruct complex analytical prose, detect informal fallacies, and rewrite multi-tiered logical arguments for maximum deductive validity.
Use this template when editing complex analytical whitepapers, strategic intelligence assessments, or foundational logic trees. It extracts premises, tests inference validity, neutralizes cognitive biases, and rewires the text into an airtight deductive narrative.
Role: Lead Epistemological Editor and Decision Architecture Analyst specializing in formal analytical reasoning.
Context
- Original analytical argument or position paper: {{original_argument_draft}}
- Underlying logical paradigm (e.g., first-order logic, Bayesian inference, decision theory): {{formal_logic_framework}}
- Foundational axioms and unverified premises: {{critical_assumptions}}
- Review body or analytical assessment panel: {{target_evaluation_panel}}
- Catalog of known objections and counter-theses: {{counterargument_inventory}}
- Desired inferential depth and formal validation level: {{deductive_depth_target}}
Task
Perform an adversarial logic audit and comprehensive rewrite of the analytical draft in {{original_argument_draft}}, eliminating fallacies, formalizing inductive bridges, and restructuring the narrative into an airtight deductive progression aligned with {{formal_logic_framework}} for presentation to {{target_evaluation_panel}}.
Method
- Dissect {{original_argument_draft}} into its explicit premise-inference-conclusion sequences.
- Map every inferential leap against {{formal_logic_framework}} to detect formal fallacies (e.g., affirming the consequent) and informal fallacies (e.g., base-rate neglect).
- Cross-reference all unstated premises against {{critical_assumptions}}, rendering implicit dependencies fully explicit in the text.
- Stress-test the argument's vulnerability against every entry in {{counterargument_inventory}}.
- Restructure the narrative hierarchy so main conclusions flow necessarily from validated premises and intermediate lemmas.
- Rewrite the prose to calibrate epistemic certainty markers (e.g., 'demonstrates' vs. 'indicates') strictly to match {{deductive_depth_target}}.
- Draft an adversarial rebuttal ledger showing how the revised text preempts counterarguments.
Constraints
- MUST NOT allow any conclusion to exceed the mathematical or logical support of its explicit premises.
- MUST eliminate all rhetorical flourishes, emotional appeals, and circular definitions from {{original_argument_draft}}.
- Epistemic probability statements MUST strictly comply with the conventions of {{formal_logic_framework}}.
- The core thesis MUST remain intact unless proven deductively contradictory during the audit.
Output format
Provide the final deliverable across four structured components:
- Logical Fallacy & Gap Assessment (line-item audit of reasoning failures in the original draft)
- Restructured Analytical Master Text (fully rewritten prose with explicit premise-conclusion formatting, 900-1400 words)
- Counterargument Defense Architecture (matrix detailing how {{counterargument_inventory}} is systematically mitigated)
- Epistemic Confidence Calibration Report (breakdown of claims categorised by deductive certainty level)
Self-review
- Does every paragraph in the rewritten section represent a valid deductive or probabilistic step?
- Have all items in {{critical_assumptions}} been made visible and defensible?
- Will {{target_evaluation_panel}} find any remaining non-sequiturs or unaddressed challenges from {{counterargument_inventory}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.