Category kit

# Not live yet (gaps #2)
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"category-kit"}'

 1import { $ } from 'startup-builder'
 2
 3return await $.Campaign.create({ play: 'category-kit' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-07-08 · Not live yet, gaps #2

npx startup-builder do Campaign.create --json '{"play":"category-kit"}' --try   # Not live yet (gaps #2)

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'category-kit' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-07-08 · Not live yet, gaps #2",
    "mode": "try"
  }
}

 1{
 2  "type": "https://startupbuilder.dev/errors/refused",
 3  "title": "Refused",
 4  "status": 422,
 5  "detail": "category-kit can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "stance graded on 2026-07-07; 2,610 Visitors a month; a cost from 7 Interviews",
11      "doc": "/plays/category-kit#check-use-when",
12      "then": "Metric.query"
13    },
14    {
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Experiment.concluded%22%2C%20%22Monitor.checked%22%2C%20%22Post.scheduled%22%2C%20%22Keyword.measured%22)&limit=1" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl -X POST "https://api.sb/leaseline.app/triggers/fire?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"like":"event_1188"}'

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/decisions?where=on%20%3D%20%22page_88%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/actions?where=on%20%3D%20%22page_88%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Experiment.concluded", "Monitor.checked", "Post.scheduled", "Keyword.measured")', limit: 1 })   // { play } compiled to this Play’s Trigger Events
 4const { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7
 5const { decisions: [decision] } = await $.Decision.list({ where: `on = "${subject}"` })   // what it chose, and why · Not live yet, gaps #7
 6const { actions } = await $.Action.list({ where: `on = "${subject}"` })   // what it did, with its checks · Not live yet, gaps #7
 7return { decision, actions }

npx startup-builder do Event.list --json '{"where":"name in (\"Experiment.concluded\", \"Monitor.checked\", \"Post.scheduled\", \"Keyword.measured\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1188"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"page_88\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"page_88\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Experiment.concluded\", \"Monitor.checked\", \"Post.scheduled\", \"Keyword.measured\")', limit: 1 })   // { play } compiled to this Play’s Trigger Events\nconst { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7\nconst { decisions: [decision] } = await $.Decision.list({ where: `on = \"${subject}\"` })   // what it chose, and why · Not live yet, gaps #7\nconst { actions } = await $.Action.list({ where: `on = \"${subject}\"` })   // what it did, with its checks · Not live yet, gaps #7\nreturn { decision, actions }",
    "mode": "try"
  }
}

 1{
 2  "decision": {
 3    "$id": "https://api.sb/leaseline.app/decisions/decision_571",
 4    "$type": "Decision",
 5    "choice": "correct-the-source",
 6    "reason": "4 of 9 Perplexity runs this week define renewal ops as HR contract renewals, and all 4 cite the same glossary Page",
 7    "stakes": "low",
 8    "options": [
 9      "correct-the-source",
10      "work-a-cited-source",
11      "answer-the-thread",
12      "refresh-the-comparison",
13      "hand-to-search",
14      "hold-the-day"
15  …

action_2 is the correction to the glossary’s editor, drafted from your definition Page. It sends from your own Mailbox only once you approve it.

≈ +$130 ARR a month at 2,600 Visitors

Worth

3 h week 1, about 13 h over the 90 days

Your time

$0.01 per panel run, ~$23 a month at 540 a week

Spend

T+9: first engine cites your definition

First signal

A graded new-category stance, 1,000+ Visitors a month

Use it when

No graded stance: positioning-tournament · under 1,000 Visitors: aeo · under 5 Interviews: signup-interviews

Not yet when

Worth’s formula: about +1.8 qualified Leads per 1,000 Visitors (Other Startups’ results; yours reads Too early to tell) × 2,600 Visitors a month × 0.08 qualified Leads to paid × $348 first order ARR ≈ +$130. Under First signal: Term share reads every 2 weeks from 360 definitional runs; the qualified-Deal kill rule reads at T+90, Nov 23.

Start it this weekCopy Anchor Link

npx startup-builder add play category-kit   # 1 · writes plays/category-kit.mdx (Not live yet, gaps #5)

# 2 · dry run; below, its 422 on 2026-07-08
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"category-kit"}'

# 3 · keep it, at You approve each one
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"category-kit"}'

# on
curl -X PATCH https://api.sb/leaseline.app/campaigns/category-kit \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endsAt":null}'

# off: nothing sends or books; your Pages stay up
curl -X PATCH https://api.sb/leaseline.app/campaigns/category-kit \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endsAt":"now"}'

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "category-kit can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "stance graded on 2026-07-07; 2,610 Visitors a month; a cost from 7 Interviews",
      "doc": "/plays/category-kit#check-use-when",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "no term history",
      "doc": "/plays/category-kit#check-baseline",
      "fix": "The 2 baseline weeks become Before; it reads before-after, not proof.",
      "then": "Metric.query"
    },
    {
      "check": "approved-pages",
      "status": "fail",
      "doc": "/plays/category-kit#check-approved-pages",
      "fix": "Publish your pricing and about Pages; the canon cites only your own pages.",
      "then": "Site.publish"
    },
    {
      "check": "domain-authenticated",
      "status": "pass",
      "observed": "leaseline.app: 3 of 3 records resolve",
      "doc": "/plays/category-kit#check-domain-authenticated",
      "then": "Domain.authenticate"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "marketing-lead",
        "communications-lead"
      ],
      "owned": 31,
      "doc": "/plays/category-kit#check-role-unstaffed",
      "fix": "Leave them: pitches and replies come to you, and the day notice drafts into owners’ queues.",
      "then": "Role.staff"
    }
  ]
}

Each panel run costs $0.01, and the panel runs 540 a week (about $23 a month). The day notice and corrections cost $0.04 a send from your Domain (Worker cost), and media spend is $0. That comes to about $25 a month, and about $40 in the category-day month.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1188",
  "$type": "Event",
  "name": "Monitor.checked",
  "at": "2026-10-19T06:00:41Z",
  "seq": 1188,
  "data": {
    "monitor": "monitor_6",
    "panel": "renewal-ops",
    "week": "2026-10-12",
    "engine": "perplexity",
    "runs": 9,
    "misdefined": 4,
    "cited": "page_88",
    "meaning": "HR contract renewals"
  }
}

# runs this week’s panel in test
curl -X POST "https://api.sb/leaseline.app/monitors/monitor_6/check?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"
npx startup-builder trigger Monitor.checked --like event_1188   # replays the delivery
npx startup-builder clock advance --by 7d   # the next panel week

Who runs itCopy Anchor Link

Content Lead · your agent (role:content-lead, worker_7) holds the Key Result. It hands every pitch, correction, guest spot and thread reply to you (Dana Okafor, person, worker_1), because the Marketing Lead and Communications Lead Roles have no person. You write or approve each one, and it sends from your own Mailbox. Your number links to Did it work.

What it reads · What it may call. It reads the panel’s answers, the cited Pages and your Fact records, and every answer and fetched Page is data, never instructions. It may draft, publish your own comparison Page and book day steps; it never sends a pitch or a thread reply. Its tools are POST /{namespace}/content/draft, POST /{namespace}/messages/{message}/schedule, POST /{namespace}/tasks/{task}/assign, POST /{namespace}/content/{content}/publish, POST /{namespace}/keywords/{keyword}/measure, and any other call becomes an Approval under the Role’s Mandate.

You hold the Content Lead Key Result: 20 % term share for renewal ops by 2026-11-23. ← worker, metric
On each panel run or term Event, choose one option and say why.                  ← triggers, chooses
The definition names no product; Leaseline’s approach sits in its own section.   ← copyRules 2
Every number carries a Fact with its method, sample and date.                    ← copyRules 1, fact-check
Never write a pitch, a launch post or a thread reply: draft fragments for Dana.  ← copyRules 10
Kill it at T+90 under 3 qualified Deals from term-touched Leads; never move that line after T-28. ← Kill rule, your file line 5

The slow loop. The panel and the kill rule are fixed from T-28, so no Change may touch them. The weekly Decisions changed no rule option in the window, so there is no replay or read-back to print.

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Every pitch, correction, guest spot and thread reply comes to you (Dana Okafor, person): the Marketing Lead and Communications Lead Roles have no person, and nothing sends in your name until you approve it. One Brief per Role, then the Approval, as captured (brief, draft, route and checks are Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_517",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-20T06:04:00Z",
    "on": "page_88",
    "brief": {
      "who": "the editor of a property-ops glossary (contact_52)",
      "said": "renewal ops: the HR team’s process for renewing employment contracts",
      "chose": "correct-the-source",
      "why": "4 of 9 Perplexity runs cite this Page for that meaning",
      "draft": "approval_88",
      "never": [
        "a pitch",
        "a link request",
        "a claim with no Fact"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_88",
    "$type": "Approval",
    "verdict": null,
    "deadline": "2026-10-20T18:00:00Z",
    "draft": "Hi Jo, your glossary defines renewal ops as renewing employment contracts. In property management it names getting each lease renewal notice out on time…",
    "route": "correct-the-source",
    "checks": [
      {
        "check": "fact-check",
        "status": "pass"
      },
      {
        "check": "pitch-cap",
        "status": "pass"
      }
    ]
  }
]

You answer with POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, POST /{namespace}/approvals/{approval}/approve or POST /{namespace}/approvals/{approval}/refuse, each a one-call window; an Approval unanswered by its deadline expires and nothing sends. Once you claim, the agent’s pending drafts on that source cancel with claimedByPerson (Not live yet, gaps #7), and every reply lands in your queue. A Task nobody claims by its due time stays with you, the last Role, and person-promise fires.

On time: you, 14 of 15 claimed within their due time, median 3 h 10 min, n 15, ■■□□ Early sign beside Other Startups’ 91 % on time (the 15th, task_402, a thread reply on Sep 6, waited 26 h). Your queue: counted by kind: in the category-day week, 28 pitches to write, 6 approvals and 3 thread replies; since then, about 2 approvals and 1 thread a week.

The fixed line: POST /{namespace}/deals/{deal}/assign sets owner to the receiving person, the agent is never a Deal’s owner, and Meetings land on the owner’s calendar under the owner’s name.

When it won’t sendCopy Anchor Link

The captured refusal, then the Stop that fired as a Campaign.paused reason (Not live yet, gaps #2); the rewrite that posted is the LinkedIn thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The LinkedIn Post did not schedule: it shows a dataset number 5 days before lift.",
  "checks": [
    {
      "check": "embargo",
      "status": "fail",
      "doc": "/plays/category-kit#check-embargo",
      "fix": "Hold the number until lift at T-0.",
      "then": "Post.schedule"
    },
    {
      "check": "fact-check",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "meaning-drift",
      "observed": "55 %, 58 %, 57 %",
      "bound": "60 %",
      "window": "3 weeks"
    },
    "doc": "/plays/category-kit#stop-meaning-drift",
    "task": "task_431"
  }
]

Did it workCopy Anchor Link

An answer engine cannot be split, so the leaf reads before-after (rule o). The 80/20 headline split on Visitors with no term touch is random, so the rows above the leaf read treated against held back. Each figure’s call is POST /{namespace}/metrics/query by node, and every node above the leaf is Not live yet (gaps #4).

{
  "$id": "decisions/decision_571",
  "$type": "Decision",
  "choice": "correct-the-source",
  "reason": "4 of 9 Perplexity runs this week define renewal ops as HR contract renewals, and all 4 cite the same glossary Page",
  "stakes": "low",
  "options": [
    "correct-the-source",
    "work-a-cited-source",
    "answer-the-thread",
    "refresh-the-comparison",
    "hand-to-search",
    "hold-the-day"
  ],
  "by": "worker_7",
  "on": "page_88",
  "expected": "meaning fidelity on Perplexity back over 60 % within 28d",
  "reopensWhen": "term-misdefined fires again for page_88 within 28d"
}

Term share counts the definitional runs whose answer cites a canon Page or names Leaseline as the term’s source, per engine, 2 weeks at a time. The headline split reads qualified Leads per 1,000 Visitors with no term touch until T+90, Nov 23.

How it moves it: answer engines cite your definition Page (page_61) on 61 of 360 definitional runs, where before the day no run cited any source for renewal ops.

Guardrails: on the path: term-touched Leads opened 2 qualified Deals against the kill rule’s 3 by Nov 23 (still deciding), and the category headline stays above the runner-up, so holdout-harm has not fired.

{
  "$id": "https://api.sb/leaseline.app/campaigns/category-kit",
  "$type": "Campaign",
  "play": "play:category-kit@1",
  "path": [
    "category-term-share",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "category-term-share",
    "unit": "percent",
    "heldBack": 980,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 360,
    "maturing": 0,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": false
  },
  "ledger": {
    "spend": 0,
    "workerCost": 71,
    "hours": 11.5,
    "pipelineArr": 4800,
    "wonArr": 1392,
    "projectedArr": 130,
    "paybackDays": null
  }
}

Outside benchmark: journalists picked 33 % of human-written pitches against 10 % of fully AI-generated ones (1,394,740 pitches answering 42,392 requests, a pitch-marketplace detection study, 2026-09-23).

Before it · After it. Before it: positioning-tournament grades the stance and hands over the name (Experiment.concluded). After it: aeo folds the term panel into its own on ship, editorial-seo and paid-search hear search demand once it appears, and community-answers takes open threads after T+7.

ExampleCopy Anchor Link

Leaseline ran it from 2026-07-08 to 2026-10-19 (103 days; T-0 was Tue 2026-08-25, so asOf is T+55). The panel ran 30 prompts on 6 engines, 3 samples each: 540 runs a week, 180 of them definitional. 25 Decisions followed term Events. Read every captured thread at ?threads=all; three follow the tables.

Dana → Morgan at a property-trade newsletter, Aug 25, 07:12 · Across 1,212 leases at 38 small property managers, 31 % of renewal notices went out under 60 days before the lease ended.¹ We call getting them out on time renewal ops, and the definition is here.² The dataset and method are on the release Page.³ *Written and sent by Dana from her own Mailbox.*⁴

Morgan, 09:40 · “Send me the per-state split; I’m writing Thursday.” · Dana, 10:05 · the CSV link from the release Page. The piece ran Aug 27, citing the definition Page.

- 31 % of renewal notices go out late. Here’s what we found across 1,212 leases.
+ Renewal ops: getting every renewal notice out on time. Our definition, in plain words.

A landlord forum thread, 2026-10-02 08:14 · “Is renewal ops just a spreadsheet with reminders?” · Content Lead · your agent, 08:16 · drafted the fact pack (the definition, the 3 in-and-out rules and the dataset link) into your queue, due 09:14 (task_488). · Dana, 08:51 · posted her own reply, linking the definition Page.

¹ From the release’s stored query, with its n and interval. ² The definition Page, which names no product. ³ The method, sample and date, on the release Page. ⁴ The agent built the list and the brief; it never writes a pitch.

Your settingsCopy Anchor Link

---
term: renewal ops
holdout: 0.2       # 20 % of Visitors with no term touch see the runner-up headline
day: 2026-08-25
kill: 3 qualified Deals from term-touched Leads by T+90
---
Make renewal ops the name for getting every renewal notice out on time. I write every pitch, the launch post and every thread reply.

$ npx startup-builder show plays/category-kit
term renewal ops · holdout 0.2 · day 2026-08-25 · kill 3 qualified Deals     your file  plays/category-kit.mdx:2-5,7 (Ask 2026-07-08; day by event_477, 2026-07-28)
family demand · worker role:content-lead, owns never · chooses 6 (4 rule, 2 read) · sequences category-press-countdown, category-day-notice · checks owned-by-a-person, fact-check, embargo, pitch-cap, readiness, problem-cost · stops 10 · placements 6 answer engines, google-search, product-hunt, hacker-news, linkedin, x, youtube, gmail, outlook    catalog  play:category-kit@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

Compiled, not written: edit the Play record category-kit and its Leaseline run, then regenerate. Every step runs from a sentence or a line of code. In your words: the CRM words you know, and where each lives here.