shell-architecture

Standards and explanation for OpenShellOrg’s structured-shell direction — not a product repo (yet).

Published docs: https://openshellorg.github.io/open-shell-org/shell-architecture/

Table of Contents

• Thesis (short)
• Documents
• Related projects
• License

Thesis (short)

1. 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.

2. SOS (flag syntax) and structured shells are complementary layers — spelling options consistently does not replace typed pipelines, and vice versa.

3. DevCentr recommends and configures; OpenShellOrg standardizes and builds companion tooling.

4. Future topics include display vs transport decoupling, terminal protocol notes, TUI vs structured stdout, and speculative mixed-fonts research.

5. Do not reinvent Nushell. Advocate, optionally contribute upstream, and build companion libraries.

6. Env refresh / shell-host — planned products so stale PATH is a non-issue (especially for Nushell users); see shell-host-and-env-refresh.

Documents

Antora component under docs/ (assembled into the org docs site):

• Thesis

• Layers

• SOS and structured shells

• Dev-Centr

• DevCentr and OpenShellOrg

• Shell Host and Env Refresh

• Stance

• Future topics

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

• project-map — project-type + file-role API; lsgrouped CLI

• Planned: openshellorg/env-refresh

• Forked: openshellorg/terminal (Windows Terminal + env-refresh UX)

• Nushell

• Public site domain: opensh.org ({OSO} Certified - opensh.org)

Not NVIDIA OpenShell — that is agent sandboxing.

License

MIT — see LICENSE