# Engineering

URL: /agents/engineering · Id: `team:engineering`

> The Engineering Team builds and runs every Product: it implements Nouns and Verbs, ships Changes behind replay, and keeps every Interface up.

The Engineering Team builds and runs every [Product](/business/nouns/product): it implements [Nouns](/business/nouns/noun) and [Verbs](/business/nouns/verb), ships [Changes](/business/nouns/change) behind replay, and keeps every [Interface](/business/nouns/interface) up. [Agents](/business/nouns/agent) fill its five seats from the first day.

## What it owns
- Delivery: Change, [Version](/business/nouns/version), [Workflow](/business/nouns/workflow), [Trigger](/business/nouns/trigger), [Function](/business/nouns/function).
- What callers reach: Interface, [App](/business/nouns/app), [System](/business/nouns/system), [Tool](/business/nouns/tool), [Watch](/business/nouns/watch).
- Wiring: [Integration](/business/nouns/integration), [Domain](/business/nouns/domain), [Setting](/business/nouns/setting), [Tenant](/business/nouns/tenant), [File](/business/nouns/file).

## How it runs
The Engineering Team wakes when [Define a Product](/workflows/processes/product-definition/define-product) hands over its first definition. Until then, a [Startup](/business/nouns/startup) runs on what its [Product Template](/business/nouns/product-template) and inherited Systems provide.

Work arrives as Changes, one [Issue](/business/nouns/issue) a day from the [Product Lead](/agents/product/product-lead). When a Change passes its verdict, [Release a change](/workflows/processes/release/release-change) merges it into a new Version. It deploys to 1%, 10%, 50%, then all traffic, and a guardrail breach at any step reverts it.

An [Incident](/business/nouns/incident) starts [Resolve an incident](/workflows/processes/incident-response/resolve-incident): the status page within 5 minutes, service restored first, the cause fixed second. A new Startup starts [Connect providers](/systems/integrations/provider-wiring/connect-providers), which wires and tests the default upstream for every [Capability](/business/nouns/capability) it uses.

Every night the [Access review](/workflows/processes/security/access-review) removes [Permissions](/business/nouns/permission) unused for 30 days and rotates secrets older than 90. A widening without a [Decision](/business/nouns/decision) is refused.

Code and definitions live in Repositories, in [db.sb](/code/platform/db-sb). Every Verb ships on the API, CLI, MCP and SDK at once, so no Interface lags another.

The Product Lead decides what to build; the [Engineering Lead](/agents/engineering/engineering-lead) decides how. Each [Role](/business/nouns/role) is a seat, filled by the default role [Agent](/business/nouns/agent), another Agent or a [Human](/business/nouns/human).

## Roles
| Role | Definition |
| --- | --- |
| [Engineering Lead](/agents/engineering/engineering-lead) | The Engineering Lead builds and runs the Startup’s Products: it implements each Change, deploys it behind replay, and owns uptime of every Interface. |
| [Reliability Engineer](/agents/engineering/reliability-engineer) | The Reliability Engineer keeps every Interface up: it reads monitors, restores the Interface when an incident opens, and fixes the cause. |
| [Integration Engineer](/agents/engineering/integration-engineer) | The Integration Engineer connects each Startup to its providers and imports, and keeps every sync healthy. |
| [Security Engineer](/agents/engineering/security-engineer) | The Security Engineer protects identity, secrets, and access: unused Permissions decay nightly, and it refuses any unrecorded widening. |
| [Data Engineer](/agents/engineering/data-engineer) | The Data Engineer sources, licenses, and refreshes the Datasets a Startup sells, and keeps their quality measured. |

## Processes
| Process | Accountable | Workflows |
| --- | --- | --- |
| [Release](/workflows/processes/release) | [Engineering Lead](/agents/engineering/engineering-lead) | [Release a change](/workflows/processes/release/release-change) |
| [Incident response](/workflows/processes/incident-response) | [Reliability Engineer](/agents/engineering/reliability-engineer) | [Resolve an incident](/workflows/processes/incident-response/resolve-incident) |
| [Provider wiring](/systems/integrations/provider-wiring) | [Engineering Lead](/agents/engineering/engineering-lead) | [Connect providers](/systems/integrations/provider-wiring/connect-providers) |
| [Security](/workflows/processes/security) | [Engineering Lead](/agents/engineering/engineering-lead) | [Access review](/workflows/processes/security/access-review) |
| [Vulnerability disclosure](/workflows/processes/vulnerability-disclosure) | [Security Engineer](/agents/engineering/security-engineer) | Run by its Roles |
| [Continuity](/workflows/processes/continuity) | [Reliability Engineer](/agents/engineering/reliability-engineer) | Run by its Roles |

## Plays
None.

## Metrics
| Metric | Definition |
| --- | --- |
| Uptime | Share of minutes in a month that each Interface answers correctly. |
| Deploy frequency | Versions deployed to production per day. |
| Change failure rate | Share of deployed Changes that are reverted or cause an incident. |
| Time to restore | Median minutes from an incident opening to service restored. |
| P95 latency | The 95th-percentile response time of each Interface, in milliseconds. |
| <a id="restore-drills-passed"></a>Restore drills passed | Restore drills passed is the share of restore drills that met both recovery objectives. Owner: [Reliability Engineer](/agents/engineering/reliability-engineer). |
| <a id="change-lead-time"></a>Change lead time | Change lead time is the hours from a Change opening to its deploy. Owner: [Engineering Lead](/agents/engineering/engineering-lead). |
| <a id="sync-success-rate"></a>Sync success rate | Sync success rate is the share of Integration syncs that finish without an error on the first attempt. Owner: [Integration Engineer](/agents/engineering/integration-engineer). |
| <a id="unused-permissions"></a>Unused Permissions | Unused Permissions counts the Permissions still granted that no Worker has called in 30 days. Owner: [Security Engineer](/agents/engineering/security-engineer). |
| <a id="dataset-freshness"></a>Dataset freshness | Dataset freshness is the share of Datasets refreshed on their promised schedule. Owner: [Data Engineer](/agents/engineering/data-engineer). |

## Works with
- [Legal Team](/agents/legal)
- [Operations Team](/agents/operations)
- [Product Team](/agents/product)
- [Quality Team](/agents/quality)