Life of a development task

Orca creates the checkout and runs the configured setup hook on Shipyard. The agent starts after the hook reports readiness. The application workflows contain the commands; this page shows their order and data boundaries.

API, with an optional dashboard

1. CreateOrca creates an API worktree on Shipyard and runs its setup hook.
2. PrepareSerialized setup installs dependencies, initializes isolated services from the local seed and reconciles authorization.
3. WorkThe API runs through its normal development command. The agent can add a dashboard checkout in the same session.
4. VerifyCheck the API directly, then test the affected behavior in the shared Linux browser.
5. ArchiveThe hook stops task services, retains volumes and moves the dashboard companion outside the API checkout.

The primary local seed is shared input; each API task has its own database and services. Restart preserves task data. Reseeding is a separate operation. Only one managed dashboard preview and one browser session run at a time, so coordinate before taking either over.

Follow API and dashboard, browser control and archive recovery. Use Orca’s desktop Delete flow for the configured archive hook; the recorded CLI version cannot run the remote hook.

Appliance search engine

1. CreateOrca creates an appliance worktree and invokes its adapter.
2. BuildCargo uses a shared, locked cache and four jobs; the task gets its own executable.
3. Work and testRuntime and test stacks are separate. Rebuild to apply Rust changes; a failed build preserves the running executable.
4. ArchiveStop this task. Retain volumes, configuration and logs outside the removed checkout.

Follow the appliance workflow. Worktree paths identify state: archive before moving a task. This workflow does not describe deployment to the physical NVR.

Disconnect versus reboot

SSH or Orca disconnection leaves native processes and containers running. A host reboot ends native processes; browser startup and task recovery need explicit checks. Power recovery separates boot verification from application readiness.