docs: say this is a reference implementation, and cut the CLI wall #1226

Merged
coilyco-ops merged 2 commits from aos/claude/ur54 into main 2026-08-24 01:43:14 +00:00
Owner

The opening sold cross-platform shell setup and hooks "for coilysiren/* repos", which names an org that moved, and framed the repo as something to install. Kai's framing is the honest one: this is a reference implementation and a grab bag, public so the shape is readable rather than because anyone should adopt it whole. The README now says that in the first screen.

The one piece genuinely built to travel had no section at all. aos-precommit releases independently and every repo in the fleet consumes it by upstream ref rather than forking it, so it now gets named hooks and a pointer to the band rules that decide its size caps. That is the part an outside reader can actually use.

The aos CLI section ran 50 lines across five command spellings, six prose paragraphs, and four inline doc links before a reader learned what aos is. Compressed to what it does, one code block with the four real entry points, the authority boundary that matters, and the doc links moved to the end.

pre-commit run --all-files passes clean.

Part of a cross-repo README pass, parent audit coilysiren/inbox#397.

The opening sold cross-platform shell setup and hooks "for coilysiren/* repos", which names an org that moved, and framed the repo as something to install. Kai's framing is the honest one: this is a reference implementation and a grab bag, public so the shape is readable rather than because anyone should adopt it whole. The README now says that in the first screen. The one piece genuinely built to travel had no section at all. `aos-precommit` releases independently and every repo in the fleet consumes it by upstream ref rather than forking it, so it now gets named hooks and a pointer to the band rules that decide its size caps. That is the part an outside reader can actually use. The aos CLI section ran 50 lines across five command spellings, six prose paragraphs, and four inline doc links before a reader learned what `aos` is. Compressed to what it does, one code block with the four real entry points, the authority boundary that matters, and the doc links moved to the end. `pre-commit run --all-files` passes clean. Part of a cross-repo README pass, parent audit `coilysiren/inbox#397`.
docs: say this is a reference implementation, and cut the CLI wall
All checks were successful
ci / aos-eval-tests (pull_request) Successful in 6s
ci / ward-doctor (pull_request) Successful in 6s
ci / aos-cli-tests (pull_request) Successful in 21s
ci / gate (pull_request) Successful in 45s
1f61afa203
The opening sold cross-platform shell setup and hooks "for coilysiren/* repos",
which names an org that moved, and framed the repo as something to install.
Kai's framing is the honest one: this is a reference implementation and a grab
bag, public so the shape is readable rather than because anyone should adopt it
whole. The README now says that in the first screen.

The one piece genuinely built to travel had no section at all. `aos-precommit`
releases independently and every repo in the fleet consumes it by upstream ref
rather than forking it, so it now gets named hooks and a pointer to the band
rules that decide its size caps. That is the part an outside reader can use.

The aos CLI section ran 50 lines across five command spellings, six prose
paragraphs, and four inline doc links before a reader learned what `aos` is.
Compressed to what it does, one code block with the four real entry points, the
authority boundary that actually matters, and the doc links moved to the end.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: devrel
Merge branch 'main' into aos/claude/ur54
All checks were successful
ci / aos-cli-tests (pull_request) Successful in 19s
ci / aos-eval-tests (pull_request) Successful in 7s
ci / ward-doctor (pull_request) Successful in 9s
ci / gate (pull_request) Successful in 51s
c1824239d4
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os!1226
No description provided.