docs: drop stale bash-first framing #24

2026-05-25T06:32:57-04:00

didericis commented

2026-05-25 06:32:57 -04:00

Summary

The project started life as bash scripts and got rewritten to Python (documented in docs/research/bash-vs-python-vs-go.md), but several docs still carried the old "bash-first" framing. Repo is now ~8.7k lines of Python vs. ~130 lines of bash (all in scripts/demo*.sh).

Touched: CLAUDE.md (both the "What this is" paragraph and the "Conventions" stdlib-first rule), PRD 0010 (quoted the old wording), and 5 research docs that variously called the project "bash-first" or "bash-orchestrated".

Left untouched (still accurate): bash code-fence syntax in examples, README's literal bash scripts/demo.sh (the demo really is a bash script), Claude Code's "Bash tool" references, IVIJL/devbox's "in bash" description (that external project actually is bash), and bash-vs-python-vs-go.md itself (decision record).

## Summary The project started life as bash scripts and got rewritten to Python (documented in `docs/research/bash-vs-python-vs-go.md`), but several docs still carried the old "bash-first" framing. Repo is now ~8.7k lines of Python vs. ~130 lines of bash (all in `scripts/demo*.sh`). Touched: CLAUDE.md (both the "What this is" paragraph and the "Conventions" stdlib-first rule), PRD 0010 (quoted the old wording), and 5 research docs that variously called the project "bash-first" or "bash-orchestrated". **Left untouched** (still accurate): bash code-fence syntax in examples, README's literal `bash scripts/demo.sh` (the demo really is a bash script), Claude Code's "Bash tool" references, IVIJL/devbox's "in bash" description (that external project actually is bash), and `bash-vs-python-vs-go.md` itself (decision record).

didericis added 1 commit 2026-05-25 06:32:58 -04:00

docs: replace stale bash-first framing with Python-stdlib-first

test / unit (pull_request) Successful in 16s

Details

test / integration (pull_request) Successful in 1m32s

Details

5e8ca21669

The project started life as bash scripts and got rewritten to Python
(documented in docs/research/bash-vs-python-vs-go.md). Several docs
still carried the old "bash-first" framing — misleading for anyone
reading them now (8.7k lines of Python vs. ~130 lines of bash, all
in scripts/demo*.sh).

- CLAUDE.md "What this is" + "Conventions": orchestrator is Python,
  posture is stdlib-first.
- docs/prds/0010-cred-proxy.md, docs/research/manifest-format-and-
  grouping.md: quoted CLAUDE.md's old wording — re-quote.
- docs/research/built-in-supervisor-design.md, landscape-containerized-
  claude.md, agent-sandbox-landscape.md, pipelock-assessment.md,
  network-egress-guard.md: drop "bash-first" claims about the project,
  keep accurate descriptions of external tools' bash usage.

Leaves untouched: bash code-fence syntax in examples, README's
literal `bash scripts/demo.sh` invocation (the demo IS bash),
Claude Code's "Bash tool" references, IVIJL/devbox bash description
(that project actually is bash), and the bash-vs-python-vs-go
research note that records the rewrite decision.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

didericis merged commit e07b8ecdb0 into main

2026-05-25 06:36:05 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: didericis/bot-bottle#24