Shell Architecture
Standards and explanation for OpenShellOrg’s structured-shell direction — not a product repo (yet).
Thesis (short)
-
Structured data pipelines beat treating stdout as both data and display. We endorse Nushell as the Unix-centric reference implementation. PowerShell pioneered object pipelines; we recommend Nushell going forward.
-
SOS (flag syntax) and structured shells are complementary layers — spelling options consistently does not replace typed pipelines, and vice versa.
-
DevCentr recommends and configures; OpenShellOrg standardizes and builds companion tooling.
-
Future topics include display vs transport decoupling, terminal protocol notes, TUI vs structured stdout, and speculative mixed-fonts research.
-
Do not reinvent Nushell. Advocate, optionally contribute upstream, and build companion libraries.
Documents
-
Thesis — structured pipelines vs byte streams
-
Layers — SOS / data model / terminal presentation stack
-
SOS and structured shells — complementary layers
-
Entrypoint Dispatch — auto-install + re-exec at the shell boundary (pairs with DevCentr Toolchain Management)
-
Dev-Centr — alignment without merging orgs
-
DevCentr and OpenShellOrg — who does what (detail)
-
Shell Host and Env Refresh — planned
env-refresh+shell-hostproducts -
Stance — do not reinvent Nushell
-
Future topics — TUI vs stdout, mixed fonts
Related projects
-
open-shell-org — SOS certification and flag syntax
-
nu-require — require / relaunch under Nushell
-
nu-emit — emit structured rows from C without hand-JSON
-
DevCentr · docs.devcentr.org — toolchain orchestration + Toolchain Management Pattern
-
Planned:
openshellorg/env-refresh; forked:openshellorg/terminal(see Shell Host and Env Refresh)
Not NVIDIA OpenShell — that is agent sandboxing. We care about structured pipes + CLI DevX.