Free tool · works now

Argument Outline Builder

Structure analytical theses, supporting claims, objections, and rebuttals into rigorous Markdown argument maps without dropping counterarguments.

Interactive Argument Builder Workbench

Supporting Premises

Each premise should provide a verifiable reason supporting your thesis.

Premise 1
Premise 2
Premise 3

Objections & Counterarguments

Anticipate real counterarguments. Critical test: objections are never dropped!

Objection 1 (moderate)
Objection 2 (critical)
100/100Robustness Score
3/3Supported Premises
2/2Addressed Objections
0Vulnerable Gaps
All premises are cited and all counterarguments are addressed.

Why Argument Mapping Matters for Knowledge Workers

When researching complex problems, drafting technical specifications, or writing essays, human intuition is vulnerable to confirmation bias. We naturally assemble evidence that flatters our preferred conclusion while skimming past inconvenient trade-offs. Centralized generative AI assistants frequently amplify this vulnerability: instructed to produce an essay outline, they will fabricate evidence, smooth over genuine objections, or discard counterarguments to deliver a superficial sense of resolution.

The Argument Outline Builder operates on a fundamentally different principle: dialectical integrity. Rather than outsourcing reasoning to an opaque remote model, it provides a deterministic workbench to map your thesis using formal argumentative structures inspired by the classical syllogism and the Toulmin model. Every supporting premise must be grounded in an empirical citation, logical proof, or vault note link, and every critical counterargument must be acknowledged and answered.

The Toulmin Framework in Plain-Text Markdown Notes

Philosopher Stephen Toulmin identified that persuasive real-world arguments do not function like simple geometric proofs. Real claims operate in contingent, noisy environments where validity depends on explicit warrants, grounds, and rebuttals:

1. Central Thesis (Claim)

The primary assertion, decision, or thesis statement being defended. Without a crisp thesis, supporting premises lose thematic focus.

2. Supporting Premises (Grounds)

Empirical data, mathematical proofs, experimental results, or primary source citations that substantiate the thesis.

3. Objections & Defeaters

Counterarguments raised by skeptics or competing architectural models. Under the Toulmin system, unaddressed objections invalidate the claim.

4. Rebuttals & Concessions

The explicit mechanism used to answer the objection: direct refutation, engineering mitigation, or a disciplined concession that narrows the scope.

Guaranteed Counterargument Preservation

The critical design constraint of this tool is that an objection is never dropped merely because it weakens the thesis. If a reviewer or internal skeptic raises a valid concern regarding latency, migration cost, or developer friction, the tool will never silently delete or soften the issue. Instead, the workbench highlights unaddressed objections as active vulnerabilities, reducing the overall robustness score until you provide a legitimate refutation, mitigation strategy, or explicit scope concession.

When exported into your Obsidian or personal knowledge vault, objections are rendered inside prominent callout blocks (> [!warning] and > [!caution]). This ensures future readers or engineering teammates reviewing your architecture decision records (ADRs) can immediately evaluate the intellectual honesty of your proposal.

The Peril of Cloud AI Sycophancy in Argument Formulation

Recent empirical evaluations of large language models reveal a persistent behavioral pathology known as sycophancy: when asked to evaluate or outline a thesis, conversational models prioritize agreeing with the user's presuppositions rather than stress-testing weaknesses. If an engineer prompts a cloud assistant with a speculative hypothesis, the model frequently invents plausible-sounding supporting evidence, minimizes severe operational risks, and outright deletes legitimate objections to present an artificially clean, unassailable narrative.

In high-stakes technical writing—such as software architecture decision records, scientific grant proposals, and strategic product roadmaps—this bias is lethal. A thesis that looks cohesive on paper will rapidly collapse under real-world production stress when confronted with omitted failure modes. The Argument Outline Builder provides a disciplined cognitive backstop: by separating premises from objections and auditing coverage deterministically, the workbench forces you to confront difficult counterarguments before your proposal enters peer review.

Mapping Argument Outlines to Architecture Decision Records (ADRs)

Engineering organizations rely on Architecture Decision Records (ADRs) to document significant architectural choices and preserve institutional memory. When poorly drafted, ADRs often record only the winning option, failing to preserve the legitimate counterarguments and trade-offs that were weighed during debate. Three years later, new engineers question why an apparently suboptimal choice was made because the original constraints were never preserved.

You can use the structured output of this tool directly as the core decision matrix of your ADRs:

  • Context & Problem Statement: Mapped directly from the Context field, defining the architectural horizon, latency constraints, and operational environment.
  • Proposed Decision (Thesis): The specific architectural path being adopted (for example, choosing SQLite in-process storage over a distributed database cluster).
  • Considered Options & Supporting Grounds: The empirical benchmarks, memory profiling runs, and operational simplifications substantiating the choice.
  • Consequences & Mitigations (Objections): The negative trade-offs—such as multi-writer contention or backup orchestration complexity—clearly documented alongside their implemented mitigations.

Dialectical Synthesis: Moving Beyond One-Sided Polemics

Formal philosophical dialectic (thesis, antithesis, synthesis) demonstrates that truth is rarely achieved by simply asserting a claim and shouting down opposition. Intellectual progress occurs when a thesis is subjected to severe critical pressure, forcing the thinker to either refine the proposition, concede edge cases, or establish explicit operational boundaries:

Direct Refutation

Demonstrating that an objection rests on factually incorrect premises, superseded benchmarks, or faulty logical deductions.

Engineering Mitigation

Acknowledging that an objection identifies a real operational hazard, but showing that a specific safeguard (rate limiting, encryption, circuit breakers) neutralizes the risk.

Principled Concession

Admitting that the thesis does not hold under specific edge conditions, thereby narrowing the thesis scope to domains where validity is absolute.

Scope Boundary

Defining non-goals and explicit architectural non-requirements so critics do not evaluate the system against irrelevant criteria.

Plain-Text Portability: Wikilinks and Zettelkasten Integration

Every artifact generated by this workbench is designed to live permanently in your local plain-text Markdown folder. When citing supporting evidence in the premises column, you can write native vault wikilinks such as [[2026-Database-Latency-Benchmarks]] or [[Miller-1968-Human-Response-Thresholds]].

When pasted into your note archive, your desktop Markdown editor automatically resolves these bidirectional links into an active knowledge graph. Furthermore, because the exported Markdown note contains structured YAML frontmatter (including robustness_score, premises_count, and unaddressed_objections), you can query your library of technical briefs using Dataview or shell scripts to flag decision memos that still have unresolved objections.

Audit Rules & Defect Detection

The browser engine continuously audits your argument structure against four rigorous analytical checks:

unaddressed-objection

Flags counterarguments that lack an explicit rebuttal, mitigation, or concession.

unsupported-premise

Flags premises that lack a cited source note, publication reference, or [[wikilink]].

circular-suspect

Flags premises whose wording heavily mirrors the thesis without independent evidence.

one-sided-argument

Warns when an argument outline contains zero anticipated counterarguments or objections.

Client-Side Security and Spreadsheet Formula Protection

Analytical briefs, executive memos, and private investment theses often contain proprietary strategy data. This tool executes 100% locally within your browser tab via deterministic JavaScript. No network fetch requests are dispatched, no telemetry tracks your keystrokes, and no cloud servers inspect your reasoning.

When downloading spreadsheet tables, the engine guards against CSV Formula Injection (CWE-1236). Any premise or objection starting with spreadsheet formula triggers (=, +, -, @, or tab characters) is safely single-quoted before export, preventing malicious command execution in Excel or Google Sheets.

Questions

Why should I map arguments into premises and objections instead of writing standard prose?

Unstructured prose allows confirmation bias and narrative flair to conceal unverified assumptions. By decomposing your position into discrete premises, evidence sources, and objections, you immediately identify unsupported assertions, circular logic, and unaddressed vulnerabilities before submitting your proposal for peer review.

Does this tool automatically discard or downplay objections that weaken my thesis?

Never. The core guarantee of this tool is counterargument preservation. Objections are never suppressed, hidden, or watered down. Unaddressed counterarguments are actively flagged as structural vulnerabilities, penalizing the robustness score until you provide a legitimate refutation, mitigation, or scope concession.

What is the Toulmin model and how does it apply to software architecture notes?

Philosopher Stephen Toulmin proposed that real-world arguments consist of Claims (propositions), Grounds (empirical data or benchmarks), Warrants (reasoning connecting grounds to claims), and Rebuttals (anticipated counterarguments). In Architecture Decision Records (ADRs), this maps directly to your proposed decision, supporting benchmarks, trade-offs, and risk mitigations.

Can I export the argument map into Obsidian or my local Markdown vault?

Yes. The tool outputs standard GitHub Flavored Markdown with YAML frontmatter, callout blockquotes (> [!info], > [!warning], > [!caution]), and native [[WikiLink]] references. You can also download formal syllogism tables or formula-safe CSV spreadsheets.

Are my draft arguments or proprietary company strategies sent to cloud servers?

No. The entire engine executes 100% locally inside your web browser. No network fetch calls are made, no telemetry is tracked, and no third-party AI models process your text.

Ground Your Thinking in Plain Text with Oyma

Capture private meeting records, research notes, and architectural debates without sending a single byte to third-party AI clouds.

tools argument outline builder downloadDownload for Mac

No account needed. Intel Mac build