Skip to content

docs: One orchestrator, three packages, PostgreSQL and clones in both deployments - #973

Merged
bwmatson merged 1 commit into
mainfrom
docs/orchestration-one-orchestrator-three-packages
Nov 16, 2026
Merged

bwmatson merged 1 commit into
mainfrom
docs/orchestration-one-orchestrator-three-packages

Conversation

@bwmatson

Copy link
Copy Markdown
Owner

Updates the orchestration design (docs/designs/orchestration.md) after the wave 1 scoping:

  • Exactly one orchestrator per installation, local or cloud. Workers share nothing with it and may run on its device, on other devices or serverless.
  • PostgreSQL in both deployments through SQLAlchemy Core, reached by a URL; a SQLite file stays as a test stand-in. This reverses the earlier 'SQLite locally' decision, because a worker on another device cannot open a file on the orchestrator's disk. The doc says what SQLAlchemy does and does not remove.
  • The kit becomes three packages in one uv workspace (core, orchestrator, worker) with import rules, split before the store and coordination interfaces land.
  • Every worker works in its own clone; the shared-worktree implementation is retired.
  • The Launcher is a container-based interface (local, remote host, Azure Container Apps Jobs; Kubernetes Jobs possible later).
  • Roadmap: a new wave 1a (the split), the store as three changes, leases for every lock, workspaces as clones. State reachable from other devices replaces the network-drive idea.
  • New open questions: where a remote worker's logs go in a local deployment, how a remote worker authenticates to the store, and which remote container hosts come first.

Docs only: the docs tests (521) and pre-commit pass. No code changes.

@bwmatson
bwmatson merged commit dc0598e into main Nov 16, 2026
5 checks passed
@bwmatson
bwmatson deleted the docs/orchestration-one-orchestrator-three-packages branch November 16, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant