Orchestrata Ultimate / Deployment / Deployment inventory

Deployment inventory

Measured on 2026-10-22 between 23:30 and 23:58 EDT, and on 2026-10-23 between 00:30 and 01:00 EDT, on openmandriva-x8664. Every row is an observation from the machine. The commands were all read-only:

cat of each VERSION file;
readlink of each current link;
installed_plugins.json;
systemctl --user is-enabled|is-active;
incus list --all-projects;
incus exec app -- systemctl is-active;
the deploy logs.

What each installer does, and how it verifies and rolls back, is on Deployment.

A. Deployments (2026-10-22/23)

Deployment	Recorded commit	Source	Current?	Identity proof
`/opt/orchestrata`	`4ac0db570` (`VERSION`, deployed 2026-10-22T15:35:47-04:00)	GitLab `orchestrata-ultimate-architecture`	6 commits behind `origin/master` `a4cbc2bdf`; the 6 touch scripts, hooks, docs, tests and plans	`git -C /opt/orchestrata rev-parse HEAD` = `4ac0db570`; the only untracked file is `VERSION`
`/opt/orchestrata-tools`	`7309a3488` (deployed 2026-10-22T19:55:40-04:00)	`wt-TOOLS-FAST`	contains `4ac0db570`, does not contain `a4cbc2bdf`; on no remote branch	`VERSION`; no `tools-deploy` log exists for this commit
`/opt/codetools`	`a5c419f5` (release `58dc55ce7d9ba893`)	`~/workspace/orchestrata.codetools` `master` (no git remote)	yes, equals `master`	`codetools --version` prints `codetools 0.1.0 a5c419f5...`; ct-install 75: `IDENTITY OK`, `SMOKE-OK`
`/opt/hermes`	`b1b66a6` (deployed 2026-10-22T19:30:11-04:00)	`~/workspace/hermes` `master`	equals local `master`, which is 10 commits ahead of GitLab `d61afb0`	release `VERSION`; `hermes-deploy` log `DEPLOY-EXIT 0`
`/opt/pi-worker`	`238d899c3300` (deployed 2026-10-16T22:25:12-04:00)	`~/workspace/pi-harness` (no git remote)	yes	`pi-task verify`: VERIFIED, image `cc669a3edc5a`, python 3.14.7 (inventory of 2026-10-22)
orchestrata plugin	`gitCommitSha a4cbc2bdfcf9`, version 1.5.0, user scope	GitLab marketplace (git source)	yes	222 plugin files byte-identical to the commit
`~/.claude` config	`a4cbc2bdf` (deployed 2026-10-23T00:00:03-04:00)	`wt-MAP-PRECOMMIT`	yes	143 deployed files byte-identical to the commit
codetools plugin	`gitCommitSha 00b1304c35d4`, version 0.1.0, scope `local` for `/home/mohamed/workspace`	marketplace `codetools`: a `directory` source at `~/workspace/orchestrata.codetools`	see codetools plugin	`00b1304c` has no `plugins/` tree; the plugin was committed later in `84ec9bd7`

B. `~/.claude` on disk (2026-10-23)

Item	Measured
files under `hooks/`	61 (this includes the three hand-installed hooks, which are not in the repo)
files under `tools/`	43
`agents/`	7
`skills/`	11 directories, 361 files (this includes skills installed by Hermes and pi-worker)
`commands/`	14
`workflow/`	5
`.venv`	python 3.14.7, GIL disabled
backups	`.backup-20261022T124507`, `.backup-20261022T135948`, `.backup-20261023T000002`
MCP servers (user scope, `~/.claude.json`)	`codetools` = `/opt/codetools/bin/codetools mcp serve`; `orchestrata` = `/opt/orchestrata/.venv/bin/orchestrata-mcp`; `hermes` = `/opt/hermes/bin/hermes-mcp`; `perplexity` = `npx -y perplexity-mcp`; `jetbrains` (no command, a URL-based server that failed to connect in this session)

C. Host units (2026-10-23)

The full register, with every unit's role, binary and deployment, is Host services. In summary:

Only one orchestrata service is running: orchestrata-conversation-consumer (disabled, active, started by hand on 2026-10-22).
Three timers are enabled and waiting: orchgraph-backup (daily 03:00), orchestrata-kg-retention (Sunday 04:00) and orchestrata-history-mining (quarterly).
orchestrata-infra-drift.timer is disabled.
Five orchestrata-ast-daemon@ instances are running from /opt/orchestrata-tools.

D. Test fleet product copy

Item	Measured
`/opt/orchestrata/VERSION` in `orchestrata-test:app`	`22363abb2`, deployed `2026-10-12T13:20:13+00:00`, 546 commits behind `origin/master`
`orchestrata-kernel`, `orchestrata-gateway` in the container	`active`, `active`

E. Gaps found

Gap	Evidence
`orchestrata-mcp` cannot authenticate	`GATEWAY_TOKEN` is not among the key names in `~/.config/orchestrata/.env` or `/opt/orchestrata/.env`; JWT expiry 3600 s; open decision
The tools deploy is not on any remote	`7309a3488` is on no remote branch
Hermes deploy is not on GitLab	local `master` is 10 commits ahead of `origin/master`
codetools keeps 52 release directories	ADR-0035 (Accepted) says one release on disk
The test fleet runs an old product	`22363abb2`, 546 commits behind
Three hooks live only in `~/.claude/hooks`	deleted by the 2026-10-23 config deploy and restored from backup
The provision skill probes `~/prod/orchestrata-ultimate`	that directory does not exist; prod is `/opt/orchestrata`

History: the inventory of 2026-08-30

The rest of this page is the original inventory, measured on 2026-08-30 immediately after deploy/deploy.sh became the single entry point. It is kept as written. Several rows no longer hold: prod moved to /opt/orchestrata, the tools are deployed, and the plugin is v1.5.0.

1. `~/.claude` — user level

Deployed by install-claude-config.sh, git archive at a pinned ref, real files and no symlinks, with its own free-threaded venv.

Component	Count	State
hooks	46	deployed, registered in `settings.json`
tools	27	deployed
agents	7	deployed
skills	10	deployed
commands	14	deployed
workflow	5	deployed
orchestrata plugin	v1.5.0 @ `a37ce1a6`	installed + enabled, user scope, sourced from the git remote
`.venv`	python 3.14t	free-threaded, verified
`VERSION`	`a37ce1a6`	matches `origin/master`

2. systemd user units — this host

The three daemons at the top ran for months as hand-started processes owned by nothing; they became units in this session.

Unit	State
`orchestrata-ast-daemon`	active/running
`orchestrata-codemod-daemon`	active/running
`orchestrata-canvas`	active/running — `:8137` answers `/api/canvases` with 200
`orchestrata-history-mining.timer`	active/waiting
`orchestrata-kg-retention.timer`	active/waiting
`orchgraph-backup.timer`	active/waiting
`orchestrata-ast-live-sync`	loaded/failed — targets the absent `~/prod` tree
`orchestrata-bot`	installed, start skipped (no prod tree)
`orchestrata-conversation-consumer`	installed, start skipped (no prod tree)
`orchestrata-gateway`, `orchestrata-kernel` (host copies)	installed, start skipped — these run in the container

"Installed, start skipped" is deliberate: the unit file is version-controlled and present, ready for the moment its prerequisite arrives, and the installer names the missing binary instead of failing the whole deploy. Before that change, one unit targeting an absent prod tree killed the entire systemd step.

3. Test fleet — the product itself

Deployed as a copy at a pinned commit into /opt/orchestrata inside the app container. Until this session the container bind-mounted the developer's checkout and executed it live — same inode as the host's files, from a branch with 109 uncommitted edits.

Component	State
`orchestrata-kernel.service` (in container)	active
`orchestrata-gateway.service` (in container)	active
app code + venv	copied at `3cf440b3`, `/opt/orchestrata/VERSION` present
Redis / Memgraph / Prolog / app	running; 18 containers across all Incus projects
fleet probe	6/6 green, 0 red

4. Not deployed on this host

Component	Why
`/opt/orchestrata-tools/bin`	0 files — `install-tools.sh` has never run here
`~/prod/orchestrata-ultimate`	absent — no promotion has happened on this machine
`orchestrata-kg-ready`	absent; it comes from the tools install above

These three are one gap, not three: the missing tools install is why orchestrata-kg-ready is absent, which is why the prod-targeting units cannot start even once a prod tree exists.