Migrating from OpenEve

The product formerly named OpenEve is now Assembly Line. Existing OpenEve projects keep working through a compatibility window: every renamed surface below accepts its legacy spelling for now, and nothing breaks on upgrade. Update at your own pace, but prefer the new names in all new work.

Renamed identifiers

Surface	Old	New	During the compatibility window
Product name	OpenEve	Assembly Line	Display copy only.
npm scope	@openeve/*	@assemblyline-agents/*	Packages are published under the new scope; the old scope was never published.
Facade package	openeve (unscoped)	@assemblyline-agents/sdk	Install and import the new package.
CLI binary	openeve	assembly-line	Both bins are installed; the legacy bin still works and warns once on stderr.
Env prefix	OPENEVE_*	ASSEMBLY_LINE_*	Uniform prefix bijection. Every variable is read under both names; the new name wins, setting both to the same value is fine, and conflicting values fail at startup.
Build artifact dir	.openeve	.assembly-line	Both are read; new builds write .assembly-line. Having both present at once is an error — delete the stale one.
Hosts inventory	openeve.hosts.json	assembly-line.hosts.json	Discovery searches the new name first; both files at one directory level is an error.
Internal HTTP routes	/openeve/*	/assembly-line/*	Both are served with the same auth and rate limits.
OAuth callback	/openeve/connections/callback	/assembly-line/connections/callback	Both are served. Callback-URL construction still emits the legacy path until the Mirror-side registration cutover, then flips to the new path.
Scheduler header	x-openeve-scheduler-secret	x-assembly-line-scheduler-secret	Both are accepted.
Plugin export	openevePlugin	assemblyLinePlugin	Both are read; exporting both with different values is an error.
Provider export	openeveProvider	assemblyLineProvider	Both are read; exporting both with different values is an error.
Telemetry namespace	openeve.* / ai.openeve.*	assembly-line.* / ai.assembly-line.*	New names are emitted now; dashboards should dual-query old and new names during the window.

What never changes

These identifiers are permanent and are not part of the rename:

• Postgres openeve_* tables and indexes, NNN_openeve_* migration IDs, and the oe_ database prefix — the migration ledger is checksum-verified and the physical schema lives on production databases.
• /var/lib/openeve, /home/openeve, the openeve OS user, and its sudoers/sshd drop-ins on existing deployed hosts.
• Existing container, volume, and network names (openeve-caddy, openeve-edge, openeve-postgres, per-deployment openeve-<slug>*).
• The /workspace/.openeve reserved sandbox directory persisted inside deployed sandboxes.
• The openeve-computer-use/v1 crypto contexts — renaming them would break all existing device bindings.
• Git history, tags, and release notes.

Removal policy

Legacy aliases remain served for at least the documented compatibility window: 14 days after production cutover or more, extended to 30 days if any external user has received a build, plus one successful production rollback cycle. Alias removals ship only in a major release and are announced ahead of time. Nothing legacy is removed while usage logs still show traffic on it.