Story
A Story is the customer narrative for one ICP, compiled from its Founding Hypothesis and Interview quotes, never written by hand.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
icp | ICP | required | The ICP it speaks to: one Story per ICP. |
hero | text | required | Who the customer is and what they want. |
problem | Problem | required | The Problem: external, internal, and the villain behind it. |
guide | text | The Startup’s empathy and authority, the authority read from Metrics and Evidence. | |
plan | text | Three steps, each naming a declared Event. | |
success | text | What the customer gains. | |
failure | text | What the customer risks without it. | |
oneLiner | string | The Story in one sentence. | |
direct | Offer | The direct call to action: an Offer that makes a Customer. | |
transitional | Funnel | The transitional call to action: a Funnel opt-in that makes a Lead. | |
from | string | required | Lineage: the slot it compiles from, as Hypothesis#<slot>@v<version>. |
stance | string | The positioning the Positioning tournament chose, graded Behavior; every compiled asset recompiles when it changes. | |
category | string | The market category name the Story claims, as answer engines repeat it. |
Object
{
"$id": "https: //api.sb/ ledgerlark.com/ stories/ story_1",
"$type": "Story",
"icp": "icp_1",
"hero": "Example hero",
"problem": "problem_1",
"guide": "Example guide",
"plan": "Example plan",
"success": "Example success",
"failure": "Example failure",
"oneLiner": "Example one liner",
"direct": "offer_1",
"transitional": "funnel_1",
"from": "Hypothesis#approach@v1",
"stance": "headToHead",
"category": "Example category"
}Relationships
- A Story is compiled from one Hypothesis: the Founding Hypothesis whose slots the Story compiles from; a pivot recompiles it.
compiledFrom, inversestories. - A Story quotes many Interviews: the Interviews whose words the Story reuses.
quotes, inversequotedIn.
Verbs
createCreates a Story.POST /{namespace}/storiesgetReturns one Story by id.GET /{namespace}/stories/{id}listReturns Stories, newest first, one page at a time.GET /{namespace}/storiesupdateChanges the given properties of a Story.PATCH /{namespace}/stories/{id}deleteDeletes a Story; its history is kept.DELETE /{namespace}/stories/{id}
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Story.create | Yes | Yes | Yes | No |
Story.get | Yes | Yes | Yes | Yes |
Story.list | Yes | Yes | Yes | Yes |
Story.update | Yes | Yes | Yes | No |
Story.delete | Yes | Yes | Yes | No |
Call it
Add a story to PatentPad with an ICP and a problem.Example
A patent-drafting Startup compiles one Story for solo inventors. The hero wants a filed patent, the villain is a $15,000 attorney bill, and the call to action is a $499 draft Offer.