Build · Create · Writing & Content
Build an Argument Structure Map
A structured argument map that exposes every logical step, making gaps and unsupported leaps reviewable before the argument is sent to stakeholders.
You receive: A JSON document with: `main_claim` (string, >=10 words); `premises` array (each: `id` (P-001 format), `statement` (string, >=8 words), `evidence` (string, >=10 words, specific data, source, or example), `evidence_type` (enum: measured_data | cited_study | analogy | expert_testimony | personal_experience | logical_deduction), `warrant` (string, >=8 words, the unstated assumption linking evidence to premise)); `counterarguments` array (each: `id` (CA-001 format), `objection` (string, >=8 words), `rebuttal` (string, >=8 words)); `argument_type` (enum: deductive | inductive | abductive); `conclusion_restated` (string, >=10 words).
Part of Pitch Investors
What's verified: STUD verifies: count floors, schema completeness, enum validity, id uniqueness, word-count floors, required evidence type coverage. STUD does NOT verify: whether the logical chain is actually valid, whether evidence actually supports the premises, whether warrants are plausible.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"required_evidence_types"
],
"checkNames": [
"format_parses",
"main_claim_length",
"conclusion_restated_length",
"argument_type_valid",
"premises_count",
"counterarguments_count",
"premise_fields_valid",
"premise_ids_unique",
"counterargument_fields_valid",
"counterargument_ids_unique",
"required_evidence_types_covered"
],
"constants": {},
"deliverableLabel": "argument_structure_map",
"documentKeys": [
"argument_type",
"conclusion_restated",
"counterarguments",
"evidence",
"evidence_type",
"id",
"main_claim",
"objection",
"premises",
"rebuttal",
"statement",
"warrant"
],
"enumLiterals": [
[
"deductive",
"inductive",
"abductive"
],
[
"measured_data",
"cited_study",
"analogy",
"expert_testimony",
"personal_experience",
"logical_deduction"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.