ABM — Overrides
Scope
ABM-pilot-specific customer-program overrides. The ABM pilot is the customer engagement under which the GO2W-26 is deployed at LGA Terminal B.
Relationship to LGA site
- LGA is the deployment site. Operating zones (CCA/CCB/Food Court), operating hours, autonomy stage, escort protocol, storage all live in /sites/lga/overrides/.
- ABM is the customer / program. Customer-facing operations manual, autonomy roadmap, and deployment-plan live here.
If a rule is about the airport / site, it lives in /sites/lga/. If a rule is about the ABM customer engagement (contract scope, autonomy roadmap, pilot KPIs, stakeholder comms), it lives here.
General SOPs modified by ABM pilot
/general/incident-response/ — extended
- ABM-specific intake form: https://docs.google.com/forms/d/1Z9JovFVgXsafhYOGOiPghLJoTvk8L7TjFtA5ZTHLYgU/edit
- ABM-specific dashboard: https://docs.google.com/spreadsheets/d/1Jcf7q1rpjy-a6FvEFSJ311vZEtRZA1WxV7sKgLzWIko/edit
- See /sites/lga/incident-response-lga/ for the full LGA workflow.
/general/communications/ — extended
- ABM-pilot Slack channel(s) — name TBD on work computer.
- ABM site coordinator handle — TBD on work computer.
- Customer-facing escalation goes through Skild management before any direct ABM notification (per universal escalation rules).
Robot autonomy-stage rules
- The ABM pilot determines the autonomy stage progression. As of Mar 31 2026: L0. Progression requires explicit Skild / ABM alignment.
[SOURCE: ABM Ops Manual §4] - All on-site behavior at the current stage (L0) is enforced via /sites/lga/overrides/.
Project artifacts
| Artifact | Owner | Source |
|---|---|---|
| ABM Operations Manual | anway@skild.ai (maintainers: Anway, Robert Belle-Isle, Laura Kasimatis, Jimit Gandhi) | https://docs.google.com/document/d/1mSJ8zEmercxNjWOYGTjA-eZUKJ8hk1EQ9jsyYjkSGEs/edit |
| Skild/ABM Autonomy Plan | laura@skild.ai | https://docs.google.com/spreadsheets/d/1uzv5FlkerCnvFMzT8ocNNnswA-mlPJmc4xjjPHZ6aCM/edit |
| Notes — ABM (LGA) Weekly Ops Review | laura@skild.ai | https://docs.google.com/document/d/1X4E08kKTpSxF3QtsERETF9adJ4tEyyyM-08LR0cKLlE/edit |
| ABM Pilot Deployment | anway@skild.ai | https://docs.google.com/spreadsheets/d/1-lhvtLtTodG_itlX8Go9eXh7rm1IvXdlcxDvmgzVzUc/edit |
| Incident report intake | tylerkugima@gmail.com (form admin) | https://docs.google.com/forms/d/1Z9JovFVgXsafhYOGOiPghLJoTvk8L7TjFtA5ZTHLYgU/edit |
| Operator field SOP (April 2026) | Tyler Kugima | raw-index/sources/GO2_Standard_Operating_Procedure_ABM.docx |
Why this SOP is draft
- The ABM-pilot project boundaries (start date, contracted scope, KPIs, stakeholders, success criteria) are not surfaced in available local + Drive material — most likely live in contract docs and/or Linear.
- Pending: contracted scope / SoW, pilot KPIs, stakeholders by role, escalation tree for customer-visible issues.
Source notes
[SOURCE: ABM Operations Manual.docx]Mar 31, 2026 (local extract).[SOURCE: GO2_Standard_Operating_Procedure_ABM.docx](April 2026, Tyler Kugima) §II Scope.[INFERRED]— project-boundary detail not in available sources.