Repository navigation
docs/rosCompose: drop the dangling .RnD/rosCompose link - #8
Merged
Merged
Conversation
ReorderBuffer/TimeBuffer were never pushed, so the path pointed nowhere. Say they are not yet published and that they are meant to land as storage layers under OneMachine's fail:: store contract. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SRQCkuYxHSYb9wbp3sNq6
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.
Requested by Roy · project thread
Before:
docs/rosCompose.mdsaidReorderBuffer/TimeBufferlive inHAPI/.RnD/rosCompose/(elasticBuffers.h,hls/), but that path is not on main or any branch, so readers hit a dead end. The paragraph was also headed "Home: OneHLS".After: the paragraph says the two buffers were confirmed in a local R&D round and are not yet published. It also says that, once promoted, they are meant to land as storage layers under OneMachine's
fail::Latest/fail::Bufferstore contract, so the drop, retry and recover policies compose over them. The heading is now "In hardware", which is what the paragraph actually describes.How: a docs-only edit to one paragraph. This follows the direction to make buffers, rings and queues one kind of storage that composable behaviours sit on, under a single contract.
🤖 Generated with Claude Code
https://claude.ai/code/session_019SRQCkuYxHSYb9wbp3sNq6
Generated by Claude Code