Your development environment

This environment keeps the Mac as the interactive workstation and uses Shipyard for agent execution, builds, isolated application services, and a shared Linux browser. The purpose is predictable daily work with explicit ownership of processes, data and credentials.

Choose a path

• Understand it: architecture overview and interactive architecture explorer.
• Start work: API and dashboard, appliance search engine, browser and manual takeover, or a test bed run on the edge appliance.
• Explain it: five minute walkthrough.
• Recover: symptom index.
• Extend it: add a machine and contribution checklist.

Agents: read the workflow for your task, use recovery recipes when blocked, and follow the contribution checklist when changing the setup. Start with the task lifecycle to see what starts, stops and stays on disk.

Working boundaries

One dashboard preview and one browser session are shared. API and search-engine worktrees have isolated dependencies. Archiving stops task services but retains data. A shared build cache does not imply a shared running binary or database.

Normal Orca startup is configured for API and appliance on Shipyard. Browser startup after reboot is manual. Full fresh-machine reconstruction, the same agent tools and access across machines, camera-image cloud permissions and historical analytics backfills remain open. See known issues.

The home test bed, a build server with simulated cameras and an edge appliance, was added on 6 October by the agent operating it. Its measurement scripts and run records stay in the appliance repository notes; this site holds the machines, the flows between them and the recovery recipes.