Short definitions of the words that appear across the platform, the docs and the incident log.
Autonomous cloud
A hosting model in which an agent derives infrastructure from the application's code, deploys it, verifies it and operates it, rather than executing configuration a human wrote.
Repository analysis
The agent's pass over a connected repository to identify services, entry points, dependencies, runtime versions, datastores and environment variables. Its output is the plan.
Plan
The agent's statement of what it will provision and run for a repository. Reviewable with shipsanely plan before any deployment.
Service
A separately running part of an application discovered in the repository: a web frontend, an API, a background worker or a scheduled job. Each service gets its own app servers.
Release
An immutable set of build artifacts produced from a specific commit. Releases are built, provisioned, verified and then promoted.
Verification
Probes run against a new release before traffic moves to it: health endpoint, datastore connectivity, request probes against detected routes, worker liveness and migrations.
Promotion
The routing change that makes a verified release live. The previous release is kept warm for fast rollback.
Managed component
A piece of infrastructure the platform provisions and operates: app servers, PostgreSQL, Redis, hosted endpoints.
Private network
The network on which app servers reach PostgreSQL and Redis. Datastores have no public endpoint.
Incident
A detected deviation from healthy production — latency, errors, liveness or resource thresholds — with a diagnosis and, usually, a repair.
Repair
An operational action taken by the agent in response to an incident: restart, rollback, re-provision, configuration change or redeploy. Never a source-code change.
Repair policy
Per-service setting: auto-repair, repair with notification, or notify only.
Agent usage
The first pricing meter: work performed by the agent — analyses, builds and verifications, diagnoses and repairs.
Infrastructure usage
The second pricing meter: hours of managed components provisioned, at a flat rate per size.
SHIPSANELY.md
An optional plain-language file at the repository root that gives the agent hints it cannot infer: unusual entry points, build-time variables, private registries.