Identity and structure
What counts as one Startup, how it differs from its Idea, Brand, Company, Studio, and Portfolio, and the two trees it sits in.
A Startup is the smallest business that can be moved, promoted, or sold on its own, together with its Customers. Everything else that names it answers a different question and keeps its own record.
The boundary test
Ask one question: could this be sold with its Customers, as a unit, without tearing anything? If yes, it is one Startup. If two parts would have to be split first, they are two.
permitpulse.dev sells general contractors two things. One is a Dataset of every building permit filed in their county. The other is an Agent that prepares and files the contractor's own permit applications.
Both Products serve the same contractors and share one P&L, so permitpulse.dev is one Startup. Now suppose the same team sells permit histories to property insurers under the same name. Different Customers, different economics, a separate sale: that is a second Startup sharing a Brand.
The reverse holds too. permitpulse.dev, api.permitpulse.dev, and a regional alias are three Domains for one Startup. Count Startups by the boundary test, never by Domains, Brands, or repositories.
Six records, six questions
Six records surround a Startup. Each answers one question, and none stands in for another.
| Record | Question it answers | For permitpulse.dev |
|---|---|---|
| Idea | What is pursued? | Permits that file themselves |
| Startup | Which business serves and earns? | permitpulse.dev |
| Brand | How are its Offers presented? | Its name, voice, logo, and colors |
| Studio | Who builds and directs it? | The Studio that minted it |
| Company | Who holds its rights and signs? | The Studio's holding Company |
| Portfolio | Where do attention and money go? | The Studio's construction Portfolio |
Each edit touches one record. A rebrand changes the Brand, and no second Startup appears. A move to a new Company changes the legal holder, and a new Domain adds an address, so history stays legible.
Two trees
A Startup sits in two trees at once, and they answer different questions.
The operating tree runs Studio, Portfolio, Startup, Product. Direction flows down it, and so do Settings: each record inherits a Setting from its nearest holder unless it sets its own. The Studio sets a 14-day refund window; permitpulse.dev inherits it, and its filing Agent overrides it with 7 days.
The legal tree runs from Company to Startup. The Company signs Agreements, owns the equity, and holds the profit rights.
The trees move independently. When permitpulse.dev moves to a Company of its own, its operating parent, Settings, Domains, and Customers stay where they were. A Company officer who signs a lease gains no operating Permission, and the Agent that files permits owns nothing.
An Idea outlives its Startups
An Idea exists apart from any Startup that pursues it. The Studio often mints three to five sibling Startups for one Idea, each a variant with its own ICP, approach, and Brand. The siblings run as one Experiment, judged on deposits from outside Customers.
"Permits that file themselves" spawned two siblings: permitpulse.dev for general contractors and a second Startup for rooftop solar installers. Installers filed more often but paid less per filing, so the Studio kept funding both and let the numbers decide.
A variant that loses goes Dormant. Nothing is deleted, and the Idea keeps every piece of Evidence for the next attempt.
Built from templates
Every Startup extends a Startup Template. A Startup Template combines an operating model, one or more Product Templates, and a Motion for each Offer.
permitpulse.dev runs the Autonomous operating model, with no Humans in its Roles. Its Products extend the Dataset API and Agent as a Service Product Templates. Both Offers sell b2b.
The Startup overrides a default only where it differs. An improved default in the Startup Template reaches every Startup that has not overridden it.
The definition is data
Every record in this chapter lives in the Startup's namespace on api.sb. Humans and Agents read and write it through the same Verbs.
Every edit is a Change, previewed and merged as one unit. Every choice is a Decision that records its options and its reason.
That is what makes a Startup operable by someone new. An operator, Human or Agent, reads the definition and knows who is served, who holds what, and who decides next.
Next
Customers and hypothesis: whom the Startup serves, and the belief it sets out to prove.