Repositories
Repositories holds a Startup’s code and definitions in db.sb, with branches, Changes, checks and Versions.
db.sb is always the record: a GitHub repository mirrors it, or sends its edits back as Changes.
Summary
| Part | This System |
|---|---|
| Group | Moves to Code |
| Status | Live |
| Shelf | Front: offered from a Startup’s first days |
You can ask:
- “Ship my changes”
- “Undo the last deploy”
- “Review this change before it merges”
What you get
| Part | This System |
|---|---|
| Starts | On for every Startup at creation, with nothing to install. |
| Built from | Database, Functions, Event streams |
Nouns it owns
| Noun | Definition |
|---|---|
| Change | A Change is a proposed set of writes to definitions, previewed on its own branch, checked, approved, and merged as one unit. |
| Version | A Version is an immutable build of a definition at a fingerprint; an Order keeps the Offer Version it bought. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Change.review | Change | None | Change.reviewed |
| Change.merge | Change | None | Change.merged |
| Change.revert | Change | None | Change.reverted |
| Version.deploy | Version | Asks first | Version.deployed |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Change.reviewed | By Change.review |
| Emits | Change.merged | By Change.merge |
| Emits | Change.reverted | By Change.revert |
| Emits | Version.deployed | By Version.deploy |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Engineering Lead |
| Team | Engineering Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Reliability Engineer, Quality Lead |
Approvals and limits
| Verb | Rule | Detail |
|---|---|---|
| Version.deploy | A person says yes first | None. |
| Version.deploy | Limit for the Engineering Lead | 20 calls per day |
| Change.merge | Mandate ship for the Engineering Lead | Merges passing Changes and reverts failing ones without asking. |
| Change.revert | Mandate ship for the Engineering Lead | Merges passing Changes and reverts failing ones without asking. |
Processes that use it
| Process | How it uses it |
|---|---|
| Iteration | A Workflow writes Change |
| Shipping | A Workflow writes Change |
| Release | A step calls Change.merge |
| Incident response | A step calls Change.revert |
| Verification | A step calls Change.review |
| Vulnerability disclosure | A Workflow writes Change |
| Barrier reports | A Workflow writes Change |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Engineering Lead’s view | The Metrics its accountable Role answers for. | Change lead time |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (9) |
admin | Every Verb (9) |
member | Every Verb (9) |
viewer | Read only (4 of 9) |
Import and export
| Connector | Mode |
|---|---|
| GitHub | Mirror: the db.sb record leads and the tool reflects it. |
| GitHub | Import: edits made in the tool arrive as Changes. |
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Live |
Compliance notes
Controls it carries:
- Log completeness
- Vulnerability management
- Deploy reconciliation
- Append-only records
- Change approval
- Point-in-time recovery
- Processing definitions
Related Systems
None.
Example
An Agent as a Service for outbound sales keeps its prompts, Skills and code in one repository. A developer edits a prompt in GitHub; the edit arrives as a Change, passes its Evals, and merges. Deploying it creates a new Version, and the previous one stays one step away.