OpenShellOrg thesis: structured shell pipelines, SOS relationship, Nushell advocacy.
Explore the docs
Report Bug
·
Request Feature
Standards and explanation for OpenShellOrg’s structured-shell direction — not a product repo (yet).
Published docs: https://openshellorg.github.io/docs/shell-architecture/
-
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.
-
Env refresh / shell-host — planned products so stale PATH is a non-issue (especially for Nushell users); see shell-host-and-env-refresh.
Antora component under docs/ (assembled into the org docs site):
-
docs — 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;
lsgroupedCLI -
Planned:
openshellorg/env-refresh -
Forked:
openshellorg/terminal(Windows Terminal + env-refresh UX) -
Public site domain: opensh.org (
{OSO} Certified - opensh.org)
Not NVIDIA OpenShell — that is agent sandboxing.
MIT — see LICENSE
Open Shell Org — openshell@devcentr.org