Skip to content
Skild Robotics Operations

Pittsburgh — Overrides

Scope

Pittsburgh-site-specific overrides and extensions to general SOPs.

Operating parameters

ParameterValue
Deployment locationPittsburgh (specific site TBD on work computer)
Operating hoursTBD
Approved zonesTBD
Current autonomy stageTBD

Most operating-parameter detail is not surfaced in available local + Drive sources. The Pittsburgh-related docs that exist (Operator Onboarding) are operator-policy material, not site-operating SOPs. Site-operating overrides need to be populated.

General SOPs modified by Pittsburgh

/training/operator-onboarding/pittsburgh/ — primary site-onboarding curriculum

  • Slack + scheduling + payment + on-shift expectations are documented (migrated from seed sites/pittsburgh/onboarding.md, status: worked).
  • Confidentiality clause from this doc applies cross-site.

/general/communications/ — confirmed channels at Pittsburgh

  • #general, #scheduling-operators, #fill-swap-shifts are confirmed Pittsburgh channels (likely org-wide too).
  • Cooper is the named escalation point for scheduling.

Note: scheduling-related operator-admin program was dropped 2026-05-18 per user signal. The Slack channels referenced above are now vestigial in /general/communications/.

What’s missing (compared to LGA)

LGA has a populated overrides.md covering operating hours, zones, autonomy stage, escort protocol, storage/retrieval, and explicit safety extensions. Pittsburgh has none of those captured in current sources.

On work computer:

  • Identify the Pittsburgh deployment location(s).
  • Capture operating hours, zones, autonomy stage.
  • Identify site coordinator / lead.
  • Document any storage / pickup / transport rules specific to Pittsburgh.

Source notes