Commercial Territory
This document is a public map of application areas for the SIBurst identity. It describes where the concept naturally applies. It is not a business plan, and it names no organizations.
The organizing question
Different systems. One underlying question: what changes when capability crosses into a different operating regime?
Every territory below is a different relationship to that question. The four
functions follow the structure of the thesis in FOUNDATION_THESIS.md: capability
must be built, it acts, it is measured, and at some point it may cross.
The four functions
BUILD — the capacity that accumulates
- compute
- training infrastructure
- inference
- orchestration
Build is where capability accumulates. Its relevance to SIBurst lies in the point at which infrastructure must be redesigned rather than scaled, because the systems it serves now operate differently.
ACT — capability that operates in environments
- agents
- autonomous systems
- embodied systems
- machine action
Act is where capability stops producing outputs for someone and starts taking actions within an environment. That shift is one of the clearest candidate thresholds in the framework.
MEASURE — knowing which regime a system is in
- evaluation
- observability
- capability monitoring
- transition detection
Measure asks not only "how well does it perform?" but "has what it can do changed in kind?" Transition detection is the function most specific to SIBurst: it exists only if regimes can change.
CROSS — the transition itself
- thresholds
- regime transition
- deployment into a new operational class
Cross is the territory the name describes most directly. Here the subject is not a component but the crossing: preparing for it, recognizing it, and governing what follows it.
Forms of identity
SIBurst can function as any of the following. They are listed, not ranked.
| Form | What the name would identify |
|---|---|
| Company identity | An organization whose purpose is organized around capability transitions. |
| Platform identity | A system on which others build, run, or observe capability that may change regime. |
| Infrastructure identity | A layer — compute, orchestration, monitoring — designed for systems before and after a threshold. |
| Research-program identity | A body of inquiry into thresholds, discontinuity, and regime change in intelligence. |
| Category identity | A name for the category of work concerned with the transition itself. |
Relationship to the boundary
These territories are natural application areas, not limits on the identity
(see DECISION_LOG.md, DEC-008). Any use inside or outside them is still
subject to the boundary test in CATEGORY_BOUNDARY.md, and any public claim
made under the name is subject to PUBLIC_CLAIM_POLICY.md.