Shipyard services

Shared browser services and isolated tasks on the worker. Use task views for process details.

Architecture, not live health. Evidence and status belong to inventory records.

Components

Connections

• Orca interface → Native coding agents: SSH task execution
• Orca interface → API task: SSH setup and archive hooks
  • mac.orca → shipyard.api_task.lifecycle: SSH setup and archive hooks
• Orca interface → Search-engine task: SSH setup and archive hooks
  • mac.orca → shipyard.appliance_task.lifecycle: SSH setup and archive hooks
• Orca interface → Display and noVNC: SSH browser access
• Native coding agents → Playwright MCP: MCP over loopback HTTP
• API task → Primary local API seed: Explicit first initialization
  • shipyard.api_task.lifecycle → shipyard.seed: Explicit first initialization
• Shared Chromium → API task: HTTP localhost 3003
  • shipyard.browser → shipyard.api_task.dashboard: HTTP localhost 3003
• Search-engine task → Shared Cargo cache: Serialized build cache
  • shipyard.appliance_task.lifecycle → shipyard.cargo: Serialized build cache
• Shared Chromium → Private browser profile: Session persistence
• Playwright MCP → Shared Chromium: CDP on loopback
• Display and noVNC → Shared Chromium: Human display and input