Relationship to Dev-Centr :: Shell Architecture

Dev-Centr and OpenShellOrg goals overlap and should stay aligned. They should not merge into one org.

Dev-Centr OpenShellOrg

Dev-Centr	OpenShellOrg
Recommends and configures Nushell for users	Advocates Nushell; builds standards and companion libs
Development Orchestration Suite product	CLI/shell standards + certification (SOS) + architecture docs
general-knowledge docs for developers	Ecosystem-facing specs anyone can implement
Repo terminal env inject / chrome; prefers our shell products	Own planned `env-refresh` + `shell-host` (plan)

Recommends and configures Nushell for users

Advocates Nushell; builds standards and companion libs

Development Orchestration Suite product

CLI/shell standards + certification (SOS) + architecture docs

general-knowledge docs for developers

Ecosystem-facing specs anyone can implement

Repo terminal env inject / chrome; prefers our shell products

Own planned env-refresh + shell-host (plan)

Rule of thumb: if it is “what should my team run?”, it is Dev-Centr. If it is “what should CLI authors converge on?”, it is OpenShellOrg. Cross-link; do not duplicate governance.

Stale PATH/env after installs is a shared UX debt: OpenShellOrg ships the durable fix; DevCentr consumes it. See Shell Host and Env Refresh and Division of Labor.

Wrong-host / wrong-version execution is a shell entrypoint failure: OpenShellOrg owns Entrypoint Dispatch (auto-install + re-exec; nu-require is the exemplar). DevCentr owns the broader Toolchain Management Pattern (control plane / TCF).