ASH-221: expand README Why — measurability, safety, wall-time#17
Merged
Conversation
The Why section argued ash mostly on token efficiency. Added three motivations that a single consistent entry point uniquely enables: - "No usage ledger" bullet — fragmented tools share no seam, so a concise performance-and-usage history of a session cannot be assembled at all. - "No safety chokepoint" bullet — every utility touches the filesystem directly; nowhere to interpose path validation or a soft jail. - The "ash is the response" paragraph now makes the wall-time point — one entry point is one place to optimize (warm daemon, no per-command process spawn, no environment re-probing) — and the ledger sentence covers latency so "is this faster?" is as answerable as "is this saving tokens?". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README §Why argued ash mostly on token efficiency. Adds three motivations a single consistent entry point uniquely enables:
rg/fd/jq/gitshare no seam, so a concise performance-and-usage history of a session cannot be assembled at all.Docs-only.
🤖 Generated with Claude Code