camino-orch is the app-instance package runtime/orchestrator prototype. It is separate from Camino: Camino owns object state, schemas, edges, and subscriptions; orch owns process and object activation lifecycle.

The current prototype exposes InvokeFunction, ListActivations, and CloseActivation over Connect RPC. InvokeFunction creates or reuses an object-scoped activation and routes the call through a package-scoped runtime process built from the descriptor's source flake.

Run

nix develop
CAMINO_ORCH_DESCRIPTOR_PATHS="$PWD/../packages/todo-runtime/descriptor.quixos-package.txtpb" camino-orch-server-start
camino-orch-server-status
camino-orch descriptor list
camino-orch invoke-ref quixos.todo todo-runtime displayLabel.get obj:0198d5d2-2c89-7ddc-8fd0-5c32cebe2b3e '{}'
camino-orch status
camino-orch-server-stop

invoke-ref is a low-level debug escape hatch. Normal calls should go through Camino schema slots, for example camino method call <object-id> complete '{}' or camino field resolve <object-id> display_label '{}'.

The todo descriptor uses source_repo: "path:." and server_installable: "#server". Orch builds that flake installable with Nix and launches $out/bin/server.

For foreground debugging:

nix develop
camino-orch-server

The server listens on 127.0.0.1:7311 by default. Override with CAMINO_ORCH_HOST, CAMINO_ORCH_PORT, or CAMINO_ORCH_URL for the CLI.