Skip to content

Deployment Template

Use at /deployments/<program>/_overrides.md and /deployments/<program>/operations-manual.md. Deployment pages capture customer/contract context — sites, autonomy stage, escalation contacts, KPIs, completion criteria.

---
title: <Deployment Name>
status: stub
applies_to:
- deployment:<slug>
audience:
- deployment_lead
- manager
visibility: restricted_ops
approval_status: draft
owner: TBD
last_source_check: TBD
related_dashboards: []
related_sops: []
related_issue_forms: []
related_kpis: []
escalation_path: []
known_gaps: []
---

Required body sections

Customer / partner

Customer organization, primary contact, contractual scope.

Sites

Physical sites where this deployment runs. Link to /sites/<site>/.

Robot(s)

Which robots in scope. Link to /robots/<robot>/.

Autonomy stage

Current stage (L0–L3 for GO2; analogous ladder for Vega when defined). What gates progression.

Operating hours / windows

Site-specific time windows.

KPIs / completion criteria

What “done” looks like for a route run. Link to /dashboards/<robot>/deployment-kpis/.

Escalation contacts

Customer site coordinator, designated escort, Skild on-call. Slack channel.

Issue reporting

Which form/dashboard this deployment uses. Link to /apps-and-tools/issue-reporting/.

Source notes

Cite the operations manual + any contractual / SLA documents.