Build · Create · Writing & Content

Annotated story-spine beat map

I get a structured beat map where each of the book's nine narrative beats (protagonist, struggle, conflict, value prop, team, product+3-points, better-than-competition, traction+market, tagline reprise) carries its own prose block, so I can drop any beat into any channel.

You receive: A JSON object {productName, tagline, beats:[{beatId, label, prose}]} covering exactly the nine named beats in canonical order, plus a productMechanics array of exactly 3 points under the product beat.

Part of Pitch Investors

Opens soon

Cost20 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

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": [
  "requireTaglineInFinalBeat",
  "tagline"
 ],
 "checkNames": [
  "format_parses",
  "tagline_set",
  "beats_exact",
  "labels_present",
  "prose_length",
  "mechanics_count",
  "protagonist_named",
  "tagline_reprise"
 ],
 "constants": {},
 "deliverableLabel": "story_spine_beat_map",
 "documentKeys": [
  "beatId",
  "beats",
  "label",
  "product",
  "productMechanics",
  "prose",
  "protagonist",
  "tagline",
  "tagline_reprise",
  "traction_market"
 ],
 "enumLiterals": [
  [
   "protagonist",
   "struggle",
   "conflict",
   "value_proposition",
   "team",
   "product",
   "better_than_competition",
   "traction_market",
   "tagline_reprise"
  ],
  [
   "true",
   "yes",
   "1"
  ]
 ],
 "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.