Repository navigation
fix(amber): balance the why paragraph against the wip status - #11
Merged
Merged
Conversation
The why section spelled out amber's planned mechanism (full git mirror, JSON metadata, integrity-hash manifest, incremental runs) in detail while scope says implementation has not started at all. Read together the entry reads as a roadmap with no code behind it, the weakest ratio of promise to substance among the 14 entries. Compress the plan to one sentence naming what amber is meant to capture, not how, so the page's honest wip framing matches what the why section actually promises.
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
2 participants
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.
Summary
From an earlier editorial pass over all 14 project entries: amber's
whysection spells out the planned mechanism in detail (full git mirror, JSON metadata, an integrity-hash manifest, incremental runs), whilescopesays implementation has not started at all — no command, no installable package. Read together, the entry reads as a roadmap with nothing behind it yet, the weakest ratio of promise to substance among the 14 entries.This compresses the plan paragraph to one sentence naming what amber is meant to capture, not how, so the page's honest wip framing matches what
whyactually promises.scope's own honest-status disclaimer is untouched — it already does what the repo's own rules ask for a wip entry.Type of change
Checklist
pnpm check)Related issues
None
Generated by Claude Code