Ecosystem

OpenShellOrg docs are assembled from multiple Antora components — one per main project.

Standards and explanation

Partner filesystem model

connectome-fs owns node/edition/projection semantics. Shell-architecture consumes that contract for navigation; it does not redefine SOS as a filesystem query language.

Companion libraries

  • nu-require — require / relaunch under Nushell

  • nu-emit — emit structured JSONL rows from C

  • project-map / lsgrouped — project-type + file-role classification; grouped directory listing (not a PATH ls replacement)

  • config-key-sanitation — classify / match / alert for config keys (active / deprecated / expired / unknown); never drop expired detection — Config Key Sanitation

Planned / forked products

Spec and ownership live in shell-architecture:

  • env-refresh + terminal fork — Nu-first env-refresh CLI (planned) and openshellorg/terminal (fork of Windows Terminal) with per-tab env health + Fix/Insert desync bar; DevCentr prefers these when installed

  • actor-shell — non-frustrating Windows/Linux UI shell on an Erlang-style actor runtime (D); Phase 1 libbeam_d landed

Orientation and help

  • about — machine orientation + command cards

  • info — modern GNU Info TUI

  • prohelp — progressive help engine + global help

  • prohelp-cli — bridges into D CLI frameworks

  • terminal-gui-prompts — promote confirm/input to native GUI dialogs; always echo prompt text for pipes

PlayTime (cousin, not a component here)

Dev-Centr’s PlayTime engine plays CentrMark playbooks and spawns argv (no shell costume). That stance belongs next to Entrypoint Dispatch. The engine is not in this hub yet — do not move it mid-build.

Partner: DevCentr

Aligned, not merged — practitioner orchestration + Toolchain Management:

Org site

openshellorg.github.io — landing page (not an Antora component)