Skip to content

by Startups.Studio

Growth Hypothesis

Hypothesis.drop

POST /{namespace}/hypotheses/{hypothesis}/drop

Drop retires a Hypothesis from active work and keeps it, with its Evidence, on record.

Noun: Hypothesis
Mode: do
Event: Hypothesis.dropped

You, to your agent

Drop the latest hypothesis.

curl -X POST https://api.sb/shiftnote.app/hypotheses/hypothesis_1/drop \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"reason":"Example reason"}'

import { $ } from 'startup-builder'

const hypothesis = await $.Hypothesis.drop({ hypothesis: 'hypothesis_1', reason: 'Example reason' })

npx startup-builder do Hypothesis.drop --json '{"hypothesis":"hypothesis_1","reason":"Example reason"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Hypothesis.drop({ hypothesis: 'hypothesis_1', reason: 'Example reason' })"
  }
}

Inputs

Input	Type	Required	Description
`hypothesis`	Hypothesis	required	The Hypothesis to retire.
`reason`	`text`	required	Why it is dropped.

Outputs

Output	Type	Required	Description
`hypothesis`	Hypothesis	required	The dropped Hypothesis.

Effects

Emits Hypothesis.dropped.
Performed by the Strategist.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Hypothesis.drop
The record is not in a state that allows this Verb, so the call is refused.	`refused`	Read the record, run the Verb that moves it to an allowed state, then retry.	Hypothesis.drop

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Hypothesis.create

Previous Page

Hypothesis.get

Next Page