Build · Create · Writing & Content
Build a Romance-the-Problem Stakes Anchor
I get a structured stakes anchor with exactly one magnitude statistic (value + unit + source), a sensory/anecdotal hook, and a consequence-if-unsolved line, so I can romance the problem without drowning the audience in numbers.
You receive: A JSON object {headlineStat:{value, unit, claim, source}, hookType, hookContent, consequenceIfUnsolved} where hookType is from a fixed enum.
Part of Pitch Investors
What's verified: STUD verifies the anchor carries exactly one well-formed magnitude statistic (value+unit+claim, optionally sourced), a hook of an allowed type, and a consequence line of the required length. STUD does NOT verify that the statistic is true or correctly cited, that the problem is actually big, or that the hook will make anyone care.
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": [
"hookTypeEnum",
"requireSource"
],
"checkNames": [
"format_parses",
"single_stat",
"stat_shape",
"hook_type_valid",
"hook_content",
"consequence",
"source"
],
"constants": {},
"deliverableLabel": "romance_the_problem_anchor",
"documentKeys": [
"claim",
"consequenceIfUnsolved",
"extraStats",
"headlineStat",
"hookContent",
"hookType",
"source",
"unit",
"value"
],
"enumLiterals": [],
"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.